Accounts Payable Reconciliation: Process, Example, and Best Practices

Accounts payable reconciliation is the process of verifying that a company's AP subledger matches its AP control account in the general ledger, and that both match what each vendor's own statement says is owed. It catches errors, duplicate payments, and unapplied credits before they distort the books.

What is accounts payable reconciliation?

Accounts payable reconciliation is the process of confirming that the AP subledger, the detailed record of every amount owed to every vendor, matches the AP control account it rolls up into, and that both agree with what vendors themselves say is outstanding. It's a checking process, not a payment process.

This matters because AP runs on two parallel records that should always agree but don't automatically stay in sync. The subledger updates every time an invoice is entered or a payment is made. The AP control account is supposed to reflect the same total.

When something goes wrong, a duplicate entry, a payment recorded against the wrong vendor, an invoice that never made it into the subledger, the two numbers drift apart, and reconciliation is what catches that drift before it reaches a financial statement. This is a narrower, more mechanical task than accounts payable management as a whole, it's one specific control inside that broader function.
‍

AP reconciliation vs. vendor reconciliation vs. balance sheet reconciliation

These three terms get used interchangeably, but they check different things against different sources, and knowing which one you're actually doing changes what you're looking for.

In practice, these nest inside each other. A full AP reconciliation usually involves reconciling several individual vendor statements as supporting evidence, and the resulting AP total is one of the line items checked during a broader balance sheet reconciliation.

They're not competing methods, they're different scopes of the same underlying question: does what we've recorded match reality.
‍

What are the steps in the AP reconciliation process?

The AP reconciliation process runs through seven practical steps: verifying the beginning balance, pulling reports, comparing totals, matching vendor statements, investigating variances, recording adjustments, and formally closing the period.

An AP clerk, staff accountant, or bookkeeper typically runs the process itself, with a Controller reviewing the result before the period closes.
‍

• Verify the beginning balance: confirm that the starting AP balance for the current period matches the ending balance from the previous period, before checking anything else. A mismatch here means last period's reconciliation wasn't actually clean.
• Pull reports: generate the AP aging report and the GL trial balance for the exact same date and time. Comparing reports pulled hours apart, after new invoices have posted, is a common way to manufacture a false discrepancy.
• Compare totals: check that the total on the AP aging report matches the balance of the AP control account in the general ledger. This is the core check the rest of the process exists to support.
• Match vendor statements: sample the top vendors by balance and match their statements against unpaid invoices and payment records, rather than checking every vendor exhaustively, to catch missing bills or unapplied credits.
• Investigate variances: trace each gap to a specific cause, direct postings to the AP control account that bypassed the subledger, manual journal entries, duplicate payments, rather than assuming it will resolve itself next period.
• Record adjustments: post the correcting entries needed to bring the subledger and control account back into agreement, with a clear note on why each adjustment was made.
• Close the period: document that the reconciliation is complete, with the supporting detail retained for audit purposes.

What does an AP reconciliation example look like?

A worked example makes the process concrete: a company's AP subledger shows $45,000 owed to a vendor, the AP control account also shows $45,000, but the vendor's own statement shows $46,200, a $1,200 gap that has to be explained before the period can close.

The investigation starts by pulling that vendor's activity for the period. In this case, the company had returned $1,200 of defective goods three weeks earlier and received a credit memo from the vendor, but AP never applied it to the account, it just sat in the system unrecorded.

The subledger and GL agreed with each other because neither one ever saw the credit, but both were wrong relative to what the vendor's statement actually reflected. The fix is a single adjusting entry: apply the $1,200 credit memo, which brings the internal records down to $43,800 and matches the vendor's corrected statement once they process it too.

This is exactly the kind of gap that only surfaces when you check against the vendor statement specifically, not just internal consistency between the subledger and GL.
‍

What are common reconciling items and discrepancies?

Most reconciling items fall into a handful of predictable categories: timing differences, unapplied credits, duplicate payments, direct postings that bypass the subledger, and a debit balance sitting where a credit balance should be.
‍

• Timing differences: an invoice or payment recorded in one period by the company but a different period by the vendor, usually not an error, just a mismatch that resolves itself once both sides catch up.
• Unapplied credits: a credit memo from a return, discount, or overpayment that exists in the system but was never applied to reduce what's owed, exactly the issue in the worked example above.
• Duplicate payments: the same invoice entered and paid twice, often because it arrived through two channels, email and a vendor portal, and nobody caught the overlap.
• Direct postings and manual journal entries: someone adjusts the AP control account directly in the general ledger without routing the change through the subledger first. The two records were tied together, and this is exactly the kind of entry that breaks that tie without leaving an obvious trail in AP's own system.
• A debit balance in AP: a vendor account that shows the company is owed money rather than owing it, usually from an overpayment or a return that was recorded but never followed up on. It's a genuine red flag worth investigating on its own, not just netting out against other balances.

