Accounts Payable Reconciliation: How to Tie AP to Your GL, Bank, and Vendor Statements

Accounts payable reconciliation is the process of confirming that what your AP subledger says you owe agrees with your general ledger, that what you paid agrees with your bank statement, and that your open balances agree with what each supplier says you owe them. Three tie-outs, run in that order.

Most reconciliation guides cover the first one and stop. The second and third are where the close week actually goes, because a subledger-to-GL difference is arithmetic and a vendor disagreement is an investigation. The wider view of payment reconciliation across AP and cards is the parent topic; this walks the AP side end to end.

Key Takeaways

• AP reconciliation covers three distinct tie-outs, and running them out of order means investigating differences that would have resolved themselves.

• AP reconciliation and bank reconciliation are different exercises. Bank reconciliation covers all cash movement; AP reconciliation covers obligations and the payments made against them.

• Most exceptions fall into six named categories, and each has a specific detection signal and a specific clearing action.

• Reconciliation is a detective control that catches what approval workflows structurally cannot, including a bank account changed between approval and payment.

• Payment rail choice is the single upstream decision that most changes downstream reconciliation effort.

• Automation removes the tie-out keystrokes and leaves the exception judgment exactly where it was.

What is accounts payable reconciliation?

Accounts payable reconciliation is the periodic verification that the AP subledger, the general ledger control account, the bank record of payments made, and supplier statements all describe the same set of obligations. It runs as part of close, and it's the point where every upstream shortcut becomes visible.

This covers the AP side only. Card-spend reconciliation follows different mechanics because the statement, not the invoice, is the primary document, and corporate card reconciliation handles that workflow separately. Mixing the two in one procedure is a reliable way to make both harder.

Account reconciliation in general is a control activity. What makes AP distinctive is the third party. Your bank will not disagree with you about what cleared, but a supplier absolutely will disagree about what's outstanding, and resolving that disagreement is a relationship exercise as much as an accounting one. The upstream flow is covered in the accounts payable process guide.

What has to tie out, and to what?

Three comparisons, each with a different authoritative record.

The AP subledger total ties to the general ledger AP control account balance as of the same date. The payment register ties to the payments shown clearing on the bank statement, adjusted for items in transit. And each supplier's open balance in your ledger ties to the balance on their statement, invoice by invoice for any account with activity.

How is AP reconciliation different from bank reconciliation?

Bank reconciliation compares your cash account to the bank's record of all cash movement, including receipts, fees, interest, and payments from every source. AP reconciliation compares what you owe suppliers and what you've paid them, which is a subset of cash activity plus a large body of obligations that haven't touched cash at all.

The two overlap at exactly one point, the payments leg, and that overlap is why they get confused. An outstanding check appears in both exercises and means slightly different things in each. In bank reconciliation it's a reconciling item against cash. In AP reconciliation it's a payment your ledger considers made and your supplier considers unreceived, which is a customer-service problem waiting to happen.

Who owns it, and how often should it run?

The AP manager executes the reconciliation and the controller signs off, which is the segregation that makes the sign-off meaningful. Monthly is the minimum, aligned to the close calendar.

Higher-volume teams get better results from a rolling weekly tie-out on the subledger and bank legs, leaving the vendor-statement leg monthly. The reason is investigative rather than procedural. A discrepancy found four days after it happens is usually traceable to a specific action someone remembers; the same discrepancy found five weeks later is an archaeology project.

How do you reconcile accounts payable step by step?

Work the three tie-outs in order, because the subledger-to-GL comparison establishes whether you have a systemic problem before you spend time on individual items.

1. Close the period's AP entries and pull the AP aging as of the reconciliation date.

2. Pull the trial balance and compare the AP control account to the aging total.

3. Document the difference in total before investigating any individual item.

4. Match the payment register against the bank statement, separating cleared items from items in transit.

5. Request or download supplier statements for accounts with material activity, and match them invoice by invoice.

6. Classify every remaining difference into a named exception category and assign an owner and a clearing action.

7. Prepare the reconciliation summary with supporting detail, and have the controller review and sign.

Step three is the one teams skip, and skipping it costs the most time. Knowing the total difference before you start investigating tells you whether you're hunting for one $14,000 item or for two hundred small ones, and those are completely different afternoons.

How do you tie the AP subledger to the general ledger?

Run the trial balance and the AP aging as of the same date, then compare the aging total to the AP control account balance. A clean tie means every invoice and payment posted to the subledger also posted to the ledger, at the same value, in the same period.

When they disagree, the usual causes are manual journal entries posted directly to the control account, invoices entered in one period and paid in another across the cutoff, and foreign currency revaluation where multi-currency payables exist. Check for direct journal entries first, because it's the fastest to test and the most common. Design decisions upstream in the invoice approval workflow determine how many invoices sit in ambiguous states at cutoff.

How do you reconcile AP payments against the bank statement?

Match each payment in the register to a bank transaction, then classify whatever's left as outstanding, in transit, or unexplained. Outstanding and in-transit items are timing; unexplained items need investigation before the reconciliation is signed.

