<img src="https://secure.coat0tire.com/221997.png" style="display:none;">

 

Supplier statement matching compares a supplier's account statement against your purchase ledger to identify discrepancies in invoices, credit notes and payments. Done with automation, it takes minutes per supplier. Done manually, a single reconciliation takes 30-90 minutes and still misses errors buried in mid-tier accounts.

Most AP teams already know they should be doing this. Most are not doing it consistently, and that is where the money goes.

Often, teams will reconcile supplier statements either too infrequently or too manually or both. The result is the same in every case: duplicate payments that should not have happened, credits that expired before anyone claimed them and month-end closes that run late because nobody spotted the gap until the last minute.

This guide explains exactly how supplier statement matching works, step by step, and where the process tends to break down.

What is supplier statement matching? 

Supplier statement matching is the comparison of two records of the same transactions:

  • The supplier's statement: a document the supplier sends (usually monthly) showing every invoice, credit note, and payment on your account from their perspective.
  • Your purchase ledger: your internal record of the same transactions, invoices received and posted, credit notes claimed, payments made.

In a world where both sides agree, every line matches. In practice, they rarely do, and the gaps are where the money leaks.

For a full definition of the broader process this sits within, see our guide to supplier statement reconciliation.

 

Why do discrepancies happen?

IOFM research found that 84% of the typical AP practitioner’s day goes on manual tasks. When the team is already stretched, statement matching is the first thing that gets skipped, and the errors build up quietly in the background. Before explaining the matching process, it helps to understand what causes the differences in the first place. There are four common sources:

Timing differences

You posted a payment on 28th March. Your supplier did not receive it until 2nd April. Both records are correct; they cover different date ranges.

Missing invoices

The supplier has an invoice on their statement that you have never seen. It was emailed to a leaver, got lost in a shared inbox or never sent correctly in the first place.

Unclaimed credit notes

The supplier issued a credit against a returned order or a pricing dispute. It is sitting on their statement. Your ledger does not know about it because nobody raised it internally.

Duplicate postings

The same invoice appears twice: once from the original, once from a chasing copy the supplier resent when they had not heard back. Both got posted. Neither got matched.

Each of these has a different resolution path, which is why the matching process matters.

How supplier statement matching works: the process step by step 

Step 1: Receive the supplier statement

Statements arrive by email (usually PDF), through a supplier portal or occasionally by post. The first challenge is getting them all in one place consistently. Many AP teams spend 20-30% of their reconciliation time just collecting statements before any matching begins.

Step 2: Extract the line-item data

Each statement contains individual transaction lines: invoice numbers, invoice dates, values, credit notes and running balances. To match against your ledger, you need this data in a comparable format, not a PDF you are reading against a screen.

Manual extraction means re-keying data from the statement into a spreadsheet. Automated extraction reads the PDF and pulls the data directly, eliminating transcription errors before the matching even starts.

Step 3: Pull your purchase ledger data for the same period

You need your own record of every transaction with that supplier for the same period: invoices posted, credit notes applied, payments made, anything on hold. Most ERP or accounting systems can export this easily; the problem is usually that the export format does not naturally align with how the supplier presents their data.

Step 4: Match the records

Line by line, you are looking for transactions that appear on both sides and agree on value and reference. Three outcomes are possible for each line:

  • Matched: Invoice number, amount and date agree on both sides. Nothing to do.
  • Timing difference: Transaction appears on one side but not the other because of a cut-off date. Note it, confirm it will clear in the next period and move on.
  • Genuine discrepancy: Transaction appears on one side only or the values do not agree. This needs investigation.
  • Does the missing invoice or credit note exist and should it be on your ledger?
  • Is the value difference a pricing error, a partial payment or a data entry mistake?
  • Is this a duplicate that needs a write-off request or a legitimate outstanding balance?
  • Post a missing document: Raise the invoice or credit note on your ledger if it is legitimate.
  • Raise a dispute with the supplier: If their record is wrong, notify them and request a corrected statement.
  • Confirm and close: If the difference is a timing item that will resolve naturally, document it and mark it for follow-up in the next cycle.

The first two categories close quickly. The third is the actual work, and it is where the errors and the money are.

Step 5: Investigate discrepancies

For every genuine discrepancy, you need to establish:

At this point your team goes back to the supplier, checks original documents or raises queries internally with procurement or the receiving team.

Step 6: Resolve and clear

Once a discrepancy has been investigated, it gets resolved in one of three ways:

Step 7: Confirm the closing balance

When all discrepancies are resolved or documented, the closing balance on the supplier's statement should agree with the balance on your purchase ledger. That confirmed balance is the sign-off that the reconciliation is complete.

Manual vs automated: what changes at each step

The steps above apply whether your team does this by hand or with automation. What changes is the time, the accuracy and the coverage.

Step

Manual process

Automated process

1. Receive statements

Chased by email, collected across multiple inboxes

Statements received and loaded automatically

2. Extract data

Re-keyed from PDF into spreadsheet

PDF read and data extracted directly, no re-keying

3. Pull ledger data

Exported from ERP, reformatted manually

Pulled directly from ERP in a consistent format

4. Match records

