Skip to content

UK finance teams

+44 7457 162137
Acinarypath

Case notes

Composite illustrations, not trophies and not promises.

The notes below are patterns we are regularly asked to untangle in UK finance teams. They are not descriptions of named clients. They are not audited results. No saving, no percentage, and no “transformation” is claimed, because a number without a ledger behind it does not belong on this site.

Pattern A

Three plants, one group pack that never tied.

A controllership desk with out-of-focus screens, cream folders, glasses and a steel ruler

A regional manufacturer with three sites kept local trading accounts and a group workbook. Each site could explain its own gross margin. The group page used a different cut of carriage and a different treatment of inter-site transfers. The monthly meeting began with a reconciliation and often ended there.

The work was not a new chart type. It was a single contribution statement: materials, direct labour, carriage, and transfers named the same way in each site and at group. Inter-site profit in stock was shown as its own line, not buried in a plug. The group pack carried a tie-out to the sum of the sites plus the eliminations, and that tie-out had an owner.

Site leads kept a shorter page that stopped at the costs they could influence. They no longer received the group eliminations and then tried to manage them. Commentary stayed with the local FD and the group controller, not with a generated paragraph.

Pattern B

Utilisation in one system, billing in another.

Two people reviewing a printed pack under a brass lamp, pages showing only geometric blocks

A professional services partnership talked about utilisation every Monday and about lock-up every month, using two systems that did not share a matter code cleanly. Fee earners recognised a week that finance could not find in the invoice run. Finance recognised a write-off that the operating report had already forgotten.

The useful cut was the life of a matter: time recorded, time billed, time written off, disbursements, and cash collected. Utilisation remained, but it stopped being the only number in the room. A lock-up bridge showed work in progress, debtors, and the movement between them, with the matters that explained the change listed underneath rather than averaged away.

Partners received their own matters. They did not receive every other partner’s compensation detail. That was an access decision made before the first extract, not a tidy-up after someone exported the wrong table.

Pattern C

Margin argued every Monday.

Overhead view of a laptop, cream report pages, a brass pen and a small plant on an oak desk

A multi-site specialty retailer had stock in one system, promotions in a set of workbooks, and a margin slide that changed depending on who refreshed it. Stores were compared on a gross margin that sometimes included markdown and sometimes did not. The argument was sincere. The definition was not stable.

The pack settled three margins and printed the names: intake margin, margin after markdown, and margin after distribution costs that stores do not control. Promotions moved from a side file into a dated list with an owner. A Monday view showed only the lines that had moved outside an agreed band, so the meeting had somewhere to start other than the whole range.

Stores saw their own band. Buying saw the range. Neither was given a national export “just in case”. The old workbook stayed in parallel until two promotional events had been explained without it.

What these notes are not.

They are not references you can call. They are not evidence that your close will shorten by a stated number of days. If a conversation turns into an engagement, the relevant pattern is rewritten against your ledger, your entities, and your readers. The composites stop at the door.

If you recognise the meeting.

Describe the argument, not the software you think you should buy. Tell us who is in the room and which two numbers refuse to meet. That is enough for a fit check.

Describe the argument