Two mechanics make this harder than it sounds. Batch settlement means a single bank debit can represent dozens of invoices paid to dozens of suppliers, so the match is one-to-many and depends on a remittance file you can actually read. And cutoff creates a permanent population of items that exist in one record and not the other, which is normal and only becomes a problem when nobody distinguishes normal timing from a genuine break.

Check volume is the aggravating factor here, since a check can sit uncashed for weeks. The true cost of paper checks includes this reconciliation drag, which rarely appears in the cost comparison anyone actually runs.

How do you reconcile a vendor statement?

Pull the supplier's statement, match it line by line against your open items for that vendor, and classify each difference by type rather than by amount. Type determines who fixes it; amount only determines urgency.

Five difference types cover nearly everything:

• Timing, where a payment is in transit and hasn't reached the supplier's ledger yet

• A missing invoice, where they billed and you never received it or never entered it

• A short pay, where you deducted something deliberately and didn't tell anyone

• An unapplied credit memo sitting on one side of the relationship and not the other

• A duplicate, where the same invoice exists twice under different numbers

The matching discipline that prevents the second and fifth types is covered in three-way matching.

Protect cash flow with modern AP

Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.

Download the whitepaper

What causes reconciliation exceptions, and how do you clear them?

Six categories cover the great majority of AP reconciliation exceptions. Each has a characteristic detection signal, which is what makes a structured exception log more useful than a list of unexplained amounts.

Detection signals assume the subledger and GL close on the same date.

Why do timing differences show up between the bank and the subledger?

Timing differences exist because payment initiation and payment settlement happen on different days, and cutoff falls somewhere between them. Checks sit in the mail and then in someone's drawer. ACH settles on a defined schedule rather than instantly. And a payment run released on the last day of the month almost never clears in the same month.

None of that is a problem in itself. It becomes a problem when the reconciliation doesn't separate expected timing from genuine breaks, at which point a growing reconciling-item balance hides the one item that actually matters.

How do you find duplicate and misapplied payments?

Sort by vendor and amount and look for pairs, then sort by invoice number and look for near-matches. Duplicates that survive both passes usually involve the same invoice entered under two slightly different numbers, an invoice paid once against a PO and once standalone, or two vendor records for the same supplier.

Misapplied payments have a distinctive signature worth knowing. AP teams working in bank portals maintain large libraries of payment templates, sometimes well over a thousand, and selecting a neighboring template sends a correct amount to the wrong supplier. The ERP often won't flag it because the payment matched an approved amount, and the approver misses it because the vendor names look alike. It surfaces at reconciliation, which is precisely why the reconciliation exists. The structural fix is a unique vendor identifier in the match rather than a name, plus a second verification step on template selection.

What do you do when the vendor statement and your ledger disagree?

Decide which record is authoritative for each line type, document the decision, and escalate anything that survives two cycles. Your ledger is authoritative on what you paid and when. Their statement is authoritative on what they billed.

The item that survives two cycles is the one to watch, because a difference nobody can resolve in two months is usually either a systemic intake failure or something that should have been written off a year ago. Auditors will find it either way, and the accounts payable audit guide covers how that conversation goes when the aging of the reconciling items is the first thing requested.

How does reconciliation catch payment fraud?

Reconciliation is a detective control, which means it catches what preventive controls structurally cannot. An approval workflow confirms that an invoice was authorized; reconciliation confirms that the money landed where the ledger says it did. Those are different questions, and fraud lives in the gap between them.

The exposure is well documented. AFP's 2025 Payments Fraud and Control Survey Report found 79% of organizations were victims of attempted or actual payments fraud in 2024, with checks targeted by 63% of respondents and wire transfers also reaching 63%, up sharply from 39% in the prior survey. The FBI Internet Crime Complaint Center's Internet Crime Report 2025 recorded more than $3.04 billion in reported business email compromise losses, with 86% of those losses moving by wire transfer or ACH.

What does a reconciliation review catch that an approval workflow misses?

It catches everything that happens after approval. A payment redirected to a different account, an amount altered between approval and release, a second payment against an already-paid invoice, and a payment to a vendor record created after the approval was granted.

That's the whole argument for reconciliation as a control rather than as bookkeeping. The AP fraud patterns that succeed almost all involve a step after the approval, because the approval is the part everyone watches.

How do you spot a changed vendor bank account during reconciliation?

Compare the payment destination on record against the last verified banking detail for that supplier, and flag every change that occurred between approval and payment. A legitimate bank change has a verification record behind it; a fraudulent one has an email.

The attack pattern is specific and worth recognizing. Attackers wait for a real invoice in an active email thread, reply within it with updated banking details, and ask for processing before month end. The urgency is the tell, and so is the timing, since the request arrives after the invoice was already legitimate. The vendor email compromise breakdown covers how the thread hijack works in practice.

What changes when reconciliation is automated?

Automation removes the tie-out keystrokes and leaves the exception judgment where it was. Matching, aging, and variance calculation are mechanical and automate cleanly. Deciding whether a vendor's statement or your ledger is right about a three-month-old short pay is not mechanical and never will be.