VLOOKUP or manual line-by-line comparison

Automated matching, exceptions flagged instantly

5. Investigate discrepancies

Human review (same as automated)

Human review, with full document context available

6. Resolve and clear

Updated manually in ERP or spreadsheet

Resolved in-platform, audit trail created automatically

7. Confirm closing balance

Calculated manually, signed off by hand

Auto-calculated, available on dashboard in real time

Steps 1 to 4 and step 7 are where automation removes the bulk of manual time. Steps 5 and 6 still need human judgement: automation surfaces the exceptions, your team resolves them.

For the commercial case for automating the process, including the cost-of-doing-nothing argument and real-world recovery outcomes, see our guide to the benefits of automated statement reconciliation.

How long should reconciling supplier statements take?

For a single supplier with a clean account, a manual reconciliation takes 30-90 minutes, depending on statement volume and how well your ledger data exports. Multiply that across a supplier base of 50-200 active accounts and you are looking at significant AP time every month. Ardent Partners’ State of ePayables 2024 report found that businesses without automation take an average of 17.4 days to process a single invoice. Statement matching is part of that same manual burden, and the time cost compounds in the same way.

Open ECX's automated Statement Reconciliation tool matches statements in seconds. Human time is spent only on genuine discrepancies that need a decision, not on re-keying data or running VLOOKUP formulas. That matters more than it sounds: IOFM research puts the manual invoice error rate at 39%, meaning nearly 4 in 10 statements will contain something worth finding.

What good statement matching looks like in practice

Most teams discover the same thing when they first automate: suddenly they are reconciling their entire supplier base in the time it used to take to do a handful. The financial impact follows quickly.

The most consistent finding in that first full reconciliation run is unclaimed credit notes: credits that were issued by suppliers, never spotted, and left to expire. For a business with 100+ active supplier accounts, it is common to recover five figures in the first quarter of comprehensive reconciling, credits that had been sitting on supplier statements unactioned for months.

That is not an edge case. It is what happens when a process that was being skipped starts getting done properly.

Supplier statement matching vs purchase ledger reconciliation: what's the difference?

These terms are sometimes used interchangeably, but they describe different scopes.

Purchase ledger reconciliation is a broader internal process: checking that your purchase ledger is accurate, complete and correctly reflected in your management accounts. It includes aged creditor reviews, accruals and period-end checks.

Supplier statement matching is specifically the comparison of your records against a supplier's external statement. It is one input into a complete purchase ledger reconciliation, but it is distinct from the broader close process.

Common mistakes in the supplier statement matching process

Only reconciling high-value suppliers

Most duplicate payments and unclaimed credits sit in mid-tier accounts that do not get the attention high-value strategic suppliers do. Reconciling only the top 10 suppliers by spend misses the majority of the risk.

Reconciling at year-end only

Annual reconciliation finds the errors too late to prevent them. Monthly reconciliation prevents them compounding.

Treating timing differences as resolved

A timing difference noted in March and not followed up in April becomes an unexplained variance in May. Timing items need a documented expected clear date and a chase process.

Accepting 'close enough' balances

A £50 difference on a £200,000 account does not feel worth chasing. But the same error pattern across 30 suppliers adds up, and it is usually a symptom of a systemic posting problem.

Frequently asked questions

What is supplier statement matching?

Supplier statement matching is the process of comparing a supplier's account statement against your purchase ledger to identify and resolve discrepancies in invoices, credit notes, and payments. It ensures both sides agree on what is owed and surfaces any credits or overpayments before they expire.

How often should you reconcile supplier statements?

Monthly is the standard for active supplier accounts. High-volume or high-value accounts may warrant more frequent review. Annual-only reconciliation leaves errors to compound and credits to expire unclaimed.

What are the most common discrepancies found during supplier statement matching?

The most common are missing invoices (never received or posted), unclaimed credit notes, duplicate invoice postings, and timing differences where a payment is recorded in different periods by each party.

Can supplier statement matching be automated?

Yes. Automated supplier statement matching extracts data from supplier PDFs, matches it against your purchase ledger, and categorises each line as matched, timing difference, or discrepancy, flagging only the exceptions for human review. IOFM research shows that 39% of invoices contain errors, which means comprehensive automated matching consistently surfaces discrepancies that manual spot-checking misses. Open ECX's Statement Reconciliation tool does exactly this, and it connects directly to your existing ERP.

What's the difference between supplier statement matching and a statement reconciliation?

They describe the same process. 'Reconciling supplier statements' is the common operational phrase; 'supplier statement matching' tends to be used when describing the specific line-by-line comparison step within the broader reconciliation workflow.

What happens if a discrepancy can't be resolved?

Unresolved discrepancies should be documented with a reason, escalated if above a threshold value, and reviewed in the following period. Persistent unresolved items are typically a sign of a process gap, either in document receipt, posting accuracy, or supplier communication.

 

Get in touch

 

See our other News stories

Are you ready to transform your P2P and O2C processes?

Get in touch

Tell us about your business needs and one of our experts will be in touch to arrange a personalised demonstration of how our award-winning P2P and O2C automation solutions can revolutionise your processes.

Contact Us