Why does my AP aging report not match my GL AP balance?
The AP aging report is your subledger detail; the GL AP balance is the control account it should sum to. A mismatch almost always means a journal entry hit the control account without a matching subledger entry — a manual JE to AP, a bill dated into the wrong period, or an accrual that never reversed. Find the entry that only exists on one side.
By Zuny Fester, Head of Operations and MarketingPart of the accounts payable and invoice processing guide.
| Symptom | AP aging report total doesn't equal the AP balance shown on the GL/balance sheet |
|---|---|
| Root cause (most common) | A journal entry posted to the AP control account without a corresponding subledger (bill) entry |
| What a control account is | A GL summary account whose balance should equal its subsidiary ledger's total |
| Other common causes | A bill entered in the wrong period, an unreversed month-end accrual, a payment posted but not cleared |
| How to isolate it | Compare the two balances as of the same cutoff date, then look for entries that touch only one side |
What's actually supposed to match
Accounts payable is a classic control-account setup: the GL carries one summary balance, and the AP aging report is the subsidiary ledger — the itemized detail that should sum to it. AccountingTools states the relationship directly: "the ending balance in a control account should match the ending total for the related subsidiary ledger. If the balance does not match, it is possible that a journal entry was made to the control account that was not also made in the subsidiary ledger."
Where the mismatch usually comes from
A manual journal entry to the AP account — a write-off, a reclass, a correction — that bypasses the vendor-bill workflow is the single most common cause, exactly as AccountingTools describes: it hits the GL control account but never touches the subledger, so the two stop agreeing by exactly the amount of that entry. A close second is timing: a bill entered with the wrong period date, or a month-end accrual (see the accrual entry for received-but-unbilled goods) that didn't reverse the way it was supposed to, leaving an estimate sitting in the GL balance that the aging report — which reflects real posted vendor bills — never picked up.
How to actually find it
Pull both numbers as of the exact same cutoff — a same-day comparison across different report-generation times is a false mismatch, not a real one. Then look specifically for entries that exist on one side and not the other: search the GL detail behind the AP account for journal entries with no linked vendor bill, and check whether any accrual entries from the prior period actually reversed. The gap is the sum of whatever's unmatched, not something to explain away as rounding.
Next step
Map the finance workflow with the most exposure and prove the automation path.
Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.
Worked example
A $6,200 gap traced to one unreversed accrual
The GL shows AP at $412,900; the aging report totals $406,700 — a $6,200 gap. Pulling the GL detail behind the AP control account for the period shows one journal entry with no linked vendor bill: a $6,200 accrual for a shipment received near the prior month-end, posted directly to the AP account instead of a separate accrued-liability account, and never flagged to reverse. The real vendor invoice posted normally through AP the following month for $6,200 — meaning that amount is now sitting in the GL balance twice: once from the stale accrual, once from the real bill the aging report correctly reflects. The fix is reversing the original accrual entry, not adjusting the aging report, which was right all along.
Frequently Asked Questions
Sources
Related
Diagnostic
How do I reconcile a phantom AP liability from a broken Bill.com sync?
Compare open bills in your AP aging against actual disbursements on the bank statement. A phantom liability shows up as a bill still open in AP with a matching payment already visible on the bank side, which means the payment posted in Bill.com but its corresponding payment record never synced back to the accounting system, leaving the original bill looking unpaid.
Read moreTopic
AP & Invoice Processing
Accounts payable and invoice processing is the set of steps a vendor bill goes through between arriving at a company and turning into a payment: capturing what the vendor sent, checking it against wha…
Read moreDiagnostic
Why does one vendor show two different balances in AP aging?
The vendor almost certainly exists as two separate records in your vendor master file — created under slightly different names (a typo, a rebrand, a merger, a re-onboarding) — so bills and credits are split across both. AP aging reports by vendor record, not by real-world vendor, so it shows two partial balances instead of one true balance.
Read moreHow-to
How do I accrue for goods received but not yet invoiced at month-end?
Debit the relevant expense or inventory account and credit an accrued liability (or GR/IR clearing) account for the received-but-unbilled value, using the PO or receiving log to estimate the amount. Reverse the entry when the real vendor invoice posts, so the expense hits once, not twice.
Read more