The working-capital stakes justify the effort either way. The Hackett Group's 2025 Working Capital Survey found $1.7 trillion trapped in excess working capital across the top 1,000 US publicly traded nonfinancial companies, equal to 35% of gross working capital, and a reconciliation process that can't close cleanly is one of the reasons payables balances drift.

How does your payment rail choice change reconciliation effort?

Each rail produces a different reconciliation artifact, and the differences are large. Check payments create an indefinite outstanding population, because a check clears when the recipient decides it clears. ACH settles on a known schedule with a predictable in-transit window, which makes timing differences boring rather than mysterious. Wire transfers clear same day and reconcile trivially, at a per-transaction cost that limits where you'd use them. Virtual cards reconcile against an authorization with a known amount, merchant, and date, which is the cleanest match of the four.

Volume is moving toward the rails that reconcile easily. US noncash payments reached 236.6 billion in 2024, with ACH's share by value approaching three-quarters for the first time, according to the Federal Reserve's payments study findings. The reconciliation benefit of that shift rarely appears in anyone's business case, which is a shame, because it's one of the more reliable returns.

How does ERP integration remove the manual tie-out?

A real integration writes payment status, cleared dates, and GL coding back into the ERP automatically, which eliminates the export-and-match step that consumes most reconciliation hours. A shallow integration moves a file and leaves the matching exactly where it was.

The distinction is worth testing during an evaluation rather than accepting from a feature list. Ask what specific fields write back, in which direction, on what trigger, and what happens when a write-back fails. Corpay supports 100+ ERP integrations by API, SFTP, or file-based connection, covering NetSuite, Sage Intacct, Business Central, and Acumatica, with QuickBooks also supported. The ERP explainer covers where the system-of-record boundary sits, and reconciliation during an AP automation ERP migration is its own difficult exercise worth planning separately.

What should you measure to know reconciliation is working?

Three numbers. Exception count and its aging, days to complete the full tie-out, and the unreconciled balance carried forward from period to period.

The carried-forward balance is the one to watch, because it's the only one that compounds. A reconciliation that closes on time every month while its carried-forward balance grows is not working, and that pattern shows up in the accounts payable turnover ratio and in days payable outstanding before anyone names it out loud. Median DPO sits around 40 days across industries, with the 75th percentile near 50 and the 25th near 30, according to APQC Open Standards Benchmarking data reported by CFO.com. A DPO drifting upward without a policy change behind it is often a reconciliation problem wearing a working-capital costume.

How Corpay simplifies AP reconciliation across rails and your ERP

The reconciliation work that never gets easier through effort alone is the supplier side, because it depends on enrollment quality and payment follow-up that nobody has time for during close. Handing that layer to a managed service changes the exception volume rather than the exception handling.

Corpay runs fully managed AP across virtual card, ACH, and check. Supplier enrollment, payment delivery, and follow-up on undelivered or disputed payments sit with Corpay, which removes a large share of the exceptions that would otherwise arrive at your reconciliation as unexplained items. Customers typically save about 40% of AP team time, and a settled batch reconciles as one transaction rather than as a pile of individually cut payments.

The tie-out itself depends on the connection. Corpay's ERP integrations write payment status and coding back automatically so the subledger and the ledger stop diverging between closes, and payments automation handles the rail mix that determines how much timing noise you inherit. The AP automation overview covers the full scope, and managing accounts payable effectively covers the process side that no platform fixes for you.

Frequently Asked Questions

What are the stages of accounts payable reconciliation?

There are three stages plus a sign-off. Tie the AP subledger to the general ledger control account, match the payment register to the bank statement, then reconcile open balances against supplier statements. The controller reviews and signs the completed reconciliation with its supporting exception detail.

What journal entry is made when accounts payable is reconciled?

Reconciliation itself generates no entry when everything ties. Entries arise from what it finds, such as recording a previously unentered invoice as a debit to expense and a credit to accounts payable, reversing a duplicate, or applying an unrecorded credit memo. Each correcting entry should reference the reconciliation that produced it.

How often should accounts payable be reconciled?

Monthly at minimum, aligned to the close calendar. High-volume teams benefit from a weekly rolling tie-out on the subledger and bank legs, because discrepancies found within days are far easier to trace than the same discrepancies found after five weeks.

What is the difference between AP reconciliation and bank reconciliation?

Bank reconciliation compares your cash account to the bank's record of all cash movement. AP reconciliation compares what you owe suppliers and what you've paid against those obligations, which is a subset of cash activity plus obligations that haven't touched cash. They overlap only at the payments leg.

How do you reconcile accounts payable in an ERP?

Run the AP aging and the trial balance as of the same date from within the ERP, compare the aging total to the AP control account, and investigate the difference at the invoice level. Where an AP platform sits alongside the ERP, the quality of the write-back integration determines whether this is a report comparison or a manual export-and-match exercise.

What is an acceptable number of open reconciliation exceptions?

There's no universal number, since it scales with invoice volume and supplier count. The meaningful test is whether the exception population is stable or growing, and whether any individual item has survived more than two reconciliation cycles without resolution.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

AP Automation