Subsidiary Ledgers and Control Accounts, Explained: How AR and AP Subledgers Keep Detail Out of the General Ledger — Posting, Reconciliation, and What an Out-of-Balance Subledger Means

Your balance sheet says customers owe you $84,000. Good news — unless your biggest customer asks for a statement and you cannot tell them what they owe, which invoices are overdue, or whether last Tuesday's payment was applied. The general ledger knows the total and nothing else. That gap — one number where you need four hundred — is exactly what subsidiary ledgers exist to close.

A subsidiary ledger (subledger) is a supporting ledger that holds the detail behind one general ledger balance: one mini-account per customer, per vendor, per fixed asset. The general ledger account that summarizes it is called the control account. The entire system rests on one rule: the control account balance must always equal the sum of its subledger balances. When it does, your books tie together. When it does not, something was posted wrong — and the difference tells you where to look. This guide covers how the two big subledgers work, how postings flow from journals to control accounts, the month-end reconciliation routine, what an out-of-balance subledger means, and how to track the difference down.

The Core Idea: Detail Lives in the Subledger, Totals Live in the Ledger​

Picture a wholesaler with 300 customers and 2,000 credit sales a month. If every sale posted directly to the general ledger, the Accounts Receivable account would drown in thousands of entries, and finding one customer's balance would mean sifting through all of them. Worse, the trial balance — which lists every general ledger account — would need 300 separate receivable accounts to show who owes what.

The subsidiary ledger solves this by splitting the job in two:

• Subsidiary ledger: one account per customer (for receivables) or per vendor (for payables), recording every invoice, payment, credit memo, and adjustment for that party. This is where you look up what Acme Corp owes today.
• Control account: a single general ledger account — Accounts Receivable, Accounts Payable — that carries only the grand total. This is what appears on the trial balance and the balance sheet.

Every transaction that touches a customer's account is recorded in the subledger detail and summarized into the control account, so the two stay in lockstep. The control account "controls" the subledger in the internal-control sense: because the two are maintained through separate postings, their agreement is independent evidence that both are right. An error in either one breaks the tie-out and announces itself at month-end instead of hiding until an audit.

The Two Subledgers Every Business Has: AR and AP​

The Accounts Receivable Subsidiary Ledger​

The AR subledger holds one account per customer. Each account shows the invoices you sent that customer (debits, increasing what they owe) and the payments, credit memos, and write-offs applied to them (credits, decreasing it). The running balance is what that customer owes you right now.

This detail powers daily operations in a way the control total never could. Customer statements, collection calls, aging reports that bucket balances into current, 30, 60, and 90+ days past due, credit-limit checks before approving the next order — all of it reads from the subledger, not the general ledger. When a customer disputes invoice 1847, you open their subledger account, not the company's books.

The Accounts Payable Subsidiary Ledger​

The mirror image: one account per vendor, showing the bills each supplier sent (credits, increasing what you owe) and your payments and debit memos (debits, decreasing it). The balance per vendor is what you owe that supplier.

The AP subledger drives the payment run — which bills are due, which carry early-payment discounts worth taking, which are overdue — and it is the first place to look when a vendor claims you never paid. Like AR, it feeds an aging schedule, this one telling you where your cash is about to go rather than where it should come from.

How Postings Flow: Daily Detail, Periodic Totals​

The classic posting rhythm, built around special journals, explains the relationship better than any definition. It has two speeds:

1. Daily (or continuously): post the detail to the subledger. Each credit sale is posted to that customer's subledger account the day it happens. Each supplier bill goes to that vendor's account. The subledger is always current, because collectors and payables clerks need today's numbers, not month-end's.
2. Periodically: post the totals to the control account. At month-end (or weekly), the column totals from the special journals post to the general ledger control account in a handful of entries. The sales journal's total debits Accounts Receivable; the cash receipts journal's total credits it.

A small example makes the mechanics concrete. Suppose July's activity for a shop with two customers looks like this:

• Credit sales for the month total $12,000: $7,000 to customer A, $5,000 to customer B.
• Cash collected from customers totals $5,000: $3,000 from A, $2,000 from B.

