How to Connect Xero to Your ERP
Why Xero connections need more care than most
Xero access tokens are short lived, and its refresh tokens rotate: each renewal issues a new one and invalidates the previous. An integration that mishandles that rotation does not degrade gracefully. It disconnects the organisation permanently and needs a human to reauthorise.
One Xero login can also authorise several organisations. An integration that silently picks the first one will post a company’s invoices into someone else’s books, which is the kind of mistake that is noticed late and is unpleasant to unwind.
Accountants in Australia and New Zealand, where Xero is the default, tend to test an integration harder than average. They will ask which account a line posts to and which tax rate it carries, and a vague answer will end the conversation.
None of this is exotic. It is the ordinary consequence of Xero being designed for accountants who hold many client files under one login, with short-lived credentials that rotate on purpose. An integration built for a simpler provider and pointed at Xero will appear to work during a demo and fail in the second week, which is the worst possible time to discover it.
The steps below therefore front-load the two decisions that are expensive to reverse: which organisation this company is bound to, and which ledger accounts its lines post against. Both take minutes to set correctly and hours to unpick once real invoices have been written against the wrong answer.
Why this happens
- Rotating refresh tokens are not persisted with the access token they were issued alongside.
- Two concurrent renewals race and invalidate each other, disconnecting the tenant.
- The organisation is assumed rather than chosen by the person who knows.
- Ledger accounts and tax rates are left unmapped, so postings cannot be defended to an accountant.
Biznsbook addresses this through OAuth 2.0 connect, organisation picker, tax rate mapping when the Integrations module is licensed and a SiteAdmin has assigned the connector to your company.
Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.
Step-by-step: Connect Xero to Your ERP
Written for owners, bookkeepers, and controllers running Biznsbook alongside QuickBooks Online or Xero. Connecting is supported today; the two-way sync is Beta, so verify each step against a sandbox company before a live month-end depends on it.
- Confirm the module and connector are available. The Integrations module must be licensed, and a SiteAdmin must assign the Xero connector to your tenant before it appears in your Integration Hub.
- Open the Xero connector settings. Go to the Integration Hub and choose Xero. The page shows connection status, the per-direction sync switches, and the connect panel.
- Authorise with OAuth. Click Connect and sign in to Xero. Biznsbook requests offline access so it can renew without asking you again, and stores the result encrypted per company.
- Choose the organisation. If your login covers more than one organisation, Biznsbook lists them and asks you to pick. It never assumes. You can change the organisation later by reconnecting.
- Verify with Test connection. Biznsbook reads the connected organisation once and reports the result, confirming the token, the scopes, and the organisation selection are all good.
- Map accounts and tax rates. Link each Biznsbook ledger account to a Xero account code, and each tax component to a Xero tax rate. Xero needs the account code on the line, so unmapped accounts are worth clearing first.
- Map a bank account before syncing payments. Xero posts a payment into a named bank account. Map your cash or bank ledger account, or Biznsbook will refuse the payment rather than guess which account to credit.
- Send one invoice and confirm it. Post a single sale invoice, check it appears once in the right organisation with the expected account codes and tax types, then review the execution log.
Review results after the first full monthly cycle. Adjust roles, mappings, or approvals where the same exception repeats.
Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.
Common mistakes to avoid
- Mistake 1: Rotating refresh tokens are not persisted with the access token they were issued alongside. Repeating this each month usually shows up first in duplicate invoices or postings landing in the wrong ledger account.
- Mistake 2: Two concurrent renewals race and invalidate each other, disconnecting the tenant. Repeating this each month usually shows up first in duplicate invoices or postings landing in the wrong ledger account.
- Mistake 3: The organisation is assumed rather than chosen by the person who knows. Repeating this each month usually shows up first in duplicate invoices or postings landing in the wrong ledger account.
- Mistake 4: Ledger accounts and tax rates are left unmapped, so postings cannot be defended to an accountant. Repeating this each month usually shows up first in duplicate invoices or postings landing in the wrong ledger account.
Track recurring exceptions in month-end notes; each should map to a control above.
Best practices that hold up as you scale
- Confirm the module and connector are available — The Integrations module must be licensed, and a SiteAdmin must assign the Xero connector to your tenant before it appears in your Integration Hub.
- Open the Xero connector settings — Go to the Integration Hub and choose Xero.
- Authorise with OAuth — Click Connect and sign in to Xero.
- Choose the organisation — If your login covers more than one organisation, Biznsbook lists them and asks you to pick.
- Verify with Test connection — Biznsbook reads the connected organisation once and reports the result, confirming the token, the scopes, and the organisation selection are all good.
Send one invoice before you send a batch. An integration that survives a week of real trading volume with a clean execution log is one you can safely put on a schedule.
How Biznsbook supports this workflow
OAuth 2.0 connect is documented in Biznsbook Integrations / Accounting capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
organisation picker is documented in Biznsbook Integrations / Accounting capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
tax rate mapping is documented in Biznsbook Integrations / Accounting capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
Four switches must all be on: the Integrations module licence, the connector assignment from SiteAdmin, the connector toggle on the settings page, and a completed OAuth connection. Sending documents out is on by default; anything that writes back into Biznsbook is opt-in.
Suggested implementation timeline
- Week 1: Document current process gaps and configure OAuth 2.0 connect with finance owner sign-off.
- Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
- Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
- Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
- Ongoing: Monthly review using why the organisation picker matters and leadership dashboard.
Metrics to track monthly
- Invoices synced versus invoices posted in the period
- Duplicate external records created (target: zero)
- Unmapped ledger accounts remaining
- Failed connector runs in the execution log per week
- Open sync conflicts awaiting a decision
Start with three metrics; trend direction matters more than a single point-in-time snapshot.
Spreadsheet / manual books vs integrated ERP
Compare typical manual finance work with Biznsbook OAuth 2.0 connect and related capabilities.
| Capability | Manual / Spreadsheet | Biznsbook |
|---|---|---|
| Authorisation | ❌ Pasted access token | ✅ OAuth 2.0 with offline access |
| Refresh token rotation | ❌ Breaks the connection | ✅ Stored with the access token in one write |
| Concurrent renewals | ❌ Can invalidate each other | ✅ Serialised so only one renewal runs |
| Organisation choice | ❌ First one assumed | ✅ You pick when there is more than one |
| Line accounts | ❌ Left to a default | ✅ Xero account code from your mapping |
| Payment posting | ❌ Guessed bank account | ✅ Refused until a bank account is mapped |
Why the organisation picker matters
Accountants and bookkeepers routinely hold access to many client organisations under one Xero login. An integration that authorises against that login and takes the first organisation it finds will post one client’s invoices into another client’s ledger. Being asked to pick takes a few seconds and removes an entire class of incident.
Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.
Frequently asked questions
Does Biznsbook handle Xero rotating refresh tokens?
Yes. Each renewal returns a new refresh token, and Biznsbook stores it together with the new access token in a single write. Renewals are also serialised per company so two of them cannot invalidate each other.
My Xero login covers several organisations. Which one is used?
The one you choose. After connecting, Biznsbook lists the organisations your authorisation covers and asks you to pick. It never selects one for you, because posting invoices into the wrong books is hard to unwind.
Can I change the Xero organisation later?
Yes. Reconnect from the connector settings page and pick a different organisation. Existing mappings stay with the company, so review them after switching.
Why will Biznsbook not sync a payment to Xero?
Xero posts payments into a named bank account. If your cash or bank ledger account is not mapped to a Xero account, Biznsbook refuses the payment and tells you to map it, rather than crediting an account it guessed.
Is the Xero two-way sync production ready?
Connecting is supported. Two-way sync is Beta, so verify invoices, contacts, and payment status against your own Xero demo organisation before you rely on it for a live month-end.
What happens if someone revokes access in Xero?
The next renewal is rejected, syncing stops, and Biznsbook raises an Attention Center item asking you to reconnect. It does not keep retrying a dead authorisation.
How this differs by industry
Retail
Retail groups in Australia and New Zealand can keep Xero as the accounting system of record while running stock, purchasing, and POS in Biznsbook against the same invoice numbers.
Wholesale & distribution
Wholesalers gain per-line account codes and tax types on every invoice, which is usually the first thing an external accountant asks to see before signing off an integration.
Manufacturing
Manufacturers keep production costing in Biznsbook and let the accountant work in Xero, with the organisation chosen explicitly so multi-entity groups do not cross their books.