Accounts Payable Reconciliation

Accounts payable reconciliation is the process of proving that the total you owe your vendors is stated correctly and completely in your books. In practice it means two checks under one name: your AP subledger (the list of open vendor bills) has to equal the accounts payable control account in the general ledger, and your ledger has to agree with what the vendors themselves say you owe. When both tie out, you can close the period knowing your liabilities are real, whole, and in the right place. Last updated July 2026.

This guide focuses on the internal side: the subledger-to-GL tie-out and the month-end AP reconciliation process a controller runs before signing off on the close. The external side, matching each vendor statement line against your ledger, is a job of its own, and we hand the detailed mechanics of that off to a vendor statement reconciliation walkthrough. Read them together and you have the whole picture.

What is accounts payable reconciliation?

Accounts payable reconciliation confirms that your recorded liability to vendors is accurate and complete by tying the AP subledger total to the AP control account in the general ledger, and by agreeing your ledger to vendor statements. It exists to catch understated or overstated payables before they distort your financial statements or trigger a wrong payment.

The word "reconciliation" hides two distinct exercises. The first is internal and mechanical: the sum of every open bill in your AP module must match, to the penny, the single AP control account balance in the GL. The second is external and evidentiary: the balance your books show for each vendor should match the balance that vendor's statement shows. A clean close needs both. The internal tie-out proves your own system is consistent; the external match proves your system agrees with reality.

How do you reconcile accounts payable?

You reconcile accounts payable by running the AP aging (the subledger) as of the period-end date, comparing its total to the AP control account balance in the general ledger, then investigating and clearing every difference until the two agree. Once the subledger ties to the GL, you validate the balance against vendor statements for completeness.

The month-end sequence a controller actually follows looks like this:

Steps 1 through 6 are the tie-out. Step 7 is where you shift from "do my two reports agree with each other" to "do my books agree with the outside world," and it is the step most teams shortchange. The subledger can equal the GL perfectly and still be wrong if a vendor billed you for something that never got entered. Where this reconciliation fits in the broader close sequence is laid out in our month-end close checklist.

What is the accounts payable subsidiary ledger?

The accounts payable subsidiary ledger, or subledger, is the detailed record of what you owe each individual vendor, one account per supplier, that together sum to the single accounts payable control account in the general ledger. The GL carries the total; the subledger carries the breakdown that supports it.

In QuickBooks, Xero, NetSuite, or Sage, the subledger is what you see in the AP aging report or the open bills list: every unpaid invoice, by vendor, with its date and amount. The general ledger, by contrast, shows accounts payable as one control account with a single balance. The design principle is that the control account and the subledger are kept in sync automatically as long as every transaction posts through the AP module. Reconciliation is how you verify that sync actually held, because it breaks more often than people expect.

One detail to watch: a debit balance in a single vendor's subsidiary account. Accounts payable is normally a credit balance, so a debit usually signals a credit memo you have not applied or an overpayment, meaning that vendor is effectively holding your money. That is a prepayment or receivable, not a negative liability. Pull it out and review it before you let it net against your other payables, or your AP total will be understated for the wrong reason.

Why won't my accounts payable reconcile?

Accounts payable usually fails to reconcile because a transaction hit one system but not the other, or hit the wrong period. The most common culprits are a journal entry posted straight to the control account outside the AP module, a duplicate invoice, an unapplied credit memo, a cutoff error, or a payment applied to the wrong invoice. Each one breaks the tie-out in a predictable way.

The single most expensive difference is not on this list of visible errors, because it does not show up as an error at all. It is a missing invoice: a bill the vendor genuinely issued that never reached AP. Your subledger and GL can agree perfectly and still be too low, because the liability was never recorded anywhere. Nothing flags it. This is exactly why auditors test accounts payable for completeness rather than just accuracy, and why the completeness step in your reconciliation matters more than the arithmetic. Our guide to accounts payable audit procedures explains how a search for unrecorded liabilities works.

Here are the reconciling items that surface most often and what causes each one:

Notice that a misapplied payment can leave your subledger total unchanged while two individual vendor accounts are wrong. That is why the internal tie-out alone is not enough, and why the completeness check against statements earns its place in the process. Duplicate invoices deserve special attention because they cost real cash; we cover controls against them in preventing duplicate invoice payments.

How often should you reconcile accounts payable?

Reconcile accounts payable at least monthly, as a fixed step in your period-end close, and continuously if your volume is high. The subledger-to-GL tie-out belongs in every month-end close without exception. Vendor statement reconciliation can run monthly for major suppliers and quarterly for minor ones, weighted toward the vendors you spend the most with.

The logic is simple: the longer you wait, the colder the trail. A cutoff error or a misapplied payment is easy to unwind the week it happens, when the vendor can still pull the backup quickly. Six months later it is an archaeology project. High-volume teams that reconcile continuously spend almost no time on the tie-out at close because there is rarely anything left to find.

How is AP reconciliation different from vendor statement reconciliation?

AP reconciliation is the umbrella term; vendor statement reconciliation is one part of it. The internal tie-out proves your subledger equals your GL, using only your own records. Vendor statement reconciliation compares your ledger against an outside document the vendor sends, which is the only way to catch bills you never recorded.

The two answer different questions. The tie-out answers "is my accounting system internally consistent?" The statement match answers "does my system agree with what my vendors think I owe?" You need both because they fail independently. A perfectly consistent set of books can still be missing a liability. Because statement matching involves its own workflow, chasing statements, aligning date ranges, and running down line-level differences, we give it a dedicated vendor statement reconciliation guide rather than compressing it here.

Can accounts payable reconciliation be automated?

Yes. The subledger-to-GL tie-out and much of vendor statement matching can be automated by software that pulls both balances, flags the difference, and matches transactions against vendor statements automatically, routing only unexplained exceptions to a human. Reconciliation software turns a manual spreadsheet exercise into a monitored control that runs every day if you want it to.

Automation works best when the data feeding it is clean, and that starts at invoice intake. If bills are keyed by hand, you inherit the duplicates and transcription errors that later show up as reconciling items, so capturing every field and line accurately with invoice data extraction software removes a whole category of differences before they exist. On the matching side, PO-based checks are handled by invoice matching software, while the period-end tie-out and statement comparison are the job of dedicated accounts payable reconciliation software. Vendor statements often arrive as PDFs, so a practical first move is to convert the PDF statement into a working spreadsheet you can line up against your ledger.

None of this removes judgment. Software can prove your subledger equals your GL and surface the vendor whose statement disagrees with your books, but deciding whether a missing invoice is a timing difference or a genuine unrecorded liability is still the controller's call. Automation clears the mechanical work so your attention goes to the exceptions that actually threaten the close.