From 26 separate ledgers to one accounting control system
Problem
When a group of companies shares an accounting team, each company usually keeps its own ledger and closes its own month in its own way. Every bookkeeper develops a routine, and as long as the books eventually balance, the differences between those routines seem harmless.
In this case there were 26 separate company ledgers, with inconsistent month-end processes, delayed reconciliations, unclear intercompany balances, and exceptions accumulating across entities. On the surface this looked like a matter of bookkeeping volume, as if more hours would solve it. The deeper difficulty was that nothing connected the ledgers into a shared financial control system, so issues were being carried forward instead of resolved. Months stayed open or incomplete, bank and credit-card reconciliations were late, transactions were categorised inconsistently, intercompany balances could not be explained, and checks, deposits, transfers and loan payments remained unmatched. Problems surfaced late, during year-end and tax work. What does a month-end close mean when every entity closes differently? And how can anyone trust a consolidated picture built from 26 different habits?
Action
The better principle is that a control process should not depend on memory or individual judgment. I designed a standardised accounting operating model across the 26 ledgers.
The work included a consistent monthly close process, bank, credit-card, loan and general ledger reconciliations, standardised categorisation rules, formal intercompany procedures, review steps for bookkeepers and accountants, an exception tracker for unresolved items, monthly reporting, and written SOPs so the process could be followed in the same way across entities. The goal was a repeatable control framework in which exceptions are visible, ownership is clear, and month-end does not rely on anyone remembering how it was done last time.
Result
The system created a structured path toward bringing 26 separate ledgers under one consistent accounting control framework. The measurable proof available is:
- 26 company ledgers
- a standardised close and reconciliation process
- shared intercompany procedures
- centralised exception handling
- a documented monthly reporting workflow
- a target implementation window of 60 days
The lesson
In multi-entity accounting, transaction volume is rarely the main risk. The risk grows when every entity closes differently, when intercompany balances are handled inconsistently, and when exceptions stay invisible until year-end. A reliable accounting system needs what a reliable software system needs: clear rules, traceability, exception handling, documentation and processes that can be repeated by someone else.