Invoice Data Extraction Logo
Invoice Data Extraction
Start Extraction
Pricing
Extraction Guide
API
Sign inCreate account
Sign inCreate account
Start Extraction
Pricing
Extraction Guide
API
  1. Home
  2. Articles & Analysis
  3. Software Integrations
  4. Xero Supplier Statement Reconciliation Workflow

Xero Supplier Statement Reconciliation Workflow

Reconcile supplier statements in Xero by comparing extracted statement rows with bills, credits and payments. Build an exception report before close.

Published
Jul 17, 2026
Updated
Jul 17, 2026
Reading Time
11 min
Author
David Harding
Topics:
Software IntegrationsXeroVendor Statementsaccounts payablesupplier statement reconciliation

On this page

Xero supplier statement reconciliation means comparing a supplier's statement rows with the bills, credit notes, payments, refunds, and supplier activity recorded in Xero for the same supplier and period. Xero does not provide a full supplier-statement reconciliation workflow equivalent to bank reconciliation, so the practical workaround is to extract the statement into clean rows, pull the matching Xero-side activity, and resolve exceptions before posting adjustments or making payments.

That distinction matters. A supplier statement is the supplier's view of what you owe. Xero is your accounting ledger. Reconciliation is the control step that explains the difference between the two before month-end close, a payment run, or a supplier query.

The useful output is not a yes-or-no tick against the statement. It is an exception report: statement invoices not found in Xero, Xero bills absent from the statement, missing credit notes, duplicate references, amount or date mismatches, foreign-currency differences, and payments that do not explain the remaining supplier balance.

For US teams using vendor terminology, this is the same practical problem as Xero vendor statement reconciliation. In Xero's own purchase and bills language, though, "supplier statement" and "supplier activity" are the terms most readers will see when trying to reconcile the account.

Define the reconciliation pack before you touch Xero

Start by fixing the scope of the pack. Use one supplier contact, one statement date, one statement period, and one version of the supplier statement. If the supplier later sends a revised statement, save it as a new source file rather than overwriting the original review evidence.

A practical pack contains three things:

  • The supplier statement, including opening balance, movement, credits, payments, and closing balance where shown.
  • Xero-side activity for the same supplier and period, including bills, credit notes, payments, refunds, and any brought-forward balance that explains older items.
  • A working exception sheet that records match status, reviewer notes, evidence, and next owner.

This is narrower than the broader vendor statement reconciliation process, which may cover procurement controls, supplier communication, statement ageing, and AP policy. For a Xero-specific review, the useful question is simpler: does the supplier's claim agree to the bills, credits, payments, and balances recorded in Xero for this contact?

Decide the purpose of the reconciliation before matching. A pre-payment review focuses on bills to pay and credits that should reduce the payment. A month-end review focuses on completeness, cut-off, and whether the supplier balance is supportable. A supplier-dispute review focuses on the specific invoices, credits, or payments being queried. The data may overlap, but the reviewer needs to know what decision the pack is meant to support.

Extract the supplier statement into matchable rows

A supplier statement PDF is not matchable until its line items become structured rows. At minimum, capture the document type, invoice number or credit note number, document date, due date, amount, currency, payment reference, outstanding amount, running balance if shown, and statement total. If the supplier includes an opening balance, keep that as its own line or control value rather than blending it into the first invoice.

This is where many Xero supplier statement reconciliations slow down. Supplier statements often mix invoices, credits, part-payments, older brought-forward balances, and references that do not match the bill number exactly as entered in Xero. Some suppliers add prefixes, spaces, branch codes, or remittance references. Others show a gross statement balance but omit the tax split or the allocation of a partial payment.

Invoice Data Extraction can help at this document-to-data layer. The product lets users upload financial documents, describe the fields they need in a natural-language prompt, and download structured XLSX, CSV, or JSON output. For this workflow, the prompt can ask for fields such as invoice number, credit note number, document date, due date, amount, currency, payment reference, outstanding balance, and statement balance. That is a way to extract supplier statement PDFs into structured rows for review. It is not a native Xero reconciliation module and does not post adjustments into Xero.