The subledger postings happen transaction by transaction: A's account is debited $7,000 and credited $3,000, ending at $4,000 owed; B's is debited $5,000 and credited $2,000, ending at $3,000. The control account gets just two postings for the whole month: a $12,000 debit from the sales journal and a $5,000 credit from the cash receipts journal, ending at $7,000. And $4,000 plus $3,000 equals $7,000 — the tie-out holds.

Modern accounting software collapses the two speeds into one: entering a sales invoice updates the customer's subledger record and the AR control balance in the same instant. The concept survives underneath, though. Most systems still forbid or warn against journal entries posted directly to a control account, precisely because a direct posting updates the total without touching the detail and breaks the tie-out by design.

The Month-End Routine: The Schedule and the Tie-Out​

Once a month, the subledger proves itself with a schedule. A schedule of accounts receivable lists every customer with a nonzero balance and totals them; a schedule of accounts payable does the same for vendors. The routine is short:

1. Print the schedule. Every open customer balance, summed to a total. The total is the subledger's claim about what the control account should be.
2. Compare to the control account. Pull the Accounts Receivable (or Payable) balance from the general ledger trial balance for the same date.
3. Investigate any difference immediately. A tie-out that fails by any amount means at least one posting went to the wrong place. Do not book a plug to force agreement — a plug makes the reports agree while leaving the underlying error in the detail, where it will corrupt statements, agings, and collections.
4. Age the detail while you are there. The same customer-by-customer data produces the aging report. Review anything over 60 days past due for collection action and anything that looks uncollectible for the allowance.

Businesses that reconcile monthly catch errors while the paperwork is still on someone's desk. Businesses that reconcile quarterly or yearly catch them when nobody remembers what happened.

What an Out-of-Balance Subledger Means​

An out-of-balance subledger means exactly one thing: the detail and the total disagree, so at least one entry exists in one place but not — or not correctly — in the other. It does not tell you which side is wrong. The usual suspects, roughly in order of frequency:

• A journal entry posted directly to the control account. The classic cause. Someone books an adjusting entry — a reclass, a write-off, a correction — straight to Accounts Receivable in the general ledger. The control moves; no customer's account does. This is why good systems lock control accounts against manual journals, and why the lock should stay on.
• An unposted or half-posted batch. In systems with batch posting, a batch of invoices entered in the AR module but never posted to the general ledger leaves the subledger ahead of the control. A batch posted twice leaves it ahead by double.
• Postings to the wrong customer or vendor. The totals still tie — the right amount landed in a subledger account — but the wrong party's balance is off. Aging reports and statements go wrong while the tie-out passes, which is why reconciling the total is necessary but not sufficient.
• Transposed or mistyped amounts. An invoice entered as $540 in the subledger and $450 in the control posting (or vice versa) breaks the tie by $90. Differences divisible by 9 are the fingerprint of a transposition — a quick first check before you start pulling invoices.
• Discounts, returns, and adjustments recorded on one side only. A credit memo applied to the customer's account but never journaled to the control, or a cash discount taken in the payment but recorded at gross in the subledger, leaves a stubborn small difference.
• Cutoff and timing differences. Invoices dated in the new month but included in last month's schedule, or a payment recorded on different dates in the two places. These self-correct next period but will fail this month's tie-out.
• Rounding and currency conversion. Multi-currency subledgers and split allocations can leave penny differences. Real systems tolerate these with a rounding allowance; anything over a few cents deserves the full hunt.

How to Track the Difference Down​

When the schedule and the control disagree, work the gap systematically instead of re-checking everything:

1. Quantify the difference first. Is the subledger higher or lower than the control, and by exactly how much? The direction halves the suspect list: a subledger that is higher than the control in AR usually means a payment or credit memo missing from the control side, or a sale double-posted to a customer.
2. Check for the 9-divisible tell. Divide the difference by 9. If it divides evenly, suspect a transposition (digits swapped) or a slide (decimal point shifted) and scan postings for digit pairs that could produce it.
3. Halve the difference. If half the difference matches a known transaction amount, that transaction was probably added instead of subtracted (or debited instead of credited) on one side.
4. Scan the general ledger control account for manual journals. Any hand-posted entry to a control account is guilty until proven innocent — verify each one has a matching subledger posting.
5. Verify batch postings and cutoff. Confirm every subledger batch for the period actually posted to the general ledger exactly once, and that the schedule and the trial balance cover the same date range.
6. Reconcile forward from the last clean tie-out. If last month tied and this month does not, the error is in this month's activity. List this month's control postings and match each to its subledger source until one has no partner.

