How Supplier Statement Matching Works: References, Amounts, Dates and Part Payments

What does a statement line get matched to?

You are comparing two lists. The supplier’s statement has a date, a reference, a description, a debit or a credit and usually a running balance. Your purchase ledger has the rows for that supplier, with whatever reference your team typed in. For each statement line you want to know whether a ledger row records the same thing. Sort both by amount first, because duplicates and swapped digits end up side by side.

The layout of the statement changes what “missing” means. A balance-forward statement lists the month’s invoices, payments and credits with a running balance. An open-item statement lists only what is still unpaid. On the first, a bill absent from the page is a real question. On the second it may simply have been paid and dropped off.

Next to each pairing, note which rule made it: reference and amount, amount and date, or a group. If someone reviews your work later, they can then question the rule and not only the tick.

What do you need in front of you before you match?

You need the statement as the supplier sent it, and your own side of the account for the same period. The five steps below are the whole routine in short form.

1. 1

   Get your side of the account

   Run the payables report for that one supplier, as at the statement date, not today.

2. 2

   Check the statement adds up

   Opening balance plus the lines should reach the closing balance. If it does not, a line has been misread or is missing from your copy.

3. 3

   Clean the references and sign the amounts

   Same case, no punctuation, credits and payments as negatives.

4. 4

   Pair the lines, strictest rule first

   Write the rule you used beside each pairing. The sections below set out the order.

5. 5

   Give every leftover a cause

   Timing, a missing document, a keying slip or a dispute. Then fix your side or query the supplier.

For your side of the account, Xero users start with Aged Payables Detail or Supplier Bill Activity, and QuickBooks Online users with Vendor Balance Detail or Transaction List by Vendor. We found all four names in Xero’s and Intuit’s own demo companies on 31 October 2026. Labels can differ by region, so check them in yours. The Xero and QuickBooks Online guides give the report choices in full.

How do the passes work, strictest first?

Every pass pairs what it can, takes those lines out of the pool, and passes the rest down. The figure at the end of each step below is how many of the nine statement lines are still unpaired. The same nine lines are drawn in full further down.

Why strictest first

Rules that go on amount and date alone are fine on a nine-line statement, where maybe one row fits. On a couple of hundred lines several rows will fit, and the rule has several candidates to choose from. That is why the exact reference matches are paired first. They come out of the pile, and the looser rules then have fewer similar rows to choose between.

When two lines look alike

AVP-008361 (8 Oct) and AVP-008369 (11 Oct) are both 947.75. With the references present, pass 1 pairs them. Blank the references and each fits both ledger rows within 7 days, so there is no safe pairing. Picking one could pay the wrong bill, which is why amount and date are accepted only when exactly one ledger row fits, and why two candidates are left for a person.

How do you match when the invoice number is spelled differently?

The reference is the only field both sides were meant to share, and it is the one people retype. On the example, two invoices pair on reference, and two do not: one is keyed 8342 and the other under a purchase order number.

Same invoice, different spelling

The supplier prints AVP-008342. Your clerk keyed 8342. It is the same invoice, and a plain string comparison says no. So clean both sides before comparing. Uppercase everything and drop punctuation and spaces. That is safe. Dropping the supplier’s prefix and leading zeros goes further, and some tools offer it, as the Unit4 row in the tolerance table below shows. Statement Zen cleans case and punctuation only, then compares exactly. It does not strip prefixes. It does treat a close reference as a hint, which the product section below explains.

Every cleaning step throws something away. With the prefix gone, 8342 is only four digits and could belong to any supplier. So treat a cleaned reference as a lead and let the amount confirm it. Pass 1 asks for the reference and the amount together for that reason, and AVP-008342 and 8342 pair here on amount and date instead.

When the reference is not the invoice number

On the example, the supplier’s invoice AVP-008357 sits in the ledger as PO-7156, because whoever keyed the bill put the purchase order number in the reference field. There is nothing to clean. AVP-008357 and PO-7156 share no token, so the reference rule has nothing to say.

The pairing falls to amount and date. The statement shows 3,120.00 on 5 October. The ledger has 3,120.00 on 6 October and no other row for that amount. One candidate, so it pairs. Mark it lower confidence. Correct the reference in the ledger.

It is a common keying habit. In a Xero Product Ideas thread (October 2026), a user said a statement-matching tool could not pair their invoices because the purchase order number sits in Xero’s reference field beside the supplier’s number. More on this in the guide to the problems that bad references cause.

What amount tolerance is safe?

Start at exact. A tolerance is for rounding and currency conversion, not for tidying differences you could explain. Every extra unit of tolerance lets in more strangers. Published settings range from exact to 10.00 and from 0 to 7 days (Unit4 sample, AutoEntry Find Match, read 30 October 2026).

Credits are negative

