For many New Zealand businesses, Xero sits at the centre of everything. Around it sit an inventory system, payroll, quoting or job management, a CRM, and freight. Each connection promises to save time. Connect them in the wrong order, or without deciding which system owns what, and you get duplicate contacts, mismatched totals and a clean-up every month-end.
Here is how we sequence integrations around Xero, and the decisions that matter more than the connector itself.
Get the basics right first
Start with bank feeds, because they make reconciliation fast and reliable. Before connecting anything else, make sure bank reconciliation is up to date and the chart of accounts is tidy.
That sounds like housekeeping, but it matters. Every other integration will post transactions into Xero, and you need a clean baseline to check them against. Connecting a new system to a ledger that’s three months behind makes it very hard to tell whether the integration is working.
Then connect where the volume is
The simplest rule for what comes next: connect the system that creates the most transactions your team currently re-keys.
Inventory. For distributors and wholesalers, the inventory system generates sales invoices, purchase bills and stock movements every day, so it’s usually the first big connection. Cin7 Core, for example, connects to Xero by importing your Xero accounts and mapping its tax rules to Xero tax rates. That mapping is where most of the important decisions sit, so give it proper attention.
Payroll. Payroll is lower volume but high stakes. On its Payroll classic platform, Employment Hero can post payroll journals into Xero automatically when a pay run is finalised. Get the account mapping right once, and payroll stops being a manual journal every pay cycle.
Job management and quoting. For trades, construction and service businesses, the job system pushes invoices and costs into Xero. Watch for adjustments made directly in Xero, such as a credit note, that never flow back to the job. That’s how job margins and the accounts drift apart.
CRM. A CRM usually sends less into Xero than people expect. Its value is in keeping customer details and quotes in one place, so decide carefully which fields it owns.
Freight. Freight costs often arrive as one monthly bill. Matching them back to individual orders is what shows your real margin by customer, so freight is worth connecting once the bigger systems are stable.
Decide which system owns what
Xero is the hub for money. It doesn’t have to be the master for everything. Before connecting a system, write down which one owns each kind of data:
| Data | Usually owned by |
|---|---|
| Customer names, contacts and addresses | CRM or job management system |
| Credit terms and outstanding balances | Xero |
| Products, stock levels and prices | Inventory system |
| Chart of accounts and tax rates | Xero |
| Employees, leave and pay | Payroll system |
Ownership is often per field rather than per record. A customer’s address might belong to the CRM while their payment terms belong to Xero. Each system should only change the fields it owns and read the rest. Most sync problems disappear once this is written down and agreed.
Decide how much detail Xero needs
Not every system needs to send every line into Xero. Some integrations post each invoice in full. Others post a daily summary instead.
Full detail lets your accountant drill into any transaction. Summaries keep Xero lean and fast. The right answer depends on what your accountant and your reporting need. If you want detailed analysis, such as margin by product line across several systems, it’s often better to keep the detail in the source systems or a separate reporting database, and keep Xero focused on the accounts.
Off-the-shelf connector or custom integration?
Ready-made connectors are the right place to start. They’re built, maintained and supported by the vendor, and they cover the common cases well.
A custom integration is worth considering when:
- No connector exists, or the one that does doesn’t sync what you need.
- You need logic in between, such as approvals, splitting costs across jobs, or setting tracking categories consistently.
- You need data to flow back from Xero, such as payment status or planned payment dates, into another system.
- Volumes are high. Xero publishes API limits that every integration has to work within, so high-volume syncs need to be designed around them.
Custom integrations need the same care as any other system: logging of every outcome, sensible retries when Xero is busy, and alerts that reach a person who will act on them.
New Zealand details to get right
- GST. Make sure tax rates map correctly in every connected system. A wrong tax code in one system flows straight into your GST return.
- Financial year. If you run an April to March year, check that each connected system’s reporting periods line up with Xero’s.
- Tracking categories. If you use them for regions, branches or departments, agree how each connected system sets them, so reports by category stay complete.
This is general information, not tax advice.
Before you connect the next system
Work through this checklist each time:
- Bring bank reconciliation up to date.
- List every system and roughly how many transactions are re-keyed from each every month.
- Connect the highest-volume system first.
- Write the ownership table for customers, products, prices and anything else that moves.
- Map accounts, tax rates and tracking categories, and ask your accountant to check the mapping.
- Decide on detail or summary for each type of transaction.
- Run a parallel period and reconcile totals between the two systems before switching off manual entry.
- Name the person who watches for failed syncs, and agree how quickly they’ll act.
Where to start
Count the transactions your team re-keys into Xero each month, system by system. The biggest number is usually where to start. If you’d like help planning the order or building a connection that doesn’t exist yet, see our integration and automation work, or get in touch.