A CRM and an accounting system can share customer information without both being allowed to change everything. Before connecting them, decide which system controls each field and what should happen when they disagree.
The difficult part is rarely copying a name. It is deciding whether the salesperson's new address is also the address that should appear on an invoice.
Start with one customer journey
Imagine a small maintenance business, used here as a fictional example. A sales administrator marks a quote as accepted. Finance checks the billing details and prepares an invoice in the accounts system. The CRM should then show that an invoice exists, so nobody chases the customer for information already supplied.
That does not require every CRM contact to become an accounting contact. Define the point at which a prospect becomes a customer, whether a person or company is being billed, and who can authorise the handover.
Write the expected outcome in ordinary language: “An approved customer appears in accounts once, with the right billing details, and sales can see the invoice reference.”
Give each field a clear owner
For that fictional business, a useful first mapping might be:
- Sales contact and preferred telephone number: the CRM controls them.
- Legal billing name and invoice address: finance confirms them before accounts accepts a change.
- Invoice number, outstanding balance and payment status: the accounting system controls them.
- Sales notes: stay in the CRM unless a specific note is needed for billing.
This is an example policy, not a requirement of a particular platform. Ask staff what each field actually means. An empty CRM field should not automatically erase a valid accounting value. A cancelled sale should not silently delete an invoice.
Keep the identities as well as the details
An email address can change. Two companies can have similar names. One business can have several billing accounts.
Xero's contacts documentation recommends using its ContactID to identify contacts rather than relying on their names. HubSpot's contacts guide also provides record IDs and supported identifier-based operations. The identifiers belong to their respective systems. A connection needs to retain the relationship between them.
Ask how that mapping is stored, who can correct it and what happens if two possible matches are found. A review task is preferable to guessing which customer's billing record to update.
Test disagreement, not just a new customer
Use fictional records in an authorised test setup. Include a new customer, an existing customer with a changed trading name, two similar names and a customer whose billing contact differs from the sales contact.
Then change the same field in both systems. Show which value wins and why. Check a blank field, an archived customer and a failed transfer that is retried. Confirm that invoice amounts and payment status cannot be changed merely by editing the CRM.
Finance should inspect the result inside the accounting system. A green integration log is not evidence that the correct customer will receive the next invoice.
Keep the first release narrow. One approved customer handover and a read-only invoice status can remove useful work without creating a second place to edit the books.