Xero

How to get a supplier statement out of Xero

If you've looked for a "send supplier statement" button in Xero, you already know: it doesn't exist. Xero produces customer statements (accounts receivable) at a click, but for the payable side — a chronological statement of bills, credit notes and payments with a running balance that you can send to a supplier — you're on your own. Here's what Xero does give you, and three ways to close the gap.

What Xero gives you today

Aged Payables report (Accounting → Reports → Aged Payables) — what you owe, bucketed by age. Great summary, but it isn't a statement: no chronological line detail, no payment history, not something you'd send a supplier.
Contact history — click a supplier, see their transactions. Right data, wrong format: one supplier at a time, on screen, not print-ready.
Exports — Bills, bills-and-payments, and report exports to CSV/XLSX. All the raw material, none of the layout.

Option 1 — Assemble it in a spreadsheet

The default answer for years: export to CSV, delete the columns you don't need, sort by date, add a formula column for the running balance, format, print. It works, and it costs 15–30 minutes per supplier, every month — plus the risks that come with manual work: a mis-sorted date here, a dropped row there, and floating-point rounding quietly shaving cents off the closing balance.

Option 2 — A connected app from the Xero App Store

Several reporting apps connect via the Xero API and can produce supplier-facing documents. The trade-offs are structural:

OAuth per client — a practice with 30 client orgs must authorize the app in every one of them, and re-authorize when connections drop.
Client data flows through a third party — which can conflict with confidentiality obligations some clients care about.
Per-seat subscriptions — tools like StatementZen run $99–899/month, recurring forever, and route statements through their servers.

Option 3 — A local generator that reads the export

The third path skips both problems: export the data (which you can already do), and let a local tool do the assembly. That's exactly why Statemint works the way it does:

No API, no OAuth — drag in the CSV/XLSX you exported; nothing to authorize in any client org.
No upload — files are parsed in your browser; the flow works offline.
Column mapping is remembered — map a Xero export once and every future export of the same shape is instant.
Balances that add up — amounts computed in integer cents with an enforced identity, so the closing balance is provably right.
One-time purchase — $29 early bird, $39 regular. No per-seat, per-client or monthly anything.

The workflow: Business → Purchases → Bills → Export (and the payments export), drop both files into Statemint, confirm the auto-detected columns, pick suppliers, print. One page per supplier, header repeated on every page, your logo at the top.

Which option should you pick?

If you send statements to one or two suppliers a year, the spreadsheet is fine. If client data can't leave your machine, or the per-client OAuth dance kills connected apps for you, or you simply have 15 suppliers and 30 minutes of billable time — the local route is the one that respects all three constraints.