How detail in payables, receivables and inventory rolls up into the general ledger — and what breaks when it does not.
A sub-ledger holds the transaction-level detail for one area — payables by supplier, receivables by customer, inventory by item — and posts a summary to a control account in the general ledger. The general ledger carries the balance; the sub-ledger explains it. The two must reconcile, and where they do not, the general ledger cannot be relied on.
The control account relationship is the structural basis of trustworthy accounts. If the receivables control account says one thing and the sum of customer balances says another, the difference is unexplained money and either figure could be the wrong one. Most of the time the cause is a journal posted directly to the control account, bypassing the sub-ledger entirely.
A supplier invoice creates a payables entry against that supplier, with full detail retained.
The general ledger receives the movement, not the detail. The control account balance should equal the sub-ledger total.
Sub-ledger total compared to control account balance, each period. Any difference is investigated, not written off.
Debtor and creditor ageing is produced from the detail, which is why the detail must be complete.
Sub-ledgers close before the general ledger so the control accounts are final when the ledger closes.
The receivables control account shows 48,62,310 while the receivables sub-ledger totals 48,47,110. The difference of 15,200 appeared at some point in the last quarter and nobody can place it.
The cause is a manual journal posted directly to the control account to correct a customer balance. It was a reasonable-looking fix — the general ledger now showed the right number — but it created a permanent difference, because the sub-ledger knows nothing about it. Every month afterwards the reconciliation carries an unexplained 15,200, and over time such items accumulate until the reconciliation becomes a list of things nobody remembers.
The structural fix is to block direct posting to control accounts entirely, so corrections must go through the sub-ledger where they belong — as a credit note, an adjustment or a write-off against a specific customer. This is a configuration setting in most ERP systems and it is frequently left open. Blocking it converts a whole category of reconciliation mystery into an error message at the moment of posting.
| Term | What it means |
|---|---|
| Sub-ledger | A detailed ledger for one area — receivables, payables, fixed assets — supporting a control account. |
| Control account | The general ledger account whose balance equals the sub-ledger total. It should always reconcile. |
| Accounting rule | Configuration deciding which accounts a transaction type posts to. |
| Direct posting | Posting straight to a control account, bypassing the sub-ledger. Almost always a mistake. |
| Drill-down | Navigating from a general ledger balance to the transactions that make it up. |
The single most common cause of an unreconcilable control account. Lock them against manual posting.
A difference found eleven months later cannot be traced to its cause. Monthly is the minimum.
Posting the difference away removes the symptom and keeps the cause, which will recur next period.
Each reconciliation needs a named owner and a sign-off, or it is performed inconsistently.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Control account variance | Should be zero. Any non-zero balance is an open item, not a rounding issue. | |
| Direct postings to control accounts | Should be zero once blocked. Count them before blocking to see the scale. | |
| Reconciliation ageing | How long differences persist. Old items rarely resolve themselves. | |
| Unposted sub-ledger transactions | Items stuck before reaching the general ledger, which create timing differences that look like errors. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.