Vendor Statement Reconciliation: Finding the Invoices Your Ledger Never Saw

Vendor statement reconciliation is the process of comparing a supplier's own statement of account against your accounts payable subledger, categorizing every difference between the two balances, and closing each one with evidence.

It is the only AP control that can find an invoice you never received. Bank reconciliation compares your records to a bank's; three-way matching compares documents you already hold. A supplier statement is the single artifact in the process that comes from outside your four walls and lists transactions you may know nothing about.

Most AP teams run it reactively, when a supplier threatens to put the account on hold. That timing is the problem, because by then the difference is a credit conversation rather than an accounting one.

Key Takeaways

• The reconciliation exists to surface invoices the ledger never received, unapplied payments, and credits you never took.

• Every difference falls into one of five categories, and the category determines both the evidence needed and who has to act.

• An unmatched line is not an error until it has been categorized. Half of what looks alarming on first pass is timing.

• Reconcile by exposure rather than universally. A risk-ranked schedule beats an alphabetical one nobody finishes.

• Most differences are caused upstream, by invoices arriving on channels the ledger cannot see and by remittance detail that fails to travel with the payment.

What is vendor statement reconciliation, and how is it different from bank reconciliation?

Vendor statement reconciliation compares a third party's view of what you owe against your own, line by line, and resolves the gap. Bank reconciliation compares your cash records to a bank's record of the same transactions, which is a narrower job with a cleaner data source.

The difference that matters is asymmetry of knowledge. Your bank cannot know about a transaction you have not initiated. A supplier absolutely can, and routinely does, because they billed you for something that went to a warehouse manager's inbox and stopped there. The reconciliation is how that invoice becomes visible before it becomes a collections call.

What does the supplier's statement actually show?

Usually an opening balance, every invoice and credit note the supplier issued in the period, every payment they have applied to your account, and a closing balance, often with an aging summary attached. What it does not show is any invoice they issued and did not record, which is rarer than people assume but not zero.

Two properties make statements harder to work than they look. Statements are issued as of a cutoff date the supplier chose, which almost never matches your close date, so timing differences are guaranteed. And many suppliers send them as PDFs or images rather than data, so the first hour of a reconciliation is often transcription rather than analysis.

Which reconciliations does an AP team already run?

Several, and they answer different questions, which is why adding this one is not duplication:

• Payment reconciliation matches payments made against bank activity and remittance records, covered in the walkthrough of payment reconciliation

• Card reconciliation matches statement transactions to receipts and general ledger coding

• The AP control account reconciliation proves the subledger agrees with the general ledger

• Duplicate detection looks for the same invoice paid twice, which the piece on duplicate payment detection covers in depth

None of those can see an invoice that never entered your system. Only the supplier's own statement can.

Why do a supplier's balance and your ledger disagree?

Because both sides are recording the same commercial relationship from different vantage points, on different calendars, with different information about what has been shipped, received, disputed, or paid. Some of the gap is arithmetic and some of it is process failure, and the first job of the reconciliation is telling those apart.

Fraud research is the reason this control earns its place on the calendar rather than living in the nice-to-have column. Of 2,402 occupational fraud cases across 143 countries causing more than $3.4 billion in losses, asset misappropriation, the category containing billing schemes and check tampering, appeared in 90% of cases, with a median loss of $104,000 and a median 12 months before detection, according to the Association of Certified Fraud Examiners' Occupational Fraud 2026: A Report to the Nations. A fictitious supplier's statement never arrives, and an account that never gets reconciled never raises the question.

Detection patterns from the same study point the same direction. Tips remained the most frequent detection method at 43% of cases, while financial statement fraud appeared in 6% of cases at a median loss of $1 million. A control that depends on someone volunteering information is a control with a hole in it.

Which differences are timing?

Anything in flight on either side at the statement cutoff. An invoice the supplier issued on the 29th that reaches you on the 3rd. A check you mailed on the 28th that clears their lockbox on the 6th. A credit note raised after their cutoff and before yours.

Timing differences resolve themselves and should never generate work beyond a note on the sheet. The discipline is proving they are timing, which means having a date and a document, not an assumption. If the same invoice shows as a timing difference two statements running, it was never timing.

Payment rails shape how much of your difference sheet is timing. Checks accounted for 26% of B2B payments in 2025, down from 33% in 2022, according to the Association for Financial Professionals' 2025 AFP Digital Payments Survey. Every check in the mix adds float on both ends, which manufactures timing differences a faster rail would not create.