If the statement format is inconsistent, preserve the original wording in a notes or source-reference column. A reviewer should be able to trace each row back to the supplier statement, especially when a credit note, payment, or opening balance does not line up cleanly. For a deeper extraction workflow, see how to convert supplier statements to Excel before building the Xero comparison sheet.

Pull the right Xero-side activity for the same supplier

Once the statement is in rows, pull the Xero-side records for the same supplier contact and period. The useful data is not only open bills. A supplier statement may include invoices that were paid during the period, credit notes, refunds, prepayments, overpayments, and part-payments that explain the closing balance.

For a Xero Supplier Bill Activity reconciliation, the Supplier Bill Activity report is usually the closest Xero-side view because it is designed around supplier bill movement through a period. Contact activity can also help when you need to see the supplier account's transaction history in context. Payable invoice detail and bills to pay views may be useful supporting views when the question is whether a bill is entered, approved, awaiting payment, paid, or credited.

Do not treat any Xero supplier statement report or activity view as a replacement for the supplier's own statement. The Xero-side data shows what your ledger currently records. The supplier statement shows the external balance claim you are testing against it.

Align the filters before comparing anything. Use the same supplier contact, statement period, and currency lens wherever Xero allows it. A statement dated 30 June should not be reconciled against a report pulled to 17 July unless the reviewer is deliberately investigating post-statement payments. Likewise, a bill entered under a duplicate supplier contact will look missing even if the invoice is in Xero somewhere else.

If the statement shows invoices that are not in Xero, do not treat the reconciliation sheet as the source of the bill. Find the source document first. Depending on the team's process, missing invoices may need to come through normal capture, approval, or Xero invoice scanning options before they are recorded.

Match statement lines to Xero records

Start with the strongest reference: invoice number for invoices and credit note number for credits. For Xero bills to pay supplier statement matching, an exact supplier reference is the cleanest starting point. If the supplier's statement reference and the Xero bill reference match exactly, use amount, date, due date, and currency as confirmation rather than as the primary key. This keeps the review disciplined and makes duplicate references easier to spot.

Weak matches need a separate status. A supplier may show invoice 104582 while Xero has INV-104582, or the statement may show a remittance reference where Xero holds the original bill number. That may be a probable match, but it is not the same as an exact match. The working file should distinguish exact match, probable match, unresolved exception, and review needed.

Payments need a different test. A payment reference may match a remittance, but the important question is whether the payment and any credits explain the remaining balance on the statement. Part-payments, supplier allocations after the statement date, and payments posted in Xero but not yet allocated by the supplier can all create real differences without meaning the bill itself is wrong.

Watch for tax and currency presentation. A supplier statement may show gross values only, while Xero stores tax details behind the bill. A foreign-currency supplier may show the source-currency amount, while Xero's accounting reports also carry base-currency values. Treat those as separate fields rather than forcing one amount column to do both jobs.

Build the exception report before updating Xero

The exception report is the real control output. It should tell the reviewer what does not agree, why it matters, what evidence exists, and who owns the next action. A worksheet with only matched and unmatched rows is rarely enough for month-end review.

Use exception categories that map to accounting decisions:

  • Statement invoice not found in Xero: The bill may be missing, entered under another supplier, awaiting approval elsewhere, or not yet received.
  • Xero bill not present on the statement: The supplier may have omitted it, credited it, issued a later statement, or applied a different date cut-off.
  • Duplicate invoice or reference: The same supplier reference may appear twice in Xero, twice on the statement, or once in each system with conflicting details.
  • Missing credit note: The supplier has reduced the balance, but Xero still shows the original payable.
  • Amount, date, due date, or currency mismatch: The bill exists, but the supporting fields do not agree.
  • Payment or part-payment mismatch: Xero shows a payment, but the supplier statement does not allocate it in the same way.
  • Unexplained opening or closing balance: The movement may match, but the brought-forward or closing value does not.

Each category should have a next-action column, but the action should come after investigation. Entering a missing bill, requesting a credit note, correcting a duplicate reference, changing an allocation, or querying the supplier are different outcomes. A good Xero Supplier Bill Activity reconciliation keeps those outcomes separate until the evidence supports one of them.

Structured statement rows make this review easier because the team can sort by supplier reference, filter by exception type, and compare statement values against Xero values without re-reading the PDF for every line. The reviewer still decides what to do in Xero.

