Finance & ERP · Integration
Xero
Add Xero to your product for your customers, and give your AI agents governed access to it.
Xero's users are small businesses plus the accountants and bookkeepers who serve dozens of them, so an embedded Xero integration has to cope with one login reaching many organisations. Every connection is per organisation, and your product picks the right one before it touches invoices, bills, contacts, bank transactions, payments or the chart of accounts. After that, call limits are enforced per organisation as well as per app, tracking categories and tax rates differ by region, and reconciliation is its own state rather than a flag on an invoice. fastn manages the per-organisation tokens, paces requests inside those limits, and keeps up with each Xero API release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect one Xero organisation or several, and choose which one your product writes to.
Create sales invoices and record bills from your product so the books reflect what the business actually did.
Read bank transactions and payment status so your product can show what has cleared and what has not.
Use each organisation's own tax rates and tracking categories instead of hard-coding one country's setup.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent compares this week's bank transactions with open invoices and flags the ones that do not line up.
An agent raises an invoice in the organisation the user is working in and nowhere else, with the call audited.
An agent summarises which bills fall due in the next fortnight for a single organisation.
Example prompt
Which bills are due in the next two weeks in this Xero organisation, and how much cash do we need?
Set up Xero in 4 steps
- 01Enable the Xero connector from your fastn dashboard.
- 02Have each customer authorise their own Xero account, so calls run under their credentials rather than a shared key.
- 03Decide which invoices, payments and vendors your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Xero integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Xero integration without building it. Your customers connect their own Xero account inside your product and work their invoices, payments and vendors there, with no per-customer code on your side.
- Handle the part that actually costs time: financial writes must be idempotent and reconcilable, because a duplicate is an accounting problem rather than a bug. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Xero update is not your on-call problem.
- One integration serves your product and your agents. The same governed Xero connection powers in-product features and gives AI agents scoped, audited access, so you move financial records without hand-keying them between systems without wiring it twice.
Used by these teams
Compare with
QuickBooks
FreshBooks
MYOB BusinessOften used alongside
Tools the same teams tend to run next to Xero, across other categories.
Shopify
Stripe
BigCommerce
AfterShipXero integration FAQ
How do I add a Xero integration to my product?
Enable the Xero connector in your fastn dashboard, then let each customer authenticate their own Xero account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Xero client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Xero account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Xero account and only ever sees their own invoices, payments and vendors. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Xero integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent compares this week's bank transactions with open invoices and flags the ones that do not line up.
Who maintains the Xero integration?
fastn does. When Xero changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Xero integration safe for financial writes?
Writes are idempotent, so a retry after a timeout does not post a document twice, and every call is logged per tenant so an entry can be traced back to the event that created it. That matters more in finance than anywhere else, because a duplicate is a number somebody has to explain.
Can it handle each customer's own chart of accounts?
Yes. ERP deployments are configured to the business, so account structures, required fields and fiscal calendars differ per customer. Those are mapped per tenant as configuration, not hard-coded.
What about Xero rate limits during a first import?
Backfills are throttled deliberately. ERP limits are often account-wide rather than per-integration, so an unthrottled import can exhaust a customer's allowance and disrupt their other integrations.
What can I build with the Xero integration?
A common starting point: let a customer connect one Xero organisation or several, and choose which one your product writes to. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Xero integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Xero does not change your per-connector cost. You can start free with 3 connected accounts.
Add Xero to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.