Many UK businesses run operations in one system and keep their accounts in Xero. The question is rarely whether to connect the two. It is what should cross between them, which system owns each record, and how the team avoids typing the same invoice twice. An ERP Xero integration is less a single switch and more a set of rules that everyone agrees to follow.
Those rules matter because the two systems answer different questions. The ERP tracks orders, stock, jobs, purchasing and approvals as they happen. Xero holds the ledger, the bank feeds and the VAT figures that an accountant will review. A good connection lets each system do its job without making staff copy information from one to the other.
Xero is one of several accounting platforms UK businesses use, and the principles here apply to others as well. This guide covers what to sync, how invoices and payments should move, how the chart of accounts can be mapped, VAT at a general level and the habits that stop double entry from creeping back. It is aimed at finance leads, operations managers and owners planning a project rather than configuring one.
Decide which system owns each record
Before any data moves, decide who creates and changes each type of record. This is the most useful step in any ERP Xero integration project, because it stops two systems editing the same thing and then disagreeing about which version is correct.
Ownership by record type
A simple way to decide ownership is to list each record type and name the system and the team responsible for it. Customers, products, orders, invoices, payments and stock are the usual candidates. The owner is normally the system where the record is first created and most often changed. A typical split looks like this.
- Customer and supplier contacts: owned where accounts are set up
- Products and prices: owned by the system that controls the catalogue
- Sales orders and dispatch: owned by the operational system
- Invoices and payments: owned by one system, agreed with finance
- Chart of accounts and tax settings: owned by finance
Why two-way sync needs careful rules
Two-way sync sounds convenient, but it creates conflicts. If a contact name changes in both systems on the same day, something has to decide which version wins. Many teams find that one-way flows for each record type are easier to understand and easier to fix when something goes wrong, with two-way flows kept for a small number of fields.
What to sync in an ERP Xero integration, and what to leave out
It is tempting to sync everything, but a larger flow creates more ways for things to break. Start with the records that finance needs to see, and leave out detail that only belongs in the operational system.
Core records that most projects begin with
Many ERP Xero integrations begin with contacts, products or items, invoices, credit notes, bills, payments and the tax rates each line uses. These records are what the ledger needs to be complete, and what the accountant relies on at period end. The starting list usually covers the following.
- Contacts for customers and suppliers, with tax and payment terms
- Products or items, with sales and purchase accounts
- Sales invoices and credit notes, with a tax rate on each line
- Supplier bills and the payments made against them
- Customer receipts, matched to the invoices they settle
Records that stay in the operational system
Detailed stock movements, individual picks, production steps and internal approval notes usually belong in the ERP. Xero needs the financial result of those activities, not every step that led to it. Daily or periodic summaries can carry the totals that matter, such as sales by category or the value of stock received.
Invoices: numbering, status and timing
Invoices are where most integration questions surface first. Who numbers them, when they reach the ledger, and what happens if an invoice changes after it has been sent are all decisions to make in advance.
One numbering sequence
Only one system should issue invoice numbers. If both systems can number invoices, the sequence will eventually collide or skip, and the accountant will spend time explaining the gaps. Decide which system holds the sequence, and make the other system use the number it is given.
When an invoice reaches the ledger
An invoice can be sent to Xero when it is approved, when goods are dispatched, or at the end of a period in summarised form. Each choice has different effects on timing and on how much detail the ledger shows. Agree the trigger with the accountant so that month-end figures match what the business expects. The invoice payload should carry the following.
- Invoice number, date, due date and customer reference
- Each line's product, quantity, unit price and tax rate
- Voided or edited invoices handled by one clear rule
- Delivery references kept in the ERP and linked where possible
Payments and bank reconciliation
Payments are the point where a sales cycle closes in the books. The risk is that the same receipt is recorded once in the ERP, once through a bank feed and once by hand, which leaves the bank out of step with the ledger.
Matching receipts to invoices
A receipt should settle the invoice it relates to, whether it arrives in full, in part, or as one payment for several invoices. Decide whether the ERP or Xero owns the matching step. Whichever it is, the other system should not repeat it, so that balances stay right.
Refunds, credit notes and write-offs
Refunds, credit notes and small write-offs should link back to the invoice they reverse. Otherwise a customer's balance can look wrong even when the business has acted correctly. Keep one clear path for each type, so the accountant can follow every movement without asking how it was booked.
- Payments matched to invoices, with partial payments tracked
- Bank feed lines matched once, not recorded again by hand
- Credit notes linked to the original invoice and a stated reason
- Write-offs approved and posted to a named expense account
Mapping the chart of accounts
The chart of accounts is the list of ledger accounts that every transaction posts to. An integration works best when every sales type, cost type and tax treatment maps to a known account in advance. A single mapping table makes this visible and gives finance one place to review changes.
Mapping operational activity to accounts
Product categories, revenue streams and cost types in the ERP should each point to a specific account in Xero. Avoid mapping several unrelated activities to one general account, because reports will then answer the wrong questions. A short review each quarter keeps the mapping in line with how the business has changed.
Using tracking categories for reporting
Xero supports tracking categories, which let finance report by department, site, project or region without creating a new account for each one. Where the business already reports by job or site, carrying that tracking into the ledger can save a good deal of manual analysis later. Confirm the set-up with your accountant before relying on it.
- One mapping table, owned by finance and reviewed regularly
- Revenue accounts split by product group where reporting needs it
- Cost accounts mapped to the categories the budget uses
- Tracking categories limited to the views the business really uses
VAT handling at a general level
VAT is where a sensible integration design earns its keep. Each line on each invoice carries a tax treatment, and that treatment must reach the ledger correctly for the VAT return to be right. The details depend on what is sold, where it is supplied and who buys it, so the rules should be agreed with a qualified accountant rather than copied from a general guide.
Carrying the tax treatment on every line
The simplest rule is that every line in the ERP carries a tax treatment, and that treatment is mapped to the matching tax rate in Xero. Standard-rated, reduced-rated, zero-rated, exempt and outside-scope sales are different categories, and the mapping should make each one explicit rather than defaulting silently.
Reverse charge, overseas sales and credit notes
Some transactions, such as certain purchases from overseas suppliers or purchases in particular sectors, use the reverse charge. Sales to customers abroad follow their own rules. Credit notes should reverse the original tax treatment. The ERP should be able to flag these cases for review rather than posting them automatically.
Making Tax Digital
Under Making Tax Digital for VAT, VAT-registered businesses must keep their VAT records digitally and file their returns through compatible software. An ERP Xero integration sits within that picture, so the accountant should confirm how the flow of data supports the return. This section is a general overview and does not replace that advice. Before go-live, confirm the following.
- Tax treatments agreed with the accountant before go-live
- Reverse charge and overseas transactions flagged for review
- Credit notes keep the original tax treatment
- VAT return figures reconciled to the ledger each period
Avoiding double entry in an ERP Xero integration
Double entry rarely comes from one big mistake. It usually creeps back through small habits: an invoice typed into Xero because the sync looked slow, a payment entered twice, or a new contact created in both systems. The design has to make the right path the easy one, and it has to show problems quickly.
Where double entry creeps back
Staff under pressure will often enter information in whichever system they trust most at that moment. If the ERP is slow to sync, someone will create the invoice in Xero to get paid faster. Make the sync reliable, make its status visible, and agree a rule that nothing is keyed twice without a recorded reason.
Monitoring, exceptions and ownership
Every integration should have an exception queue that lists failed transfers, duplicates and unmatched items, with a named owner who clears it on a set schedule. A daily reconciliation between the two systems catches differences while they are still small. Without an owner, exceptions build up quietly until the month-end close. The queue should flag the following.
- Failed transfers listed with the reason for failure
- Possible duplicate contacts and invoices flagged for review
- Daily totals compared between the ERP and Xero
- A named person responsible for clearing exceptions
FAQ
What should be synced between an ERP and Xero?
Many projects start with contacts, products, invoices, credit notes, bills, payments and tax rates, because those are what the ledger needs. Detailed operational records, such as individual picks or production steps, usually stay in the ERP with summarised totals passed to Xero. The right list depends on what the accountant needs to close each period.
Should invoices be created in the ERP or in Xero?
Usually the system where the sale is approved should create the invoice, and the other system should receive it rather than re-create it. The key is to decide the owner in advance and to use one numbering sequence. Whichever you choose, agree the trigger point with finance.
How do you avoid double entry between an ERP and Xero?
Give each record type one owner, make the sync reliable and visible, and agree that nothing is keyed twice without a reason. Daily reconciliation and a named person for exceptions catch problems early. Staff stop double keying when they trust the sync, so reliability matters as much as design.
Does an ERP Xero integration handle VAT automatically?
It can carry the tax treatment from the ERP into Xero, provided each line is mapped correctly. The correct treatment depends on what is sold, where it is supplied and who buys it, so the mapping should be agreed with a qualified accountant. Automation speeds up the flow, but it does not decide the treatment on its own.
How should the chart of accounts be mapped?
Each product group, revenue stream and cost type in the ERP should map to a specific account in Xero, through a single mapping table owned by finance. Avoid mapping unrelated activity to one general account, because reports will then mislead. Review the mapping each quarter as the business changes.
What happens when a sync fails?
A well-designed integration lists the failed transfer with its reason and holds it in an exception queue rather than losing it. A named person clears the queue on a set schedule, and the daily reconciliation confirms that totals agree. Without that routine, failures can sit unnoticed until month end.
Final thought
An ERP Xero integration works when the business knows which system owns each record, what crosses the boundary, and how tax and payments are treated. The technology matters less than the agreement behind it. A short written set of rules, reviewed with the accountant, will do more to protect the figures than any single setting.
A sensible first phase is usually the flow that removes the most double entry, typically invoices and payments, followed by a carefully mapped chart of accounts. Add the more detailed records once the core flow has run cleanly through a full month-end.
Mirex Agency works with small and mid-sized UK businesses on ERP solutions. If your team is keying the same information into two systems, a conversation about which records belong where is a sensible starting point. The ERP solutions page is at mirexagency.com/services/erp-solutions.