Fix the error at its source — correct the wrong-customer posting, post the missing batch, reverse the direct journal and rebook it through the subledger module — then re-run the schedule and confirm the tie-out before closing the period. The audit trail matters here: future you (and your auditor) will want to see what was wrong and how it was corrected, not just matching numbers.

Beyond AR and AP: The Other Subledgers​

Receivables and payables are the pair every business has, but the pattern repeats wherever one balance summarizes many items:

• Fixed asset subledger. One record per asset — description, cost, placed-in-service date, depreciation method, accumulated depreciation — rolling up to the Buildings, Equipment, and Accumulated Depreciation controls. Without it, you cannot compute depreciation or prove what you own at audit.
• Inventory subledger. Perpetual records by item or SKU, rolling up to the Inventory control. A physical count that disagrees with the subledger is the inventory world's out-of-balance signal.
• Notes receivable and notes payable subledgers. One record per loan, tracking principal, interest accrual, and maturity, behind the Notes controls.
• Payroll and employee advance subledgers. Per-employee detail behind accrued payroll and advance balances.

Each follows the same contract: detail in the subledger, total in the control, tie-out every period.

The Same Pattern in Plain-Text Books​

If you keep books in Beancount, you already have subledgers — they are just spelled with colons. Hierarchical accounts give you the customer-level detail and the control total from a single journal, with no separate postings to drift apart:

2026-07-03 * "Acme Corp" "Invoice 1847 - consulting, net 30"
  Assets:Receivables:Acme-Corp                  7000.00 USD
  Income:Consulting                            -7000.00 USD
 
2026-07-18 * "Acme Corp" "Payment received, invoice 1847"
  Assets:Checking                               7000.00 USD
  Assets:Receivables:Acme-Corp                 -7000.00 USD

Each Assets:Receivables:<customer> account is one subledger account, and the parent Assets:Receivables balance is the control total — computed, not posted, so it cannot drift out of balance with its detail. A balance report grouped at the parent shows the control figure for your balance sheet, while drilling into the children shows every customer's open balance, the equivalent of the schedule of accounts receivable. The month-end routine shrinks to reviewing the per-customer balances for stale items rather than proving two ledgers agree. For the mechanics of querying these balances, the Fava dashboard documentation covers balance-sheet and account-drill-down views, and the double-entry primers walk through the underlying journal structure.

Common Mistakes That Break the Tie-Out​

• Posting manual journals to a control account. The number one cause, and entirely preventable. Route every AR and AP adjustment through the subledger module so both sides move together.
• Treating the tie-out as the whole reconciliation. Matching totals prove the postings agree; they say nothing about whether each customer's balance is right. Pair the tie-out with aging review and periodic statement confirmations.
• Letting unapplied cash pile up. Payments received but never applied to invoices inflate both the subledger and the control equally — the tie-out passes while customer balances overstate what is owed. Apply cash promptly and clear unapplied receipts monthly.
• Reconciling rarely. A quarterly tie-out that fails means three months of activity to search. Monthly takes minutes when the habit is fresh.
• Plugging the difference. A journal that forces agreement without finding the error converts a visible alarm into two wrong reports. Find the entry, fix the entry.

Your Month-End Subledger Checklist​

Close every period the same way and out-of-balance subledgers become a ten-minute fix instead of a forensic project: run the AR and AP schedules, tie each to its general ledger control, age the detail and chase anything past due, apply all unapplied cash, and confirm no manual journal touched a control account all month. The control account is a promise that the detail adds up — keep the promise monthly, and your receivables and payables will survive any audit, any collection dispute, and any Tuesday-afternoon question about what one customer really owes.