Vendor Reconciliation: What It Covers and How to Run It

What does vendor reconciliation cover?

It looks like one task. It's five checks, and each one finds what the others miss. Read the 'Cannot catch' column first. A program that runs one check and assumes it covers the rest has a hole in it.

The words change by country but the documents don't. US teams say vendor, credit memo and check. In the UK and Australia you will hear supplier, credit note and cheque, and the vendor's statement is often called a statement of account. If you work across regions, there is a side-by-side list of UK, US and AU terms in the Academy.

Why does AP reconciliation start with the control account?

Start at the control account, before you open a single vendor. On the same date, the AP control account in the general ledger should equal the total of every vendor balance in the AP subledger. When it doesn't, any vendor-level work you do is built on numbers that disagree with the books you report from.

When AP and the GL disagree, it is usually for a dull reason. Someone posts a manual journal straight to the control account because tracking down the vendor was taking too long. A payment batch reaches the GL on the 31st but isn't applied to the vendor until the next morning. Now and then a bill goes to the wrong control account, or the two reports were run for different dates. The Bellhaven tie-out at 31 October 2026, just below, has the first two of these.

The gap is $1,314.10 and it has two causes with two different fixes. The journal needs a vendor attached or needs reversing. The payment batch needs applying to invoices. Nobody should close the gap by editing a vendor balance by hand. If you can, block direct postings to the control account for everyone except the person who runs the reconciliation, and review that person's activity.

What does the vendor statement check find?

The vendor statement check is the one that can find an invoice you never received. Three-way matching only tests documents you already hold, and the control account tie-out only tests your own books against themselves. A statement comes from outside and can list a bill nobody in your company has seen. The line-by-line method has its own guide, so this section sticks to what the Marlowe account shows.

Marlowe's statement and Bellhaven's ledger both start at $6,915.60, agreed on 30 September. They end $338.60 apart.

Four lines match. Five do not. Effects below are statement minus ledger.

Add the five effects and you get the net gap, −$338.60. Add their sizes and you get $8,585.70 of movement. A reviewer who compares only closing balances sees $338.60 and might wave it through as rounding. Two of the five, the duplicate posting and the check in transit, are each many times the gap and pull in opposite directions. Chasing the duplicate and the missing credit memo is covered in missing credit memos and duplicate payments.

Make the four ledger corrections and Bellhaven's ledger reads $6,324.55. The last one, CM-1182, has to wait until Marlowe sends the credit memo. Marlowe's statement still reads $8,762.70, and the $2,438.15 between the two is check 7802, which will show on November's statement. $8,762.70 less that check is $6,324.55, so they agree.

What if the vendor never sends a statement?

Ask for their open items at a fixed cut-off date, sent to a shared mailbox rather than to one person. Small shops and one-person trades often send nothing, and you still need evidence from outside your own books.

Ask for their figure before you give them yours. A reply to a blank request is better evidence than a tick on a number you supplied. Keep the request short and put these in it:

• Your account number with them, V-1042 in the example, and the cut-off date: 31 October 2026.
• A request for their open items at that date, with invoice numbers and the date and amount of each, plus any credit memos or payments they have not yet applied.
• A reply date, and a promise to check any differing line the same day.
• Nothing about your own balance, until they have answered.

If they do not answer, send your own open-items list and ask them to confirm or correct it.

Who should own the reconciliation?

The person who prepares the reconciliation should not be the person who reviews it. Name both, and write down what the preparer may not do. The split below is a starting point. A small team may have to combine roles, and then the reviewer needs to be senior enough to ask awkward questions.

Who may adjust a difference, and up to how much?

Set a threshold for how big a difference has to be before someone must name its cause, and say who may post the fix. Without one, you get an analyst writing off $40 while another spends a month chasing $12. The limits below are examples only. Set yours from your own volume and risk.

This split also answers a fraud question. The ACFE's Occupational Fraud 2026 report analyzed occupational fraud cases from around the world and found billing schemes in 21% of them (508 cases), with a median loss of $90,000. Checking statements from real vendors will not expose a fake one, which is why vendor setup stays away from payment release. The 2026 AFP Payments Fraud and Control Survey, with 465 responses reporting on 2025, found that business email compromise affected 74% of organizations. The survey notes that fraudsters mostly pose as vendors or executives to ask for changes to payment instructions. A change to a vendor’s remittance details should therefore be confirmed with contact details you already hold, separately from the statement check.

What should the reconciliation log record?

One row per vendor for each cut-off date. Keep it, because it is the first thing an auditor or whoever takes over from you will ask for. Put in the statement balance, your ledger balance, the difference, how much of that difference you have explained, and a status. Leave anything unexplained showing. And if a difference is still marked as timing when the next statement arrives, it isn't timing any more, so go and find out what it is.

How often should each vendor be reconciled?

