Why "integrates with Xero" isn't enough
Many CRMs list Xero as an integration. That phrase can mean almost anything. It might mean every invoice, contact and payment moves both ways in real time. It might mean a button that copies one invoice when you remember to press it.
The difference matters. A good connection saves your team re-typing invoices and lets sales see who has paid. A poor one creates duplicate contacts, mismatched invoice numbers and VAT on the wrong rate, which your bookkeeper then has to untangle.
This guide lists the questions to ask about any CRM that connects to Xero. They apply whichever product you're considering.
Start with your accountant
Before you look at products, talk to whoever looks after your books. Ask them:
- Which records should start in the CRM, and which should start in Xero?
- Should invoices arrive in Xero as drafts or approved?
- Which sales account should invoice lines go to?
- Which VAT rates do you actually use?
- Who reconciles payments, and where?
[STEVEN: what your own accountant or bookkeeper asked when you connected Xero.]
Their answers become your checklist. An integration that fights how your accountant works will cost more time than it saves.
1. Which way does data flow?
This is the most important question, and "two-way sync" doesn't answer it. Ask about each type of record separately:
| Record | Questions to ask |
|---|---|
| Invoices | Created in the CRM and sent to Xero? Or created in Xero and copied back? |
| Credit notes | Are they sent at all? In which direction? |
| Contacts | Pushed to Xero, pulled from Xero, or both? |
| Payments | Recorded where, and copied which way? |
| Quotes and orders | Do they go to Xero, or stay in the CRM? |
| Products | Are items or price lists synced? |
A clear one-way flow for each record is often safer than vague two-way sync. It's obvious which system is the source of truth, so there's nothing to argue about.
2. What exactly syncs?
For each record that moves, ask what goes with it. For an invoice, check:
- the line descriptions, quantities and prices
- the VAT rate on each line
- discounts
- the due date and reference
- the account each line posts to
- any tracking categories you use in Xero
Also ask what doesn't sync. A supplier who tells you plainly what's left out is easier to trust than one who says "everything".
3. When does it sync?
Ask whether each sync happens:
- instantly, when something happens (for example, when an invoice is issued)
- on a schedule, such as every hour or every night
- only when someone presses a button
Then think about what that means day to day. If payments come back once a night, sales may still see an invoice as unpaid on the morning after the customer settled. That may be fine. It just needs to be known.
4. What status do invoices arrive in?
Some integrations post invoices to Xero as drafts, for someone to approve. Others post them as approved. Neither is wrong, but it changes who does what. Drafts give your bookkeeper a check. Approved invoices save a step, but only if you trust what's being sent.
Also ask: are draft invoices in the CRM ever sent to Xero? Usually they shouldn't be.
5. Do invoice numbers match?
If the invoice your customer holds says INV-0142, the invoice in Xero should say the same. If the numbers differ, every payment query becomes a lookup exercise.
Ask:
- Which system sets the invoice number?
- What happens if Xero already has an invoice with that number?
- Do credit notes keep their numbers too?
6. How are VAT rates mapped?
VAT is where a poor integration does real damage. Your CRM has its own idea of VAT rates. Xero has its own tax rates. Something has to match one to the other.
Ask:
- Can you map each VAT treatment you use (standard, reduced, zero-rated, exempt and so on) to a specific Xero tax rate?
- What happens if a rate isn't mapped? Does the invoice stop with a clear message, or is a default rate used?
A default rate is a risk. An invoice posted at the wrong rate flows into your VAT return. Stopping with a message is less convenient but much safer. Check this with your accountant.
7. How are contacts matched?
When the CRM sends an invoice for a customer, it has to find that customer in Xero. Ask how:
- by a stored link, after the first match?
- by exact email address?
- by name, and is it an exact or a fuzzy match?
- what happens when there's no match?
Fuzzy matching sounds helpful, but it can merge two different customers with similar names. An exact match, with a new contact created when there isn't one, is more predictable.
[STEVEN: a duplicate-contact mess you've seen, and how long it took to sort out.]
8. What happens when things conflict?
Sooner or later, the two systems will disagree. Someone edits an invoice in Xero. Someone voids an invoice in one system but not the other. A customer overpays.
Ask:
- If an invoice is edited after it's sent to Xero, is the change re-sent, ignored or flagged?
- If an invoice is voided in Xero, what happens in the CRM?
- Are odd cases, like overpayments, applied automatically or flagged for someone to review?
- Where can you see which records failed to sync, and why?
Look for a visible sync status on each record and a way to retry a failed one. Silent failures are the worst kind.
9. Setup, permissions and cost
A few practical checks:
- Who can connect? Ideally only an admin can connect or disconnect Xero and change mappings.
- Which Xero organisation? If you run several, can you choose the right one?
- What about past invoices? Are they backfilled, or does sync start from the day you connect?
- What does it cost? Is the connection included, or a paid add-on or higher tier?
Test it before you commit
Use a free trial and Xero's demo company, or a test organisation, if you can. Then:
- Create a customer and issue an invoice with two VAT rates.
- Check it appears in Xero with the right number, contact, account and tax rates.
- Record a payment in Xero and see how long it takes to show in the CRM.
- Raise a credit note and check it follows.
- Leave a VAT rate unmapped and see what happens.
[STEVEN: what you check first when testing an integration like this.]
An example of clear answers
As an example of what clear answers look like: in Beagle CRM, issued invoices and credit notes go to Xero as approved documents under the same number, contacts are matched by exact email and then exact name, payments come back from Xero every hour, and an unmapped VAT treatment stops the sync with a message. Quotes and orders stay in Beagle. You can read the full detail on how Beagle works with Xero, including what it doesn't do.
Whichever CRM you choose, get answers like that in writing before you connect it to your books.