Which differences are real, and what causes them?

Four causes account for nearly all of them:

• An invoice arrived somewhere other than AP, went to the requester, and was never entered

• A payment was applied by the supplier to the wrong invoice, usually because remittance detail did not travel with it

• A credit or rebate was issued and never taken, which sits quietly because it favors the supplier

• A short pay or deduction was taken by you and not accepted by them, so both sides are right in their own records

The second cause is the most systematic and the most fixable. A payment that arrives as a lump sum with no remittance advice forces a cash application clerk at the supplier to guess which invoices it covers, and their guess becomes your reconciling item next month. Structured remittance data, the subject of the guide to remittance advice, removes that guess entirely.

How do you work a statement line by line?

Match on invoice number first, then on amount and date for anything that does not match on number. Everything that fails to pair after that pass goes on a difference sheet with a category, an owner, and a required piece of evidence.

What does the difference sheet look like?

Four columns, one row per unmatched item, and a category on every row. Here is the shape, with one worked example of each category:

Illustrative figures, internally consistent for example purposes. Not client data.

The categories are the entire value of the sheet. An uncategorized list of unmatched items is a to-do list; a categorized one routes itself, because each category has exactly one owner and one form of proof.

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 evidence closes each category of difference?

An invoice not received closes with a copy of the invoice plus proof of receipt of the goods or services, which usually means a delivery ticket or a signed acknowledgment, and then it enters the normal approval flow rather than getting paid off the statement. Payments not applied close with the payment reference and remittance detail sent to the supplier's cash application team.

A credit not taken closes with the credit memo and an entry, and it is worth chasing because unclaimed credits are pure recovery. A short pay closes only when the underlying dispute closes, which means it is not really an AP item at all. Duplicate payments close with a refund request or an offset against future invoices, and the causes are worth understanding separately, since duplicate payments usually indicate a control gap rather than a one-off error.

One rule saves more money than any other. Never pay directly off a supplier statement. A statement is a claim, not an approved payable, and paying from one bypasses three-way matching and the approval chain in a single step.

Which suppliers should you reconcile, and how often?

Rank by exposure, not by alphabet or by who complains loudest. Most AP departments have a few hundred active suppliers and time to reconcile maybe twenty properly, so the selection is the decision.

How do you rank suppliers by exposure?

Four factors, roughly in order of weight:

• Annual spend, because a percentage error is bigger on a bigger number

• Transaction count, since a supplier billing weekly has far more chances to diverge than one billing annually

• History of differences, which is the best single predictor of future differences

• Payment method and channel, since suppliers paid by check with no remittance data diverge more than suppliers paid electronically with structured remittance

Add a fifth judgment factor that no formula captures. Any supplier whose invoices routinely arrive outside the AP inbox belongs on the list regardless of spend, because the ledger is structurally blind to them. Vendor master hygiene sits underneath all of this, and the practices in vendor management best practices are what keep the ranking meaningful.

What cadence fits a small AP team?

Monthly for the top tier, quarterly for the middle, annually or on-demand for the tail. A two-person AP team can hold that schedule if the top tier is genuinely small, ten to twenty accounts, and if statements arrive on a predictable date.

The practical trick is asking suppliers to send statements to a dedicated address on a fixed cutoff. Most will, nobody thinks to ask, and it converts an unpredictable inbound flow into a scheduled task. Tie the cadence to your own close calendar rather than theirs, and skip a cycle deliberately when nothing has changed instead of letting it slip.

Worth an honest caveat. I have never seen a small team hold a universal monthly cadence for more than two quarters, and a schedule that quietly collapses is worse than a narrower one that holds, because everyone believes the control is running.

How do you stop the differences from happening?

Attack the two causes that produce most of the sheet. Invoices enter on channels the ledger cannot see, and payments arrive without the data needed to apply them. Both are structural, and both are fixable without adding headcount.

How does structured invoice capture close the missing-invoice gap?

By making the AP system the only front door and by turning every arriving document into data on receipt. When suppliers submit to one address and every invoice is captured, coded, and entered on arrival, the category "invoice not received" mostly disappears, because there is no second inbox for it to land in.

