What the Xero-Amex integration does not cover

If your company runs corporate cards on American Express and your books live in Xero, you have connected the two. The Xero-Amex integration is a widely used add-on: it pulls statement lines into Xero automatically, removing a daily import step. That is a useful saving. It is not reconciliation.

The distinction matters in practice. Finance teams discover it at month-end, when Xero holds a full transaction list but receipts are missing, category coding is uncertain, and no approval record exists for the charges that needed one. The integration delivered the data. The reconciliation work still needs doing.

What the integration does

The Xero-Amex connection is a data feed. Each business day, it retrieves statement activity from your Amex account and creates corresponding transactions in Xero. You can then review, code, and post those transactions.

That last step — review and post — is the endpoint of the reconciliation process. The integration places you there. It does not handle the steps that need to happen before you can post with confidence.

What reconciliation actually covers

Reconciliation is the work that happens between the charge and the ledger entry. It has three distinct parts.

Receipt collection. Every charge requires documentation. The statement line carries a vendor name and an amount. The receipt tells you what was purchased, whether the spend was business-related, which VAT rate applies, and whether it falls within policy. For EU businesses, the BTW rate and the supplier's BTW number must appear on the receipt to satisfy the EU VAT Directive — details the card statement does not carry. The Xero-Amex integration does not collect receipts. Hubdoc, which Xero bundles with all paid plans, captures receipt images — but matching those images to the statement lines the Amex feed imports, and routing those charges through an approval workflow before posting, are steps neither the integration nor Hubdoc handles.

Match verification. A statement line and a receipt are two separate records that need to be confirmed as the same transaction. For corporate card programmes with multiple cardholders, that means checking vendor, amount, date, and — for international spend — currency conversion, at volume. The integration does not do this matching.

Approval workflow. Finance policy requires sign-off before a charge is posted: manager approval above a threshold, category coding by the cardholder, or both. The Xero-Amex integration does not route imported transactions through an approval workflow before they are posted.

Without these three steps completed upstream, a posted transaction is not reconciled — it is filed. The difference is visible at audit.

Where Rexa fits

Rexa is designed to collect the receipt when a cardholder makes an Amex charge — via browser upload initially, with email forwarding and direct inbox capture on the roadmap — and match it to the corresponding card-statement line. Where match confidence is uncertain, Rexa will flag the charge for review before posting. Where policy requires approval, Rexa will route the charge to the designated approver.

For a detailed walkthrough of what card reconciliation involves from charge to close, read the Amex corporate card reconciliation guide.

The practical difference

At lower card volume, the gap between the integration and full reconciliation can be managed manually — receipt requests, spreadsheet matching, and email sign-offs are time-consuming but workable. As card volume grows, those manual steps become a reliable monthly bottleneck.

Rexa is being built for teams where that bottleneck has become a material cost in hours. Your existing Xero-Amex feed stays in place for statement import; Rexa is designed to handle the receipt collection, match verification, and approval routing that need to happen before reconciliation is complete.

American Express and Amex are trademarks of American Express Company. Rexa is not affiliated with, endorsed by, or in partnership with American Express.