A control account reconciliation compares one general ledger balance, such as accounts receivable, with the total of the subsidiary ledger that details it, such as the customer accounts. When the two agree, every amount in the control account belongs to a named customer, vendor, asset or employee. When they differ, an entry has bypassed the detail.
What does a control account reconciliation prove?
A control account reconciliation proves that the summary balance in the general ledger is fully supported by individual records in the subsidiary ledger. It does not prove that each record is right. A customer balance can be wrong and still add up; the reconciliation only shows that nothing in the total is unassigned.
A control account is a general ledger account that holds the total of many detailed accounts kept elsewhere. A subsidiary ledger, or subledger, is the list of those detailed accounts. In most accounting systems, posting an invoice or a bill updates both at once, so they should never drift apart on their own.
That is why a difference matters even when small. It means the two records were not updated together, and the system's own design was bypassed somewhere. Proving each detailed balance is a separate step, done with vendor statements, customer tests, asset counts or payroll records.
Control accounts and the subsidiary ledgers behind them
A business usually has several control accounts. Each one has a matching subsidiary record that produces a report you can total. The reconciliation for each is the same in shape: the subledger report total as of period end against the control balance on the same date.
| Control account | Subsidiary ledger | Report to total |
|---|---|---|
| Accounts receivable | Customer accounts | Customer aging |
| Accounts payable | Vendor accounts | Vendor aging |
| Fixed assets, at cost and accumulated depreciation | Fixed asset register | Asset register by class |
| Inventory | Item or stock records | Valued inventory listing |
| Accrued wages and payroll liabilities | Payroll system | Payroll liability report |
| Petty cash | Petty cash vouchers and count | Count sheet |
Fixed assets are often the weakest of these, because the register is kept in a spreadsheet and updated by hand. The register-to-ledger tie and the physical check are covered in fixed asset reconciliation from register, ledger and count. Payroll liabilities bring their own subledger, the payroll register, and the steps are in the payroll reconciliation from register to ledger and tax forms. Petty cash is small but follows the same logic, with the count as its subledger, as the petty cash reconciliation form shows.
Direct journal postings that break a control account
The most common cause of a control account difference is a manual journal entry posted directly to the control account instead of through the subledger. The general ledger moves, the subsidiary ledger does not, and the totals part ways by exactly the amount of that entry.
Direct postings usually come from good intentions. A bookkeeper corrects a misposting with a journal entry. An accountant books a year-end accrual or a reclassification to the receivables account. An import from another system posts summary totals to the ledger without detail. Each is reasonable on its own; each breaks the tie.
Many systems let you prevent this by flagging an account as a control account, which blocks manual journals to it. Where that setting exists, turn it on. Where it does not, add a monthly report of non-subledger postings to each control account and review it as part of the close.
Two other causes are worth knowing. A subledger report run on a different date from the ledger shows timing differences that are not errors. A subledger that includes or excludes a currency, a branch or a class of accounts that the control account treats differently creates a permanent gap that grows every month.
How do you trace a control account difference to its entries?
To trace a control account difference, find the month it first appeared, then compare that month's control account postings with the subledger activity for the same month. The entries that sit on only one side are the cause.
Use these steps:
- Confirm both reports share one as-of date and the same scope.
- Find the first month with a difference. Compare the control balance and the subledger total at each recent month end. The difference usually starts in one month and then carries forward unchanged.
- List that month's postings to the control account and group them by source: sales, receipts, bills, payments, journals.
- Compare each group with the subledger's activity for the same month. The group that does not match holds the problem.
- Within that group, filter for manual entries and for entries with no customer, vendor or item attached.
- Correct the record that is wrong. If the entry belongs to a customer, reverse it and repost through the subledger. If it belongs to another account, reclassify it out.
If the difference grows every month by a similar amount, look for a recurring entry, such as an automated journal or an import, rather than a one-off error.
When a control account difference points to concealment
Some control account differences are not mistakes. A receivable written off by journal with no customer attached, a vendor payment with no matching bill, or a subledger total that quietly matches only because an unexplained adjustment was made each month can all hide theft. These deserve escalation, not a quick reclassification.
Watch for a difference that someone keeps clearing with an entry they cannot support, for adjustments made by the same person who handles cash, and for subledger totals that match the control account only after a last-minute entry. A persistent gap that nobody can explain over several months is a reason to involve someone outside the bookkeeping function. The guide on what to do if you suspect embezzlement at work covers how to protect the evidence and who to tell. On the cash side, PreciseBankFlow flags bank statement lines that do not match the ledger, which helps confirm whether payments behind an unexplained entry ever left the account.