Ask a finance team where month-end actually goes, and the answer is almost never “posting journals.” Posting is quick. What consumes the days is everything that happens between systems: exporting payables, importing them somewhere else, chasing the difference between a subledger total and the control account, and re-checking figures that were already correct when they were first entered.
Where the time really goes
In a conventional setup, accounts payable, accounts receivable and the general ledger are three separate stores of truth. Every transaction is recorded once in a subledger, then again — in summary — in the GL. That second recording is the problem. It introduces a gap, and the gap has to be reconciled before anyone can trust a report.
Most closes are therefore spent proving that two systems agree about something that only happened once.
What a combined ledger changes
A combined ledger removes the second recording. AP, AR and the GL are one product sharing one ledger, so a supplier invoice does not post to a payables system and then flow into the general ledger later. It posts into the ledger, immediately, as a journal like any other.
The consequence is simple: there is no subledger-to-GL reconciliation, because there is no subledger sitting apart from the GL.
The practical difference
- No export and re-import. Nothing moves between systems, so nothing can be lost, duplicated or mistyped in transit.
- Reports are current by definition. Standard reports read the ledger directly. A journal posted at 11am appears in the trial balance at 11am.
- One audit trail. Every posting carries its origin, its approver and its date in a single chain, rather than being reconstructed across three systems.
- Fewer control accounts to babysit. Control accounts stop being a reconciliation exercise and become what they were meant to be — a summary view.
What it does not fix
A combined ledger is not a substitute for good process discipline. It will not chase a supplier for a missing invoice, decide your accrual policy, or tell you that a cost has been coded to the wrong department. Bank reconciliation still has to happen, because that is a genuine comparison between two independent records — your ledger and the bank’s.
What it removes is the artificial reconciliation: the work created by your own systems rather than by the business.
A realistic expectation
Teams moving to a combined ledger usually find the close compresses in two stages. The first is immediate — the subledger reconciliation simply disappears. The second takes a cycle or two, as people stop building spreadsheets to bridge gaps that no longer exist.
The honest measure of success is not the number of hours saved in the first month. It is whether, by the third close, anyone still asks whether the ledger and the subledger agree.