Where financial reporting breaks: handoffs, exceptions and workarounds

Financial reporting usually breaks where numbers change hands: subledgers feeding the ledger, entities agreeing intercompany balances, management and legal views being reconciled, and late adjustments landing after review. Each failure leaves traces in suspense accounts, unexplained bridges and spreadsheets that sit outside the ledger.

Subledger feeds that arrive late or do not agree

Business unit statements depend on payables, receivables, payroll and the fixed asset register posting cleanly to the general ledger. When a feed is late, the reporting team waits or estimates. When it arrives but does not agree, someone books a correcting entry and promises to investigate later.

The asset register is a common culprit. Depreciation and impairment get recorded in the asset system, yet the ledger shows a different net book value because a disposal or transfer was never posted.

How to tell: reconciling items that carry forward from one period to the next with the same description. Plug entries labelled "timing" that never reverse. A reconciliation signed off with an open difference and no named owner.

Manual journals at the end of close

Accruals, reclassifications and top side adjustments tend to cluster at the very end. Some are legitimate. Others correct errors that should have been fixed in the source system.

The damage comes when journals post after the business unit statements have been reviewed. Reviewers signed off on figures that no longer exist.

How to tell: journals dated in the period but created after the review meeting. Approvals granted in bulk by one manager. The same recurring accrual entered by hand each period because nobody built it into the system.

Intercompany balances and eliminations

Consolidation needs both sides of every intercompany transaction to match before eliminations can run. In practice, one entity books a charge and the other disputes it, or books it in a later period, or at a different exchange rate.

The consolidation team often forces the elimination and parks the difference somewhere harmless looking.

How to tell: an elimination difference account with a growing balance. Entities that confirm balances by email outside the reporting system. The same counterparty pair turning up in the mismatch report again and again.

Mapping the ledger to the statements

Every line in the statements and footnotes depends on a mapping from ledger accounts. When finance adds an account for a new product or cost centre, the mapping is easy to forget.

How to tell: unexpected growth in "other" lines. Footnote totals that miss the face of the statements by a small, stubborn amount. A preparer who keeps a private list of accounts to move by hand before publishing.

Management and legal views drifting apart

Legal consolidation follows entities. Management consolidation follows segments, products or regions. Both start from the same ledger, but allocations, transfer pricing and restructured hierarchies pull them apart.

Trouble starts when the bridge between them lives in a spreadsheet only one analyst understands. Cost management reports then show margins that cannot be explained against statutory results.

How to tell: board members asking why segment totals do not add up to the published figure. A reconciliation rebuilt from scratch each quarter. Allocation keys last updated before the most recent reorganisation.

Board packs, filings and regulatory returns

Board statements, shareholder reports and regulatory returns are the final handoff, and the most exposed. Narrative is drafted while numbers are still moving. Regulatory returns are often built from extracts that have their own logic, separate from the ledger.

A late adjustment then has to flow through every document. Some get updated. Some do not.

How to tell: a figure quoted in commentary that differs from the table beside it. Version names ending in "final" followed by something else. A regulatory return that nobody can trace back to a ledger balance without asking the person who built the extract.

Questions to ask the people who run it

The documented process describes how reporting should flow. The people doing it know where it actually bends. Ask them directly, and ask to see the files.

• Which reconciliations do you sign off with a known difference still open?
• What do you do when a business unit sends numbers after the cutoff?
• Which journals do you post every period by hand, and why are they not automated?
• Where do intercompany disputes get settled, and who has the final say?
• What spreadsheet would stop the close if it disappeared tomorrow?
• How do you bridge management results to the legal figures, and who checks it?
• When a number changes after review, how do you find every document it appears in?
• Which report or return could only one person produce?
• What checks do you skip when the deadline is tight?

Listen for hesitation. A pause before answering usually marks a workaround that has become part of the job.

What the workarounds are protecting

Most workarounds exist because something upstream failed once and was never fixed. The private mapping list covers a gap in system configuration. The forced elimination covers a dispute process that has no owner. The heroic analyst covers missing documentation.

Removing a workaround without fixing its cause moves the breakage somewhere less visible. Trace each one back to the handoff it compensates for, and change that handoff first.

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.