Not every reconciling item points to a real problem. Timing differences are normal and expected. What matters is having a process that distinguishes a timing difference that will resolve on its own from an unapplied credit or duplicate payment that won't fix itself without someone acting on it.
‍

What are AP reconciliation best practices?

Reconciling on a consistent monthly cadence, tied to the broader month-end close, is the single most important habit here, everything else compounds on top of that foundation.
‍

• Reconcile monthly, not only when something looks wrong: waiting until a vendor complains or a number looks off means months of small discrepancies have already piled up by the time anyone investigates.
• Investigate discrepancies immediately: a reconciling item that gets carried forward "to look at later" almost never gets looked at later, it just becomes next month's larger, harder-to-trace variance.
• Segregate reconciliation duties from payment processing: the person reconciling the account shouldn't be the same person who approves and issues payments, otherwise the check loses its independence as a control. See our guide to accounts payable internal controls for the fuller framework this sits inside.
• Use a standardized checklist every cycle: rebuilding the process from memory each month is how steps get skipped under deadline pressure. A fixed template, the same fields, the same order, every time, makes the process repeatable regardless of who's running it.
• Document every adjustment: a brief note on why each correcting entry was made turns the reconciliation into something an auditor can actually follow, not just a number that changed.

These overlap with, but aren't a repeat of, the broader accounts payable best practices that apply across the whole AP function, these five are specific to keeping the reconciliation itself reliable.

What to look for in AP reconciliation software

AP reconciliation software should automatically match the subledger against the GL and flag genuine discrepancies, not just surface every minor timing difference as if it needed the same attention.
‍

• Automatic matching, not just automatic exporting: the software should actually compare subledger and GL totals and highlight the gap, not just make it easier to pull both reports side by side.
• Discrepancy classification: real tools distinguish a timing difference from an unapplied credit from a duplicate payment, instead of surfacing one undifferentiated list of "exceptions."
• A clear audit trail: every adjustment should be logged with who made it and why, so the reconciliation itself is auditable, not just its final result.
• ERP integration: the software should pull directly from the company's existing general ledger rather than requiring a manual export and re-upload every cycle.

For a broader look at what separates strong options in adjacent AP software categories, see our guide to the best invoice processing software.
‍

How Flo automates accounts payable reconciliation

Flo, Spendflo's AI agent, automatically compares the AP subledger against the general ledger every cycle, and classifies whatever doesn't match, a timing difference, an unapplied credit, a duplicate payment, so an accountant starts the investigation already knowing what they're looking at instead of starting from an unsorted list of gaps.

Every adjustment Flo helps identify gets logged automatically, building the audit trail that makes each close faster to review, not just faster to complete. Learn more on our accounts payable page.
‍

Frequently asked questions about accounts payable reconciliation

1. What is accounts payable reconciliation?

The process of verifying that a company's AP subledger matches its AP control account, and that both agree with what vendors themselves say is outstanding. It's a control that catches errors and discrepancies before they reach a financial statement.
‍

2. What is an example of accounts payable reconciliation?

A common example is a subledger and GL that agree with each other but both miss an unapplied vendor credit memo, making the internal records overstate what's actually owed until someone traces the gap back to the vendor's own statement.
‍

3. What are the three types of reconciliation in accounts payable?

AP reconciliation (subledger versus GL), vendor reconciliation (internal records versus one specific vendor's statement), and balance sheet reconciliation (the AP total as part of the broader period-end close). They nest inside each other rather than compete.
‍

4. How often should accounts payable be reconciled?

Monthly, tied to the broader close cycle. Waiting longer lets small discrepancies accumulate into larger, harder-to-trace variances by the time anyone investigates.
‍

5. What causes most accounts payable reconciliation discrepancies?

Timing differences are the most common and usually resolve on their own. Unapplied credits and duplicate payments are less common but require someone to actually act on them, they don't fix themselves.
‍

6. Can accounts payable reconciliation be automated?

Yes, and it's usually one of the highest-value automation targets in AP, since matching a subledger against a GL and classifying the resulting gaps is exactly the kind of repetitive, rules-based work software handles well. See our accounts payable automation guide for the broader picture.
‍

7. What's the difference between accounts payable reconciliation and 3-way matching?

‍3-way matching happens before payment, confirming a purchase order, receipt, and invoice agree. Reconciliation happens after, confirming the recorded totals from that whole process still match the general ledger and the vendor's own records.