Why an accounts payable aging report does not match the general ledger report

An accounts payable aging report does not match a general ledger report when the two files represent different scopes, cutoff conditions or postings. Start by making those conditions comparable, then build a signed bridge from open supplier balances to the AP control balance.

Do not use an unexplained adjustment to force agreement. The useful result is a list of evidenced differences, each with a document, owner and next action.

Establish exactly what should agree

Request the detailed aging export, the AP control-account transaction export and the ledger opening or closing balance for the same cutoff. Keep the reports' extraction timestamps and filter settings. An aging file that suppresses supplier debit balances is not the same population as a signed control-account balance.

Confirm these conditions before matching rows:

• The same legal entity, accounting period and posting cutoff.
• Every relevant AP control account, with non-trade accrual accounts identified separately.
• The same reporting currency and translation basis.
• Posted transactions on both sides, with voids and reversals treated consistently.

Microsoft's vendor aging documentation shows that date basis, transaction currency and inclusion of negative balances are report choices. That supports checking the settings rather than assuming the report label defines its contents.

For bucket definitions and the basic calculation, use the separate accounts payable aging report guide. This reconciliation uses the complete signed balance, not just the overdue columns.

Normalize the sign before calculating a difference

Use liability-positive amounts throughout: invoices increasing AP are positive; credits and payments reducing AP are negative. For a ledger export with separate debit and credit columns, the AP movement is credits minus debits. Apply that convention to the opening balance as well.

Unexplained difference = AP control credit balance - Comparable signed aging balance

Keep the original amount and sign fields beside your normalized amounts. Do not overwrite source values, and do not add an opening balance to a closing balance as though both were transaction movements. The general ledger report guide covers that account roll-forward separately.

A worked reconciliation with three causes

A US manufacturer compares its September 30, 2026, aging with its later close ledger. The aging shows two positive invoices. Document review finds an additional invoice posted after the aging was extracted, a credit hidden by the aging's negative-balance filter and a journal posted directly to the control account.

The evidence table below occupies A1:E6. A and B identify the item; C and D use the liability-positive convention. Zero means that specific row is absent from that export, not that its accounting value is zero.

Enter this in E2 and fill down through E6:

=D2-C2

In row 7, total columns C, D and E:

C7: =SUM(C2:C6)
D7: =SUM(D2:D6)
E7: =SUM(E2:E6)

The aging total is $112,000 and the AP ledger balance is $138,000. Their difference is $26,000. The document differences explain it: $18,000 - $4,000 + $12,000 = $26,000.

Prove the bridge with a check cell that must return zero:

=D7-C7-E7

These amounts are exact dollars, with no rounding. Refreshing the aging under the corrected cutoff and credit settings should produce $126,000 in this example. The remaining $12,000 is a ledger-only item requiring controller review. The bridge explains that difference; it does not establish that the journal is valid.

Match at a document level without duplicating amounts

Use entity, vendor ID, document ID and currency together where possible. Invoice numbers alone can repeat across suppliers. If the ledger splits one invoice across lines, sum those lines before comparing them with the invoice's open balance.

Do not match an original invoice posting directly to its remaining open balance without including its settlements. A partially paid invoice can legitimately have different original and outstanding amounts. Include the invoice, credits and payments through the cutoff to derive the comparable open amount.

For a larger exception file, put the cause label in F2:F6 and a selected cause in H2. This sums the signed difference for that cause:

=SUMIFS($E$2:$E$6,$F$2:$F$6,H2)

Microsoft's SUMIFS documentation confirms that the function sums amounts meeting the specified criteria. Covirage is not affiliated with Microsoft.

Label each exception by evidence: extraction timing, omitted credit, missing settlement, account scope or ledger-only posting. A small net difference can hide offsetting problems, so retain the positive and negative items rather than reviewing only their net amount.

Where reconciliation goes wrong

• Matching report dates but ignoring extraction times. Backdated close entries can change one file after the other has been saved.
• Comparing movements with balances. Monthly credits minus debits explain a movement; they need the signed opening balance to reach closing AP.
• Treating unmatched rows as errors immediately. A payment or credit may use a settlement reference rather than the invoice number. Inspect the supporting record.
• Deleting offsetting differences. Two unrelated exceptions can cancel numerically while both remain unresolved.

Run the checks before trusting a spreadsheet total before concluding that the accounting system is wrong. For recurring closes, the monthly file refresh checklist helps preserve comparable extracts and cutoffs.

Trace your own AP differences in Covirage

Bring the aging export and AP ledger detail with their cutoff information. Covirage maps the columns, and its tools compute and check the differences; the external AI model explains the result with every figure traced to its rows. Create a free Covirage account and bring a sample of your own files.

See Covirage for finance teams for the broader reporting context.