How do I reconcile a vendor statement against my AP ledger?
Compare the vendor's list of open invoices against your own AP ledger for that vendor, item by item, not just by total balance. Most gaps are timing — an invoice the vendor issued but you haven't received or entered yet, or a payment you've sent that the vendor hasn't applied yet — not a real dispute, and matching totals alone can hide two offsetting timing gaps that shouldn't have offset.
By Zuny Fester, Head of Operations and MarketingPart of the accounts payable and invoice processing guide.
| What's being compared | Vendor's own open-invoice list (their statement) vs. your AP ledger's open balance for that vendor |
|---|---|
| Where to pull your side | A vendor balance detail report — open bills and credits for that specific vendor |
| Most common gap: your side | An invoice the vendor already issued that hasn't been received or entered into AP yet |
| Most common gap: their side | A payment you sent that the vendor hasn't yet applied to the specific invoice it covers |
| Why matching totals isn't enough | Two offsetting gaps of similar size can make totals tie even though neither individual invoice actually matches |
Why a matching total doesn't mean the reconciliation is clean
A vendor statement showing the same total balance as your AP ledger looks like a clean reconciliation, but a total can match by coincidence when two separate gaps happen to offset — an invoice you haven't entered yet, worth roughly the same as a payment the vendor hasn't applied yet. The totals tying doesn't mean either individual invoice actually matches; it means the errors happened to cancel out at the aggregate level. A real reconciliation compares line item to line item, not just balance to balance.
The most common gap on your own ledger
An invoice on the vendor's statement that's missing from your AP ledger is usually not a dispute — it's an invoice the vendor has already issued and mailed or emailed, that simply hasn't made it into your AP system yet, whether due to mail time, an approval queue, or a processing backlog. Your own vendor balance detail report — pulling open bills and credits specifically for that vendor — is the source for your side of the comparison; anything on the vendor's statement that isn't on that report needs to be traced to figure out whether it's genuinely missing or simply not yet entered.
The most common gap on the vendor's statement
The mirror-image gap is a payment you've sent that still shows on the vendor's statement as an open invoice, because their AP-side counterpart — accounts receivable — hasn't applied it yet. This is the exact same unapplied-cash and remittance-matching problem covered elsewhere in this library, just from the paying side rather than the receiving side: the payment exists and was sent, but the vendor's own processing hasn't caught up to reflect it on their statement.
When a gap is a real dispute, not just timing
Not every gap resolves itself with time. An invoice amount that differs between your ledger and the vendor's statement for the same invoice number — not a missing invoice, an actual dollar mismatch on one that both sides agree exists — usually points to a pricing discrepancy, a quantity dispute, or a credit memo one side applied and the other didn't. Those need to be resolved directly with the vendor rather than left to age out, since unlike a pure timing gap, they won't self-correct on the next statement.
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 vendor statement and an AP ledger that tie in total but not line by line
A vendor's statement shows a $22,400 open balance across three invoices: #V-901 ($8,000), #V-902 ($6,400), and #V-905 ($8,000). Your AP ledger's vendor balance detail report shows a $22,400 open balance too — but across a different set: #V-901 ($8,000), #V-903 ($6,400, not on the vendor's statement at all), and #V-905 ($8,000).
The totals tie exactly, which would pass a balance-only check. Line by line, they don't: your ledger has #V-903 open, but the vendor's statement doesn't list it — meaning either it was paid and the vendor hasn't applied that payment yet, or it was somehow miscoded on your side. Meanwhile the vendor's statement lists #V-902, which isn't on your ledger at all — an invoice you likely haven't received or entered yet. Both gaps happen to be $6,400, which is exactly why the totals matched despite the ledgers actually disagreeing about which invoices are real and open. Resolving this means confirming #V-903's actual status with the vendor and locating or requesting a copy of #V-902 — not accepting the matching total as proof everything's fine.
Frequently Asked Questions
Sources
Related
Topic
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 moreDiagnostic
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.
Read moreDiagnostic
How do I run an AP payment batch and choose ACH vs check vs virtual card?
Batch by payment method and settlement timing, not just due date. ACH settles same- or next-day but is capped (NACHA's same-day limit is $1M/entry) and needs vendor bank details; check is slow and float-prone but needs nothing from the vendor; virtual card is fastest but only works if the vendor accepts card. Some ERPs don't even distinguish ACH from check in their data model.
Read more