Checking Xero supplier statements with n8n and deterministic TypeScript
A reference match is not the same thing as a safe amount comparison. A supplier statement might show the invoice's original total, the remaining balance after a payment, or an unclear amount column. Treating all three as the same value can produce a convincing report with the wrong conclusion. The open-source Xero Supplier Statement Checker uses n8n for orchestration and TypeScript for…
The open-source Xero Supplier Statement Checker project utilizes n8n for workflow orchestration and TypeScript for deterministic checking. The tool aims to accurately compare supplier statements by separating references from amounts, normalizing references, and preserving evidence through operator review. Separate reference candidates are presented for review before attempting any amount comparisons, and calculations are performed using integer minor units based on a checked-in currency table.
The workflow employs explicit page retrieval with sequential pages and explicit page sizes, validating the evidence rather than trusting a caller's success flag. If a page fails, there is no basis for declaring an invoice absent. The checker is a preview and has only been tested locally, with pending verification on live Xero and n8n Cloud.
Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
