Integration guides
How to integrate a CRM with accounting software
Nicolas Blassel, Co-founder
A deal is won on Tuesday. On Friday finance asks sales for the billing address, types the client into the accounting system and spells the name a little differently. Nobody in the client-facing team can answer "have they paid?" without walking over to finance.
The short answer, from what I see in firms of 10 to 50 people: to integrate a CRM with accounting software is rarely hard technically. Most popular CRMs and accounting packages have a native connector or work with Zapier or Make. What makes the integration succeed or fail is three decisions you make before switching anything on: which system owns each type of record, which direction each record flows, and how the integration recognizes a client it has already seen. Get those right and the tool choice is almost secondary.
What does it cost when the CRM and accounting do not talk?
In most firms I see, it is not one big failure. It is a string of small ones.
- A partner sends a proposal to a billing address that was corrected in accounting months ago.
- A won deal waits for its invoice until someone remembers to ask.
- The same client exists twice in accounting, and the debtors list never quite agrees with the CRM.
- A salesperson chases a client for a proposal that finance has already been paid for.
None of this costs much on the day. Over a year it is late billing, hours of retyping and a team that stops trusting either system.
Decision 1: which system owns each record
A source of truth is the one system where a piece of information is created and corrected. Everywhere else holds a copy. Without one, two people edit the same client in two places and the integration has to guess who is right.
A split that works for most professional services firms:
| Record | Usually owned by | Why |
|---|---|---|
| Prospects, contacts, companies | CRM | Sales and intake create them first |
| Deals and proposals | CRM | Pipeline work happens there |
| Billing customer (legal name, tax number, billing address) | Accounting | Finance is accountable for invoices being correct |
| Invoices, credit notes, payments | Accounting | The ledger must be authoritative |
| Products and services | Accounting, or one agreed list | Line items must match the revenue accounts |
The handover point matters. A common pattern is that the CRM owns a client until the deal is won; at that moment the integration creates the billing customer in accounting, and from then on billing details are corrected in accounting only. I would write this down in one page that the whole team can find, and I would get the partners to agree it before anyone connects anything. Check the billing customer structure with your accountant, especially if clients have several entities or you bill in more than one currency.
If you run an accounting firm, the "CRM" is often your practice management tool rather than a sales system. Karbon, for example, holds the client contact, the work and the billing, and according to Karbon's help centre it connects to Xero, QuickBooks Online Accountant and HubSpot. Our guide to Karbon, Xero and HubSpot for accounting firms shows how that chain fits together.
Decision 2: one-way or two-way, per record
Two-way sync sounds better, but it means an edit on either side overwrites the other, and you need rules for what happens when both change at once. One-way sync is easier to reason about and easier to troubleshoot.
A practical default:
- CRM to accounting, one way: a new won client creates the billing customer; optionally a won deal creates a draft invoice for finance to review.
- Accounting to CRM, one way: invoice status, payments and outstanding balance appear on the CRM record as read-only information.
- Two-way only where both teams genuinely edit the same field, and only after you have decided which side wins.
Native connectors often let you choose direction per object. HubSpot's Xero integration, for example, offers one-way or two-way sync for contacts and products, according to HubSpot's setup guide. Our HubSpot and Xero guide covers that pair in detail. Law firms have extra rules to think about, because trust accounting must follow your jurisdiction's requirements.
When a partner asks me for two-way everywhere, I usually ask who will settle the argument when sales and finance disagree about an address. If nobody can answer, it should be one-way.
Decision 3: how the integration recognizes a client
Duplicates are the most common failure in CRM and accounting integrations, and they come from matching on the wrong thing. Each system has its own idea of what makes a record unique:
- HubSpot automatically deduplicates contacts by email address and companies by domain name, according to its knowledge base. Companies created through the API, including by sync apps, are not deduplicated by domain, so an integration can still create duplicate companies.
- QuickBooks Online requires a customer's display name to be unique across customers, vendors and employees, according to Intuit's Customer API documentation. An automation that tries to create "Smith & Co" when it already exists will error.
- Xero lets you merge contacts after the fact, but notes that if you use Xero Projects, a project's contact does not update when merged.
Matching on a company name is fragile: "Smith & Co", "Smith and Co" and "Smith & Co Ltd" are three clients to a computer. The reliable approach is for each system to remember the other's identifier for the client, so that later steps look the client up by that identifier and not by name. If your CRM represents people and your accounting system represents companies, decide explicitly which CRM record corresponds to the billing customer.
Clean your data before you integrate a CRM with accounting software
An integration copies whatever is already there, including the mess. Before going live, I would want these done, and most of them only your team can do:
- Line up the client lists from both systems and agree which entries are the same client.
- Merge duplicates on both sides.
- Archive clients nobody has billed or contacted in years, following your firm's record retention rules.
- Fill in missing billing emails and tax numbers on active clients.
Which "J. Martin" is the real client is something only your team knows, and a sync will copy the wrong one faithfully.
Native connector or automation platform?
When you integrate a CRM with accounting software, start with the native connector if one exists. It is maintained by the vendor, usually cheaper, and covers the common case of syncing contacts, invoices and payments. Here are common pairs that have one, each with the vendor page that says so (checked November 2026; plans and regions vary, so confirm on the page before you rely on it):
| Pair | Native connector | Vendor source |
|---|---|---|
| HubSpot and Xero | Yes, one-way or two-way per object | HubSpot setup guide |
| HubSpot and QuickBooks Online | Yes, contacts, invoices and products | HubSpot marketplace listing |
| Karbon and Xero | Yes, contact and invoice sync | Karbon help centre |
| Karbon and QuickBooks Online Accountant | Yes, contacts, invoices and payments | Karbon QuickBooks overview |
| Karbon and HubSpot | Yes, HubSpot contacts sync into Karbon | Karbon help centre |
Reach for Zapier or Make when you need logic the connector does not offer:
- A won deal creating a draft invoice with specific line items.
- A payment triggering onboarding tasks or a notification to the account lead.
- A third system in the chain, such as a document signing tool or practice management system.
- A CRM with no native connector to your accounting package, as with Salesforce and QuickBooks; see our Salesforce and QuickBooks guide.
The one rule for mixing them: never let two tools write the same record. If the native sync creates customers, the automation should look customers up, not create them. This is the rule I see broken most often, usually by two people who each added a helpful automation a year apart.
This is where the connectors stop being enough on their own. The vendor pages tell you what syncs. They do not tell you which system your firm should trust for each field, what happens when a client has two entities, or what to do when a sync fails on the last day of the month. If you are not sure how your CRM and accounting should hand a client over, tell us what your firm runs today and I will say what I would check first.
What does a proper CRM and accounting integration involve?
Switching on a connector takes minutes. The work is in the stages around it, and I would not skip any.
- Decide. Who owns each record, which way it flows and where the handover happens. Write it on one page, with the partners and the person who does the billing in the room.
- Clean the data. Duplicates merged, old clients archived, billing details filled in.
- Map. How a CRM record lines up with the billing customer, and how products and services line up with revenue accounts. This is judgement about how your firm reports its income, not a form to fill in.
- Test. Run the awkward cases through: a returning client, a client with two entities, a name that changed, a part-paid invoice, a sync that fails halfway. Tidy sample records tell you very little.
- Switch over. Go live one flow at a time, keep the old routine until the new one has proved itself, and watch the failures closely for the first weeks.
Keep it healthy after launch
Mappings drift as the firm changes.
- Name an owner who checks the sync log or error alerts weekly.
- Use a firm-owned login for every connection, not an individual's account that disappears when they leave.
- Change fields deliberately. Renaming a CRM field or changing a tax code can quietly break a mapping.
- Review quarterly whether the mapping still matches how the firm works.
Do it yourselves or have it done?
If you have one CRM, one accounting package, a native connector that covers your case and one person who knows both, you can probably do this yourselves. Start with the one-page ownership table and the cleanup.
I would get help when:
- Nobody agrees which system holds the right billing details for a client.
- The same client already exists several times in accounting or the CRM.
- Clients have several entities, or you bill in more than one currency.
- You want a won deal to create a draft invoice, or a payment to start onboarding, without anyone retyping.
- The person who set up your current connections has left, and nobody knows what is switched on.
In those cases the risk is not the connector. It is a duplicate client or a wrong invoice, found when a client calls.
How Flow Mesh helps
We are a small team of specialists who connect the software firms already use and take the repetitive work between those systems off their people. Our stack audit looks at your CRM, accounting software and the tools around them, gives each a verdict (keep, configure, consolidate or replace), and sets out in writing which system owns each record and which way it should flow. If you want us to build it, the integration work is scoped and quoted in writing after the audit and done inside your own accounts. If the same client is still typed twice in your firm, contact us and tell me what your CRM and accounting tools are.
