To check a supplier statement against Xero, resolve the supplier to its Xero ContactID, retrieve that contact’s purchase bills, and compare the statement lines against explicit rules for references, dates, currencies, and amounts. An n8n workflow can orchestrate those steps, but its Xero integration does not provide a dedicated statement-reconciliation action. Treat the results as an exception report for human review—not as automatic proof that every discrepancy is an error.
What the workflow checks—and what it does not
A supplier statement is an external record of activity with a supplier. It may show invoices, credits, payments, or an outstanding balance. The workflow compares the statement data you supply with purchase bills recorded in Xero; it does not reconcile bank transactions or establish accounting treatment for every balance difference.
As an Amazon Associate I earn from qualifying purchases.
Xero’s Invoices API covers both sales invoices and purchase bills. The n8n Xero node documentation lists contact and invoice operations, including create, get, get all, and update actions, but no supplier-statement reconciliation operation. The workflow must retrieve the relevant records and perform the comparison itself.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallDo not use Xero’s Bank Feeds API Statements endpoint as the source of supplier statements: it is for financial institutions submitting bank statement data to Xero.
#1 Best Overall
Prepare the statement input
Use structured rows when available, such as CSV data with one row per statement entry. Decide which fields the comparison needs before building the workflow. A practical input might contain supplier name or account reference, invoice reference, invoice date, due date, currency, invoice amount, and statement balance. Preserve the original values even if you create normalized versions for matching.
If the supplier sends a PDF or image, extraction is a separate stage. Validate the extracted text and values before matching; the available product documentation does not establish a particular OCR method or guarantee that extraction is correct. A misread invoice reference or decimal separator can create a false exception.
Resolve the supplier to a ContactID
Use the Xero ContactID as the canonical supplier identifier for the workflow. Xero warns that Contact Name may no longer be unique and recommends ContactID for uniquely referencing contacts. A name match can help an operator find the record, but should not silently determine which supplier’s bills are compared.
Rank #2
Make supplier resolution a deliberate step: confirm the intended contact, retain its ContactID, and use that identifier for subsequent bill retrieval and comparison. If the input could refer to more than one contact, stop for review rather than selecting the first result.
Retrieve the supplier’s purchase bills
In n8n, use the Xero node’s invoice operations where they expose the fields and filters the workflow needs. Select purchase bills for the resolved ContactID and the relevant date range; do not compare against sales invoices. Exact filter availability depends on the API and node version in use.
If the built-in node does not expose a needed parameter or operation, n8n’s Xero integration documentation points to the HTTP Request node for custom API calls. Verify the current endpoint, credentials, and permissions in the relevant n8n and Xero documentation. Keep the check read-only unless writing to Xero is an explicit requirement: the API includes create and update operations, and some actions depend on invoice state and organisation rules.
Author and run deterministic matching rules
Deterministic matching means the same input and rules produce the same outcome, with the reason visible to a reviewer. It does not mean that extraction is infallible or that a discrepancy is necessarily a bookkeeping error. Define normalization and comparison policies explicitly, then retain both original and normalized values.
Normalize invoice references
Trim surrounding whitespace and choose a case policy, such as case-insensitive comparison. Keep the statement’s original reference and the Xero reference in the report so the operator can see exactly what was compared. Do not remove punctuation or leading zeroes unless the business has a documented rule to do so.
Compare dates consistently
Parse dates using an explicit format or locale assumption. Decide whether the rule compares invoice dates or due dates, and use the same field on both sides. Ambiguous dates such as 04/05/2026 should not be interpreted without knowing whether the input means 4 May or April 5.
Keep currency and amounts explicit
Compare amounts only within the same currency unless the workflow implements a documented conversion rule. State whether the comparison is for the original bill total, an outstanding balance, or another amount. A supplier statement can show a balance affected by payments, credits, timing, or currency, so a difference from the original bill total is not automatically an error.
Do not guess between duplicate candidates
If more than one bill satisfies the matching rules, mark the statement line as ambiguous or a possible duplicate. Do not silently choose the first candidate. An operator can then review the references, dates, currencies, amounts, and Xero records.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteRun TypeScript without overstating n8n’s support
n8n’s Code node documentation specifies JavaScript or Python execution; it does not document native TypeScript execution. A practical TypeScript approach is to author and type-check matching logic in TypeScript, compile it to JavaScript, and deploy the resulting JavaScript in a supported workflow setup. Treat that as a build and deployment arrangement, not a built-in TypeScript runtime.
Best Value
The Code node documentation also says the node cannot access the filesystem or make HTTP requests. Use dedicated n8n nodes for file handling and API calls. External npm module imports are configurable in self-hosted n8n; n8n Cloud does not allow arbitrary external npm imports and provides specific modules. Check the current Code node documentation and TypeScript documentation for the execution and compilation details relevant to your deployment.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Report outcomes for human review
Return one result per statement line, with the original statement values, normalized values, candidate Xero bill identifier and reference when found, compared fields, the rule that produced the result, and a review status. Useful outcomes include:
- Matched: one purchase bill satisfies the stated matching rules.
- Statement item missing from Xero: no bill was found under the selected contact and query scope.
- Xero bill missing from statement: a retrieved bill has no corresponding statement line in the comparison period.
- Amount or date difference: a candidate bill was found, but a compared field differs.
- Possible duplicate or ambiguous: multiple candidates meet the rules, or the available fields do not identify one bill reliably.
- Balance mismatch or partial payment: the statement balance does not match the original bill total or another chosen comparison amount and needs accounting review.
- Needs review: input quality, currency, dates, credits, payments, or another condition prevents a reliable automatic outcome.
These labels describe comparison results, not accounting conclusions. Verify payment, credit, and balance cases against the relevant Xero records and, where appropriate, a qualified accounting practitioner; the integration documentation does not determine tenant-specific accounting treatment.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Choose controls that fit the input and deployment
Before enabling a workflow, confirm that the statement source, matching rules, permissions, and review process suit your operation. The right design depends on the quality and volume of incoming data; no one matching approach is best for every supplier or deployment.
Quick Recap
- For structured CSV or text, validate required columns and date, currency, and decimal formats before comparison.
- For PDF or image input, make extraction review a distinct step and do not treat extracted values as verified automatically.
- For uncertain references or duplicate candidates, route exceptions to a reviewer rather than broadening the matching rule until it produces a result.
- For n8n Cloud, account for the Code node’s external-module restrictions; for self-hosted n8n, configure permitted imports deliberately.
- Limit Xero permissions to the read scope needed for checking unless the workflow has a separately approved write requirement.
- Retain enough source values and rule explanations for an operator to reproduce why each line matched or was flagged.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