The productivity case is measurable. Companies with a touchless invoice-processing rate of 30% or higher average 3.5 times higher AP productivity, the evaluated platforms' customers averaged a 60% touchless rate, and AP cycle times improved 59% after implementation, according to The Hackett Group's Digital World Class Matrix for accounts payable. Touchless processing matters here less for the labor saving than for the completeness, since an invoice that enters as data at arrival cannot be the one nobody saw.

Capture also produces the audit record that makes a reconciliation defensible, which the piece on the AP audit trail covers from the compliance angle.

What does remittance detail travelling with the payment change?

It removes the supplier's guess, which removes your next reconciling item. When a payment carries invoice-level detail the supplier's system can consume, cash application happens automatically and correctly, and the "payment not applied" category stops appearing.

Rail choice decides whether this is possible. ACH carried 39.7 billion transactions worth $104.06 trillion in 2024, lifting its share of noncash payment value from 72% to 74%, per the Federal Reserve's 2025 Federal Reserve Payments Study, and B2B ACH volume grew 9.4% year over year to nearly 2.1 billion transactions in the first quarter of 2026, according to Nacha's Q1 2026 ACH Network volume statistics. The relevant property is the addenda record rather than the speed, since a check carries a stub that a human has to read.

Validated supplier banking belongs in the same conversation, because a payment sent to the wrong account creates a reconciling item and a loss at the same time. The controls are set out in vendor verification and banking validation.

Close the gap at the source with Corpay AP automation

The reconciling item that hurts, an invoice sitting in a requester's inbox for six weeks while the supplier's aging bucket moves right, is an intake failure that the reconciliation happened to catch rather than a reconciliation failure of its own. AP automation from Corpay closes it upstream by capturing every supplier invoice as structured data, routing it for approval, and paying by virtual card, ACH, or check with remittance detail attached to the payment.

Fully managed AP goes a step further by moving supplier-facing work off your team entirely. We enroll your suppliers, deliver the payments, handle the follow-up when something needs chasing, and simplify reconciliation on both sides of the relationship. Customers typically see about 40% time saved on payables work and go live in weeks. Card-based payments also return value rather than consuming it, with $800M+ in rebates paid to customers per year.

What does fully managed AP change about supplier queries?

It changes who answers them. Supplier calls about payment status, remittance detail, and application questions go to the managed service rather than to the AP supervisor who was going to spend that afternoon on the reconciliation. The reconciliation gets done because the interruption that usually kills it has moved.

There is a second-order effect worth naming. When suppliers get consistent answers from a team whose job is answering them, statements arrive on time and disputes surface earlier, which shrinks the sheet before you ever sit down with it. The broader process context lives in the guide to the accounts payable process.

Which ERPs does it connect to?

Corpay maintains 100+ ERP integrations, including NetSuite, Sage Intacct, Microsoft Dynamics 365 Business Central, and Acumatica, over API, SFTP, or file-based connections. For reconciliation purposes the question worth asking is narrower than the integration list. Ask how invoice-level remittance data is written back to the subledger, and ask to see it working at a company with your supplier count rather than in a demo tenant.

Auditors will ask a version of the same question. The evidence expectations are laid out in the accounts payable audit checklist.

Frequently Asked Questions

What is vendor reconciliation?

Vendor reconciliation is the comparison of a supplier's statement of account with your accounts payable records to identify and resolve differences. It confirms that both parties agree on what is owed, and it surfaces invoices, credits, and payment application errors your own records cannot reveal on their own.

What are the three types of reconciliation?

In an AP context the three most common are bank reconciliation, which matches cash records to bank activity, account reconciliation, which proves a subledger agrees with the general ledger, and vendor or supplier statement reconciliation, which compares your balance with a third party's. Each uses a different source of truth.

How do you do a vendor statement reconciliation in Excel?

Put the supplier's transactions in one sheet and your ledger's open items in another, match on invoice number with a lookup, then match remaining items on amount and date. List every unmatched line on a difference sheet with a category, an owner, and the evidence required to close it.

How often should supplier statements be reconciled?

Monthly for your highest-exposure suppliers, quarterly for mid-tier accounts, and annually or on request for the long tail. Ranking by spend, transaction volume, and history of differences matters more than frequency, because a narrow schedule that holds beats a universal one that lapses.

How is vendor statement reconciliation done in an ERP?

Most ERPs provide a vendor aging or open-items report that becomes the ledger side of the comparison, and some offer a statement import that automates the first matching pass. The categorization and evidence steps stay manual in nearly every system, which is why the difference sheet remains the working document.

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

Payments Automation