Suppliers print credit notes in a few ways: a separate credit column, brackets, CR after the amount, or a minus sign. Turn all of them into negative numbers before you compare anything. Then invoices and credits stay in separate piles, and a credit is never paired with an invoice, even when the amounts happen to agree.

A credit of 386.20 and an unrelated invoice of 386.20 net to nil and look settled when they are strangers. On the example, credit note AVC-002294 for 386.20 has no ledger partner. The guide on missing credit notes and duplicate payments covers the chase and has a query email you can send.

Same reference, different amount

AVP-008388 is 2,936.00 on the statement and 2,963.00 in the ledger. The reference agrees, so it is the same invoice, and the amounts do not. The difference is 27.00, and 27 is a multiple of 9. Swap two adjacent digits and the difference is always a multiple of 9; here the last two digits before the decimal are swapped. The reverse does not hold, since one random difference in nine divides by 9 too, so check the invoice copy before you call it a keying slip.

Not every gap is a keying slip. A short payment leaves a remainder that is a round sum, or a payment you can find in the bank statement. An early-payment discount of 2 percent leaves exactly 2 percent of the invoice. A price change shows on every line from that supplier, so look at three or four of their invoices before you blame one. Whichever it is, the line stays a difference until someone clears it, either with a credit note from the supplier or by paying the remainder if your terms never allowed the discount.

Tax and currency

If every line differs by the same percentage, stop hunting single errors. A statement that shows every line 20 percent above the ledger is tax-inclusive against a tax-exclusive ledger. Fix the basis, then rerun. Also check whether the statement is in the supplier’s currency while the ledger holds yours.

How much should dates count?

A date backs up a pairing but rarely makes one. Pass 2 only asks that the date fall inside a window, because the statement date, the date your ledger posted the bill and the day it reached your inbox can easily be a few days apart.

Which date is the invoice date

When a line carries a date and a due date, the invoice date is the date column, and the due date is later. Weigh three signals in order. First the column headers. Then the pattern down the page: which column is always the older one? Only then position, because “leftmost” is a habit of layout, not a rule. The due date is not evidence of when the invoice was raised, so do not test timing against it.

On the example statement the terms are 30 days, so every due date falls 30 days after its invoice date, and the due date has a column of its own. The mockup further down puts it in the description to save width. On a row or two, a supplier may have entered a due date that is earlier than the date. If the headers and the rest of the page agree on which column is which, one odd row does not change the answer. Some statements print a due date and no invoice date at all. Then the due date is all you have. Show it, label it as a due date, and keep it out of any check on whether a line is late or outside the period. The module on date and amount differences works through more layouts.

The window

Demanding the same day rejects good pairings. On the example, the supplier shows our first payment on 14 October and the ledger posted it on 13 October. The second is 27 October against 26 October. One day apart, both times, and nothing wrong.

The tools we read allow up to 3 or 7 days. We use 7. A window of 30 days would take in most of a month’s invoices from the same supplier, and then a matching date proves nothing.

Day and month swaps

A printed 05/11 is 5 November in a day-first country and 11 May in a month-first one, 178 days apart. If a pairing is clean on reference and amount but the dates are months apart, test it directly: reverse day and month on the printed date. If the reversed date equals the other side exactly, treat it as a swap and say so. Only a date with day and month both 12 or under can be swapped, and it changes nothing when day equals month.

Cut-off

Check the date against the statement date before you call a line missing. A ledger bill dated after the statement date cannot be on it, so it is not missing; it is timing. AVP-008402 is the other way round: dated 29 Oct, two days before the 31 Oct statement date, and not in the ledger. It may simply not be entered yet, so check the approval queue and the inbox it was sent to. It is a timing difference until the supplier says otherwise.

How are part payments and payments on account matched?

Each side records a payment on its own day and sometimes against different invoices, so payments need more care than invoices do. The cases below are the ones that come up most.

One invoice, two payments

On the statement there is invoice AVP-008357 for 3,120.00, followed by two payments, one in each half of the month. In your ledger it looks the same: one bill, two payments. The payments go in with the credits, away from the invoices, so a payment line can only ever pair with another payment row. Once those are paired, check that they add up to the invoice they name.

The group check only works when each payment line carries the invoice number. A payment printed as “Payment received” with no reference can be one of several invoices, and a total on its own proves nothing. In that case ask the supplier for the remittance allocation.

One payment, several invoices

You paid once and the supplier spread it over three invoices, perhaps not the three you meant. Pair the payment by its total first. Then see which invoices the supplier applied it to and compare that with your remittance. If the supplier applied it differently, the total still agrees but the ageing is wrong: an invoice you thought was paid is still open on their side. That is how it goes unnoticed until someone looks at the ageing report.

How your ledger shows a part payment

