What each role in financial reporting knows that the others do not

Unit accountants know why their numbers moved. Consolidation knows how entities connect and cancel out. Management reporting knows what leaders expect to see. The filings team knows what regulators require. Trouble starts at each handoff, where figures travel onward but the reasons behind them stay with whoever booked them.

The business unit accountant

This person holds the story behind the ledger. They know which accrual was an estimate made under pressure. They know a supplier dispute is unresolved, and that the manual journal posted late on close day was a correction and not new activity. They often know which subledger feeds are unreliable and quietly patch them each period.

Almost none of this survives into the unit financial statements. A trial balance carries amounts. It does not carry doubt. When the unit accountant leaves or goes on holiday, the patching stops and the numbers shift for reasons nobody downstream can explain.

The consolidation team

Consolidation sees the whole group and understands ownership, currency translation and the eliminations needed to strip out trading between entities. It knows when two units disagree about what they owe each other, often before either unit does.

What it lacks is the operational reason for a mismatch. It can see that one side booked a recharge and the other did not. It cannot see whether the charge was agreed, disputed or simply forgotten. So it forces a plug to make the group balance and moves on. That plug becomes a permanent feature if nobody chases it back to the units.

There is a second blind spot. Legal consolidation and management consolidation frequently run on different structures. The team knows both hierarchies, but the people reading management packs rarely realise that a segment total and a legal entity total can legitimately differ.

Management reporting and cost review

This group knows what executives will ask and which variances will draw attention. It reshapes ledger data into cost centres, projects and segments that make sense to the business. It also carries a good deal of informal knowledge about allocations: which costs get spread, on what basis, and who complained last time.

The risk is drift. Management reports often pull from extracts, adjusted offline in spreadsheets. Over time they stop tracing cleanly to general ledger balances. Finance leaders then face two versions of profit and must explain the gap at the worst possible moment, usually in front of the board.

External, regulatory and board reporting

The people producing statutory filings, shareholder reports and regulatory returns know the disclosure rules in detail. They know what auditors will test and which footnotes need supporting schedules. Board pack preparers know the tone and level of detail the directors want.

They are furthest from the transactions. A regulator may ask why an asset value fell, and the answer sits with an asset accountant who reconciles the fixed asset register to the ledger and knows an impairment was booked on a judgement call. If that judgement was never written down, the filings team has to reconstruct it under deadline. Regulatory returns are especially exposed because they often use definitions that differ slightly from the financial statements, and only a handful of people understand the mapping.

Systems and subledger owners

Payables, receivables, payroll and fixed assets each run their own records. Their owners know about timing differences, held payments, rejected batches and adjustments still waiting to post. Reporting teams usually learn about these only when a reconciliation fails. A change to a feed, a new account code or a revised mapping table can break a report several steps away, and the system owner may never hear about the break.

Where the gaps do the most damage

Most reporting failures are not calculation errors. They are context failures. A number is correct in its own system and wrong in the place it ends up. The common pattern looks like this: a judgement made early, recorded only as an amount, reinterpreted later by someone who assumes it was a fact.

Anyone redesigning this process should map who holds each judgement and how it reaches the next person. Automating the transfer of figures without carrying the explanation alongside them tends to make reports faster and harder to defend.

Questions to ask the people who run it

The documented process describes the intended flow. These questions surface the real one.

• Which entries do you correct by hand every period, and what would happen if you stopped?
• When intercompany balances disagree, who decides the answer, and where is that decision recorded?
• Which management reports do not tie back to the ledger, and who knows why?
• What spreadsheet sits between the system and the board pack?
• If a regulator asked about this balance tomorrow, whose desk would the question land on?
• Which feed from another team do you check before trusting it?
• What do you know about this period's numbers that is not written anywhere?
• Who would notice first if a mapping table changed?
• When the last person in your role left, what broke?

The answers often contradict the process documentation. Those contradictions are where the redesign work should start.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.