Xero Integration Services
Xero has one of the better accounting APIs to work with. The decisions that determine whether an integration succeeds are still accounting decisions, taken with whoever owns your books before any code exists.
Discuss your projectFour questions before anything is built
Which revenue account does each product or service post to? Which tax rate applies, and does it vary by customer or by the customer's country? Are you using tracking categories for departments, branches or projects, and must every line carry one? And how is a Xero contact matched to the record in your own system — by name, by email, or by an identifier stored in both?
The tracking categories question is the one that catches people. Xero allows up to two, and if your management reporting depends on them, every invoice the integration creates has to populate them. Discovering that after a month of transactions means correcting them by hand.
None of these are technical questions and all of them determine what the integration does. Building first produces a month of transactions posted to the wrong accounts, which your accountant then unpicks — considerably more expensive than the conversation would have been.
What we build
Invoices from your own system
Raised from orders, jobs or won deals, with line items on the right accounts and tax rates, tracking categories populated, and your invoice branding theme applied. Created as drafts while the integration is new.
Quotes that convert
Xero quotes raised from your system and converted to invoices on acceptance, so figures follow through rather than being retyped.
Payment status back
Paid, part paid, overdue and days outstanding written into your own application as read-only fields, so your team can see a customer's position before promising terms.
Contact synchronisation
Matched on an identifier held in both systems rather than on company name, which gets edited and abbreviated. Near matches go to a review queue instead of merging automatically.
Bills and supplier payments
Purchase invoices created from approved orders or from extracted documents, which pairs naturally with invoice data extraction.
Repeating invoices
For subscription or retainer billing, created from your system where the arrangement is recurring rather than one-off.
Credit notes and refunds
Handled as their own document type. Treating a credit note as a negative invoice causes problems your accountant will find.
Reporting data out
Pulling financial data into your own dashboards, so revenue and margin reporting draws on the ledger rather than a parallel calculation.
The Xero-specific details that cause real problems
These account for most support calls on an otherwise working integration.
- Xero authorises a connection per organisation, so a business running several Xero organisations needs the integration scoped per connection with a rule deciding which one a transaction belongs to — entity, region or brand.
- Refresh tokens are short-lived and must be rotated on every use. An integration that does not refresh correctly stops working quietly rather than loudly, so we alert on token health instead of waiting for a failed sync.
- Rate limits apply per organisation and per application, which means bulk work is batched and paced rather than looped.
- Tracking categories are limited to two, and where your reports depend on them they must be populated on every line the integration creates.
- Tax rates are configured per organisation and differ by region, so we map to the rate as named in your Xero rather than to a generic code.
- Invoice numbering stays with Xero. Assigning numbers from your own system produces gaps and duplicates in the sequence, which an auditor will raise.
- Invoices move through draft, submitted, authorised and paid, and only some fields are editable at each stage. The integration respects that rather than attempting edits Xero will reject.
- Attachments can be pushed to a transaction, which is worth doing — the source document sitting on the invoice in Xero saves your finance team searching for it.
Two one-way flows, not a bidirectional sync
Clients usually ask for a two-way sync. What they almost always need is two one-way flows with explicit ownership, and it is considerably more robust.
Your system owns the operational record — the order, the job, the customer relationship. Xero owns everything financial: invoice status, payments, credit terms, balances. Transactions flow one way into Xero, and status flows back the other way into read-only fields. Neither system overwrites what the other owns.
A genuine bidirectional sync, where both sides can edit the same invoice, invites conflicts with real financial consequences — a salesperson changing an amount already filed, or two edits racing and one silently winning. We would want a specific reason before building one, and in practice we have rarely found a good one.
Common questions
Tell us what you need
Describe the problem and we will come back with scope, timeline, and a rate. No obligation to proceed.
Get in touch