Keep source currency separate in foreign-currency reconciliations

Foreign-currency supplier statements should be reconciled in the statement currency first. If a USD supplier sends a USD statement, the first question is whether the USD invoices, credits, payments, and closing balance agree. Xero's base-currency accounting impact is a second review layer, not a substitute for source-currency matching.

This is a real practitioner pain point. A Xero Product Ideas request for foreign-currency Supplier Bill Activity totals asked for the Supplier Bill Activity report to include source-currency amounts and currency-specific balances for multicurrency supplier reconciliation, and it had 39 votes. The useful takeaway is specific: teams reconciling foreign-currency suppliers need source-currency totals they can compare to the supplier's own statement.

Keep separate columns for document currency, source amount, base amount, exchange-rate date, payment currency, and statement-currency balance. If Xero records the bill in one currency and the payment is made in another, do not collapse the difference into a single variance note. The reviewer needs to know whether the exception is a missing document, a supplier allocation issue, a timing difference, or an exchange-rate effect.

For month-end review, explain both balances. The supplier statement balance supports what the supplier says you owe in its currency. Xero's base-currency balance supports the accounting ledger. A clean reconciliation can show why those two views differ without forcing either one to disappear.

Make Xero changes only after the exceptions are explained

The reconciliation should not be used to force Xero to agree with the supplier statement. It should give the team enough evidence to decide what, if anything, needs to change.

For a missing supplier invoice, find the original invoice and follow the normal entry or approval route. If the team has structured bill data ready, it may be appropriate to import purchase bills into Xero by CSV, but the reconciliation sheet itself is not source evidence. For a missing credit note, request the document or confirm whether it has already been applied under another reference. For a duplicate reference, inspect both records before voiding, editing, or merging anything in the working file.

Payment exceptions need the same restraint. A supplier may allocate a payment to different invoices than the Xero record shows, or a payment made after the statement date may explain a supplier query without changing the statement balance. The right next step might be a remittance check, a supplier email, or a payment allocation review rather than an accounting adjustment.

A good Xero supplier statement reconciliation ends with a clean supplier account and a review trail: matched items are marked, exceptions have owners, source documents are attached or requested, and unresolved differences are documented before close or payment approval. That is the control value of the workflow.

Extract invoice data to Excel with natural language prompts

Upload your invoices, describe what you need in plain language, and download clean, structured spreadsheets. No templates, no complex configuration.

Exceptional accuracy on financial documents
Parallel processing — large batches complete in minutes
50 free pages every month — no subscription
Any document layout, language, or scan quality
Native Excel types — numbers, dates, currencies
Files encrypted and auto-deleted within 24 hours
Start Extracting FreeView Pricing
Continue Reading

Related Articles

Explore adjacent guides and reference articles on this topic.

How to Prevent Duplicate Bills in Xero

Xero flags possible duplicate bills by matching contact, reference and amount, but its alert can miss near-duplicates. Learn how to prevent paying twice.

Xero Invoice Status Authorised: What Approved Really Means

In Xero, Authorised means an invoice has been approved and is ready for payment. Learn how it maps to Approved and Awaiting Payment in each Xero view.

Xero GST on Capital: BAS Labels G10 and 1B Explained

How Xero codes capital purchases to BAS labels G10 and 1B, why GST on Capital is archived under Simpler BAS, and when to restore it for Full BAS reporters.

Back to Articles & Analysis

Invoice Data Extraction

The AI-native automation platform for high-accuracy invoice extraction

Platform

  • Start Extraction
  • Home
  • Pricing
  • API
  • Python SDK
  • Node.js SDK

Solutions

  • Invoice to Excel
  • Invoice OCR Software
  • Bank Statement Converter
  • Receipt OCR
  • Utility Bill Extraction
  • Payroll Data Extraction
  • PDF Data Extraction

Resources

  • Articles
  • Contact

Trust & Security

  • Security
  • Subprocessors
  • AI Data Use

Legal

  • Terms of Service
  • Data Processing Addendum
  • Privacy Policy
  • Refund Policy
  • US State Privacy Rights
  • EEA/UK Privacy Rights
English
Sign inCreate account

© 2026 Invoice Data Extraction — DEH Technologies LLC

Secure by Design. Your data is never used for AI training.