Reconciling accounts payable means proving that the vendor invoices you booked, the balance in your AP subledger, and the control account in your general ledger all agree, and that no supplier is owed money you never recorded. The slow part is not the arithmetic. It is getting invoices and vendor statements off PDFs and into a spreadsheet you can actually match. Upload a statement or an invoice and get every line as structured data to reconcile against your ledger.
Upload your invoices
Drop files here or click to upload
Up to 50 files
Uploading...
AP reconciliation looks like a two-number check: the total of the AP subledger should equal the AP control account in the general ledger. It rarely does on the first try. A journal was posted straight to the control account, an invoice was entered twice, a credit memo never got applied, or a vendor is carrying an invoice on their statement that your team never received. Every one of those is a small difference that a person now has to chase, usually at month-end when there is no time to chase it.
A manual journal entry hit the AP control account without a matching entry in the subledger, so the two stop tying. Finding it means listing every entry to the control account that did not come from the AP module.
A supplier statement lists every invoice they think is open. To reconcile it you need those lines in a spreadsheet next to your own ledger, and instead you are reading a PDF line by line and typing invoice numbers.
The most expensive reconciliation difference is an invoice the vendor has issued that never reached AP. It does not show up as an error. It shows up as a balance that is quietly too low, which is exactly what an auditor tests for.
The same invoice entered under two slightly different numbers overstates what you owe and, worse, sets up a duplicate payment. Reconciliation is where duplicates surface, if the data is clean enough to spot them.
A credit memo posted to the vendor but never applied against an invoice leaves both the credit and the invoice open. The net is right and the detail is wrong, so the statement never agrees with your ledger.
You booked an invoice on the last day of the month, the vendor booked their payment receipt in the next period, and the two statements will never match until you separate genuine timing differences from real ones.
Reconciliation software helps you compare three things: the AP subledger, the GL control account, and each vendor statement, then explain every difference between them. The comparison and the journal entries run inside your accounting system. The step that stalls most teams is upstream: turning the invoices and the vendor statements into structured lines you can line up and match. That is the part the extractor at the top of this page handles.
Read a supplier statement PDF and return every open invoice, credit, date, and amount as rows, so you can match the statement against your ledger instead of reading it line by line.
Vendor, invoice number, date, and totals off every invoice, captured cleanly so the subledger you are reconciling was accurate when it was posted in the first place.
Consistent invoice number and vendor fields make duplicates visible in a sort, which is the single fastest reconciliation win and the one that also stops a duplicate payment.
Statement lines and your ledger export in the same Excel or CSV shape, so a lookup or a pivot surfaces what is on the statement but not in your books, and the other way round.
The arithmetic on each document is checked and low-confidence fields are flagged, so a scanned statement does not seed the reconciliation with a misread amount.
Statements and invoices are encrypted in transit, are not used to train public AI models, and processed files are deleted automatically.
The sequence is the same whether you reconcile in QuickBooks, NetSuite, Sage Intacct, or a controller-built spreadsheet.
Run the AP aging as of the period-end date and agree its total to the AP control account balance in the general ledger. Any difference is almost always a journal posted straight to the control account outside the AP module.
Tip: Always run the aging on the same date as the trial balance you are reconciling to, or you will chase a timing difference that is not real.
List every entry to the control account that did not originate in AP, plus any invoice or payment posted to the wrong period. Correct each one with a journal, not by forcing the balance.
For key suppliers, match the statement against your ledger for that vendor. Capture the statement lines as data first, then find invoices on the statement that are missing from your books, unapplied credits, and anything you show that they do not.
Record the reconciling items, the reason for each, and the correcting entry. A clean reconciliation is one where every difference is explained, not one where the number happens to be zero.
AP reconciliation sits at the close, which is why it usually lands on the people with the least spare time in the month.
Reconcile vendor statements through the month so nothing is missing at close, and keep the subledger clean enough that the tie-out is quick.
Own the subledger-to-GL tie-out and sign off that AP is complete and accurate before the trial balance is finalized.
Run the same reconciliation across many clients on different accounting systems, and need the vendor statements off PDFs fast to do it at volume.
Test AP for completeness, so the reconciliation working papers and the search for unrecorded liabilities are the evidence they ask for first.
Accounts payable reconciliation is the control that proves your recorded payables are complete and accurate. It agrees the total of the AP subledger to the AP control account in the general ledger, and it matches individual vendor statements against your ledger, so that every invoice you owe is recorded and nothing is recorded twice. Last updated July 2026.
There are really two reconciliations under the same name. The first is internal: the AP subledger, which is the detailed list of what you owe each vendor, has to equal the single AP control account figure in the GL. The second is external: a vendor sends a statement of what they think you owe, and you match it against your own records. Software helps with both, but the comparison and the correcting journals run in your accounting system. The part that slows teams down is getting the invoices and statements into structured data in the first place.
Reconciling accounts payable is a four-step routine. Run the AP aging at period-end and agree its total to the GL control account. Investigate any difference, which is usually a journal posted directly to the control account. Match key vendor statements against your ledger to catch missing invoices and unapplied credits. Then document every reconciling item with its cause and correcting entry. The goal is an explained balance, not a forced one.
| Step | What you compare | What it catches |
|---|---|---|
| Subledger to GL | AP aging total vs AP control account | Journals posted outside the AP module, wrong-period entries |
| Vendor statement | Supplier statement vs your ledger for that vendor | Missing invoices, unapplied credits, duplicates, disputes |
| GL to trial balance | AP control account vs trial balance | Consolidation and mapping errors |
| Cutoff review | Invoice dates around period-end | Liabilities booked in the wrong period |
AP reconciliation is the broad tie-out of your whole payables balance, subledger to general ledger. Vendor statement reconciliation is one part of it: matching a single supplier statement against your ledger for that supplier. You can have a perfect subledger-to-GL tie-out and still owe a vendor an invoice you never received, which is why statement reconciliation matters. The subledger tie-out proves your books agree with themselves; the statement reconciliation proves your books agree with the supplier.
The accounts payable subsidiary ledger, or AP subledger, is the detailed record of every open item you owe, broken down by vendor. The general ledger carries a single AP control account that should always equal the sum of the subledger. Reconciliation is the check that it does. When a debit balance appears in a vendor subsidiary account, it usually means a credit memo or an overpayment left the vendor owing you, which is a prepayment or a receivable rather than a payable and should be reviewed before the balance nets against other suppliers.
In most AP departments the same handful of causes explain nearly every difference.
Only the missing invoice understates what you owe, and that is the one auditors care about most. It is the reason the accounts payable audit procedures center on a search for unrecorded liabilities rather than on the invoices you already booked.
Get the statement into a spreadsheet, list your own open items for that vendor next to it, and work the differences in both directions. Every invoice on the statement should appear in your ledger; anything that does not is either a missing invoice to book or a dispute to raise. Every open item in your ledger should appear on the statement; anything that does not is usually a payment the vendor has not yet applied or a genuine timing difference. Capturing the statement lines as data is what makes this a lookup instead of an afternoon of reading. The same extraction runs behind our invoice matching software for the PO-based side of AP.
Reconcile the subledger to the GL every month as part of the close, without exception, because an unexplained AP difference distorts both the balance sheet and cash forecasting. Reconcile vendor statements on a risk basis: monthly for high-volume or high-value suppliers, and at least quarterly for the rest. Many teams also reconcile a vendor before releasing a large payment run, which is the cheapest time to catch a duplicate. For where reconciliation sits in the wider routine, see the month-end close checklist.
The matching can be, and the data capture that feeds it definitely can. Software can pull the subledger, agree it to the GL, and flag differences, and it can read vendor statements and line them up against your ledger. What it cannot do is decide whether a difference is a timing item or a real error, or whether a missing invoice is a dispute or an oversight. Automating the reconciliation should shrink the list of differences a person works, not pretend the list is empty. We are the layer in front of it: we turn the statements and invoices into structured data so the reconciliation has something clean to compare.
We do one job in this workflow and we are clear about its edges. We read vendor statements and invoices and return structured Excel, CSV, or JSON: vendor, invoice number, dates, amounts, and line items. That is the data your reconciliation compares. We do not post journal entries, hold your subledger, or run the tie-out itself, because those live in your accounting system. If you need the full automated AP cycle rather than the data layer, the accounts payable automation software page covers it, and best AP automation software compares the platforms honestly, including where each beats us.
Accounts payable reconciliation proves that your recorded payables are complete and accurate. It agrees the total of the AP subledger to the AP control account in the general ledger, and it matches vendor statements against your own ledger, so that every invoice you owe is recorded once and nothing is missing or duplicated.
Run the AP aging at period-end and agree its total to the GL control account. Investigate any difference, which is usually a journal posted outside the AP module. Match key vendor statements against your ledger to find missing invoices and unapplied credits. Then document every reconciling item with its cause and correcting entry, so the balance is explained rather than forced.
AP reconciliation is the broad tie-out of your whole payables balance from subledger to general ledger. Vendor statement reconciliation is one part of it: matching a single supplier statement against your ledger for that supplier. A perfect subledger-to-GL tie-out can still hide an invoice a vendor issued that you never received, which is why statement reconciliation matters.
Reconcile the subledger to the GL every month as part of the close. Reconcile vendor statements on a risk basis: monthly for high-volume or high-value suppliers and at least quarterly for the rest. Many teams also reconcile a vendor before a large payment run, which is the cheapest moment to catch a duplicate before it is paid.
You need the AP aging report as of the period-end date, the general ledger AP control account balance, and the vendor statements for the suppliers you are reconciling. Getting the statement and invoice data off PDFs and into a spreadsheet is the step that makes the match practical rather than a manual read.
The usual causes are a journal posted straight to the control account, a duplicate invoice entered under two numbers, an unapplied credit memo, a missing invoice the vendor issued but you never booked, a cutoff error, or a payment applied to the wrong invoice. Only the missing invoice understates the liability, and that is the one auditors test for first.
The AP subsidiary ledger is the detailed record of every open item you owe, broken out by vendor. The general ledger carries one AP control account that should always equal the sum of the subledger. Reconciliation is the check that the two agree, and a difference points to an entry that hit one but not the other.
The matching and the data capture that feeds it can be automated. Software can pull the subledger, agree it to the GL, read vendor statements, and line them up against your ledger. It cannot decide whether a difference is a timing item or a real error. Automation should shrink the list of differences a person works, not claim the list is empty.
No. We extract the vendor statement and invoice data and return it as structured Excel, CSV, or JSON, which is what your reconciliation compares. We do not post journal entries, hold your subledger, or run the tie-out, because those live in your accounting system. We remove the retyping that makes statement reconciliation slow.
The PO-based side of AP: 2-way and 3-way matching.
The full automated AP cycle, end to end.
Get every row a reconciliation needs, not just the total.
AP platforms compared honestly, including reconciliation.