Your own system decides what a part payment looks like. Here is how Xero and QuickBooks Online show it, and one pattern we see in Vista data.

Payment in transit

A payment in your ledger and not yet on their statement is timing, not an error. Note the payment date and the bank reference, and look for it on the next statement.

What happens to each of the nine lines?

Take Brackenwold Packaging Ltd, a supplier we made up, and its October 2026 balance-forward statement to Fennimore Bakeries Ltd. It closes at £6,590.20, while the purchase ledger has £7,419.30 for the same supplier. We matched it by hand first, using the reference cleaning and the 7-day window from above, and then fed the same nine lines to Statement Zen’s matching code, which landed on the same pairings. Its output follows the comparison of each line with the ledger.

We ran the nine lines and eight ledger rows through Statement Zen’s matching code on 30 October 2026, locally and in line mode. That mode works from the extracted lines alone, and the payments and the credit note were entered as negative amounts. AVP-008361 and AVP-008369 came out as clean matches. AVP-008342, AVP-008357 and the two payments were date corroborated, each paired on amount and date. AVP-008388 was an amount variance of 27.00, AVC-002294 a credit on account, AVP-008402 statement only and AVP-008395 ledger only. Every pairing matches the hand method, except that the code pairs the two payments one by one and leaves the check against AVP-008357 to you.

Three of those four steps are yours to fix. Correct the swapped bill, post the credit note once it arrives, and enter the invoice once it clears approval. That moves the ledger by 245.20, to 7,664.50. The last 1,074.30 is one bill the supplier has not shown, and only the supplier can explain it.

Why does a line fail to match?

• A scanned statement with a misread digit. A scan can turn a 3 into an 8. If a reference fails to pair and the amount is exact, look at the page itself before you blame the ledger.
• An invoice emailed to someone who left. The statement lists it and your ledger never saw it. Nothing is wrong with the matching there; the invoice is missing.
• Payments posted on account and never allocated. The ledger shows an open bill and a floating payment. The statement shows the bill paid. Allocate the payment, and the two lists line up.

How does Statement Zen match?

Statement Zen follows the same ladder with some differences. As of 30 October 2026 it tries each statement line in this order, and uses each ledger row once. Invoices pair with invoices, and payments and credits with payments and credits.

1. Same reference and same amount to the cent, after case and punctuation are removed. A pair with the same date is a clean match, and a pair one day or more apart is filed as a date difference.
2. Same amount and a date within 7 days. One ledger row fitting is enough to pair, and if several fit, the one with a close reference is paired. Otherwise the line is listed as an ambiguous match with its candidates for a person to choose.
3. Same amount and a close reference, with no date needed: the same four or more digits under a different prefix, or one character out. These are filed as a fuzzy reference for you to check.
4. Same reference, different amount. A gap of up to 35 percent of the larger figure is an amount variance. A bigger gap where the ledger holds less is filed as part paid. Where the ledger holds more, the pair stands only if the dates are within 7 days.
5. Groups. One statement line equal to the sum of two to four ledger rows, or one ledger row equal to the sum of two to four statement lines. Rows must be the same kind, dated within 14 days of the line. If more than one combination fits, nothing is paired.

Whatever is left is listed as on their statement only, or in your ledger only. Statement Zen never pairs on amount alone, and it does not strip supplier prefixes.

Two things differ from the hand method above. Payment lines are paired with ledger payments on amount and date, like any other line, so checking that your payments add up to the invoice they name stays with you. The group step looks only at sums and dates, not at invoice numbers. The one place payment lines are read by invoice number is the explanation of why your ledger holds less than the statement bills, where it uses payment lines that carry that invoice number and add up exactly to the gap.

Each line then gets a category, such as clean match, amount variance, statement only or ledger only. You can try it on your own statement on the free reconciliation page.

It works with Xero, QuickBooks Online and Vista.

Questions people ask

Sources

• CFO.com: Percentage of error-free disbursements, Metric of the Month (citing APQC) (dated 5 Feb 2025), read 30 Oct 2026
• Unit4 ERP Apps statement extension configuration, matching settings, read 30 Oct 2026
• AutoEntry Help Centre: Supplier Statement won’t reconcile, read 30 Oct 2026
• Xero Central: Apply a supplier’s credit to a bill, read 30 Oct 2026
• Xero Central: Record payment of a bill (NZ page), read 30 Oct 2026
• Intuit: Apply vendor credits to a bill in QuickBooks Online, read 30 Oct 2026
• Xero Product Ideas: supplier statements thread, read 30 Oct 2026

What changed

• 30 Oct 2026: First published, with the nine-line worked example.
• 31 Oct 2026: Shortened by removing repeated tables and explanations.
• 31 Oct 2026: The CFO.com source now shows the date we read it, with its publication date in its name.