Reconciliation and data syncing are different jobs
Syncing copies data from one system to another. If a record is incomplete, changed later or never copied, both systems can still agree and both can still be wrong.
Reconciliation is an independent check of the two systems against each other, to confirm that every deal has a correct invoice.
What to match
| HubSpot field | Xero field | Notes |
|---|---|---|
| Deal ID or custom reference | Invoice reference or number | Best key if stored consistently |
| Company | Contact | Names often differ slightly |
| Deal amount | Invoice total (ex and inc VAT) | Watch tax treatment and currency |
| Close date or milestone date | Invoice date | Allow for timing lag |
| Line items or products | Invoice lines | Useful for partial invoices |
The six mismatches you will meet
- No invoice for a closed deal (unbilled)
- Invoice amount lower than the deal (partial or under-billed)
- Invoice with no matching deal (manual invoice or missing CRM record)
- Duplicate invoices for one deal
- Tax or currency differences that look like errors but are not
- Timing lags (deal closed this month, invoiced next month)
A manual method
- Set the period: choose the months to review and a cut-off date.
- Export from both systems: closed-won deals from HubSpot and invoices from Xero, with a margin either side of the period.
- Create a shared key: use the deal ID or invoice reference where it exists.
- Match exact keys: pair every record that shares a reference.
- Match on customer and amount: allow a small tolerance for VAT and rounding.
- Match on customer and date window: catch invoices raised a little before or after the close.
- Triage exceptions by value: start with the largest amounts at risk.
- Fix and document: raise or correct invoices and note the cause of each gap.
Run it monthly at minimum.
Making your data easier to reconcile
- Store the HubSpot deal ID on the Xero invoice reference (or the invoice number on the deal).
- Standardise customer names.
- Record scope amendments on the deal, not only in email.
- Agree a rule for when a deal triggers an invoice.
How Auditor Alpha helps
- Compares HubSpot deals with Xero invoices using three matching layers, so it works even when no shared reference exists.
- Handles tolerance, VAT, currency and timing differences, so you see fewer false alarms.
- Checks every 2 hours rather than once a month.
- Shows every mismatch with its evidence and a suggested fix.
- Read-only access: nothing is written back to HubSpot or Xero.
Read more: the HubSpot and Xero integration.
Illustrative example
Deal “Platform Build”, £48,200, closed on 4 March. Xero holds an invoice for £40,160 plus VAT, dated 12 March. The totals look different, but £40,160 plus 20% VAT is £48,192, so the £8 gap is small enough to fall within the matching tolerance, not a billing error. A tolerance rule treats this as a match, where a strict comparison would raise a false alarm.
All names and figures in this example are illustrative, not real customer data.
Frequently asked questions
Does syncing data mean my records are reconciled?
Not necessarily. A sync moves data; reconciliation checks that every deal has a correct invoice.
How often should I reconcile?
Monthly at minimum, and continuously if volume or risk is high.
What if my deals do not store invoice numbers?
Match on customer, amount and date window. Auditor Alpha's semantic matching does this automatically, and you can start storing a reference going forward.
Does Auditor Alpha change my data?
No. It is read-only. Corrections stay with your team.