Check your biggest and most error-prone vendors every month and again before a payment run. Check regular vendors monthly. Occasional ones can wait for the quarter. Most teams that try to reconcile everyone every month give up on it by about the third quarter, so a smaller list that actually gets done is better. If a past-due notice, an account hold or a changed remittance detail turns up, check that vendor straight away whatever tier it is in.

To pick the top tier, ask what a missed error would cost you with that vendor. High spend, lots of invoices each month, a history of credit memos and recent bank detail changes all push a vendor up the list. Don't ignore the small ones completely, though. Their credit memos tend to sit there for months because nobody chases them.

The full cadence table, with the pre-payment-run check, is in the month-end and pre-payment-run checklist.

What about credit balances and unclaimed property?

Unapplied credits and unusual balances should be reviewed at each cut-off. Where the business has issued a check which the vendor has not presented, the amount is still owed to the vendor, and under state unclaimed property rules it may have to be reported once the dormancy period has passed. Where a vendor has been overpaid, or a credit note has been received but not used, the amount is due to the business and should be followed up with the vendor in the same way as any other debt.

Dormancy periods differ by state and by the kind of item. The National Association of Unclaimed Property Administrators lists three years for vendor-to-vendor payments in many states, five in some, and exemptions in others, as of 30 October 2026. Check the owner's state first, then your state of incorporation. This is general information, not tax or legal advice.

What do auditors expect to see?

Auditors care about completeness in accounts payable, meaning liabilities that exist but never reached the books. PCAOB's AS 2310 says evidence from a knowledgeable external source is generally more reliable than evidence from internal sources. Paragraph .06 lists completeness and uses accounts payable as its example.

A statement the vendor sends you comes from outside your books, but it is weaker evidence than a confirmation the auditor sends and receives directly. The note to paragraph .08 says a request on a blank form, with no balance stated, may give more reliable evidence, although replies can be slower. The standard applies to auditors, not to management, and it doesn't require you to reconcile statements. For the control side, see reconciliation as a control. This is general information rather than audit advice, and it reflects the standard as we read it on 30 October 2026.

Spreadsheet, ERP reports or software: which should you use?

A spreadsheet is enough while only a handful of vendors send statements, and reconciliation software becomes worth having once retyping the statements is the slowest part of the month. ERP reports can supply the ledger side but cannot compare it with the statement. The table shows where each approach strains, and the main difference is the shape of the statement, because a PDF with a prefix on every invoice number is easy to read but slow to retype.

If you would rather start in a spreadsheet, the workbook below has a reconciliation sheet, a cause-code list and a chase list. Team best practices covers the habits that keep the work going once it is set up.

Where Statement Zen fits

Statement Zen is reconciliation software, and we sell it, so weigh this paragraph accordingly. You forward a vendor's statement by email, it is matched against your ledger in Xero, QuickBooks Online or Vista, and the result appears in your dashboard. Setup is covered on the Xero page, the QuickBooks Online page and the Vista page, and plans are on the pricing page. To see your own statement matched, try the free reconciliation.

Where do reconciliation programs go wrong?

Most failures come from comparing documents that are dated differently or from leaving a difference with nobody responsible for it, and the four examples below are the usual forms these take.

• Using a statement dated 30 September against a ledger run on 15 October, which invents differences that are not there.
• Carrying a timing item for months because nobody owns it, for example a check from March still shown as in transit in September.
• Letting one person set up vendors, post journals and release payments, then reconcile the result.
• Treating every difference as the vendor's mistake, or every one as yours. In the example, three of the five were Bellhaven's own, one needed the vendor to send a document, and one was just timing.

Pick one vendor and follow it from the control account all the way to a signed log row. Wherever you get stuck is the step your process is missing. Statement checking and three-way matching are different jobs, covered in statement reconciliation vs invoice matching.

Questions people ask

Sources

• ACFE: Occupational Fraud 2026, A Report to the Nations (billing schemes, 21% of cases, median loss $90,000), read 31 Oct 2026
• PCAOB: AS 2310, The Auditor's Use of Confirmation (paragraphs .06 and .08, Appendix C), read 30 Oct 2026
• NAUPA: Property Type, Vendor-Vendor Payments (dormancy periods by state), read 30 Oct 2026
• 2026 AFP Payments Fraud and Control Survey Report Highlights (465 responses, business email compromise affected 74% of organizations in 2025), read 31 Oct 2026

What changed

• 30 Oct 2026: First published.
• 31 Oct 2026: Added a step-by-step bridge from the statement balance to the ledger balance, an evidence column for each difference, a vendor impostor fraud figure with its source, and a note on how the sources were checked.
• 31 Oct 2026: Updated ACFE and AFP figures to the 2026 editions.
• 31 Oct 2026: Takeaways now open with the definition and the example’s figures. The cadence section now opens with the answer, and two subheadings are now questions.