How do you stop re-keying data between your CRM, accounting and project tools?

A new customer signs. Sales creates them in the CRM. Finance creates them again in accounting, slightly differently. Operations sets them up in the project tool with a shorter name because the field was small. Three months later an invoice goes to the wrong address, a report shows two customers where there is one, and someone spends a Friday afternoon working out which version is right.

Nobody chose to run the business this way. Each system was bought for a good reason, by a different team, and the gap between them was filled by people typing. The typing is the part that can go.

What re-keying costs, beyond the typing

The hours are the visible cost. Someone with real skills spends part of every day copying fields from one screen to another, and that time never appears on a budget line because it's spread across six people in small pieces.

The hidden cost is bigger. Every copy is a chance to make a mistake, and the mistakes don't show up where they were made. A mistyped payment term in accounting becomes a late payment. A missing job reference in the project tool becomes an invoice that can't be reconciled. A customer who changed address and only told one department keeps getting post at the old one. Each of these takes an hour to untangle, and someone has to notice first.

There's a third cost, which is that nobody trusts the numbers. When three systems disagree about how many active customers you have, every report starts with a caveat, and decisions get made on whichever version was quoted most recently.

Give every record one owner

The fix starts with a decision, not a tool. For each kind of record, name the system that owns it. The owner is where the record is created and changed. Every other system holds a copy that it is not allowed to edit for the fields the owner controls.

• Customers and contacts: usually the CRM, because that's where they first appear.
• Invoices and payments: accounting, always.
• Jobs, projects and their status: the project tool.
• Products and prices: wherever your price list really lives, which is sometimes a spreadsheet, and that's worth fixing on the way.

Then agree one reference that travels with the record. A customer number, a job number, an order number, generated once by the owner and written into every copy. Without a shared reference, connecting the systems means matching on names, and names are how you got into this.

How the connection works

Once the owners are decided, the automation is a set of carries. When a record is created or changed in its owner, the change is picked up, translated into the shape each other system expects, and written there. A new customer in the CRM becomes a customer in accounting with the same name, address and payment terms, and a client in the project tool with the same reference. A status change on a job becomes a note on the deal. An invoice posted in accounting becomes a line on the customer's record that sales can see before they call.

Three things make this hold up in daily use.

• Every carry is logged: what changed, where, when, and what was written on the other side. When a value looks wrong, you can follow it back to where it came from instead of guessing which system to blame.
• Conflicts go to a person. If two systems were changed in different ways before the carry ran, nobody wants a machine to pick a winner. The two versions go to whoever owns that record, side by side, with one click to choose.
• The old way is switched off. If people can still create a customer directly in accounting, they will, and the copies drift again. The owner system becomes the only door.

Whether a carry needs AI or plain integration depends on what's being carried. Mapping a field to a field is integration and should stay that way. Reading a free-text note and deciding which job it refers to, or spotting that two differently spelt customers are the same company, is where a model earns its place. Most connections are mostly the first kind, with a little of the second at the edges.

What to carry, and what to leave alone

Not every field needs to travel. Decide, for each record, which fields the other systems need to do their job and carry only those. Accounting needs the customer's legal name, billing address, payment terms and the shared reference. It does not need the sales notes, the deal stage or the contact's birthday. Carrying less means fewer conflicts and a log that's easier to read.

Decide the timing too. Most carries should happen within minutes of the change, so a deal marked won this morning is a customer in accounting before the invoice is raised. A few are better in a nightly batch, such as a large status update across hundreds of jobs. And some fields should never be carried at all: anything one system calculates from its own data, such as an outstanding balance, is read from that system when needed rather than copied around and allowed to go stale.

Attachments and documents are a case of their own. A signed proposal usually belongs in one place, with the other systems holding a link to it rather than a copy. Three copies of a contract is how you end up with three versions.

Where to start

Start with the record that causes the most arguments. For most businesses that's the customer, because it's created early, changed often, and used everywhere. Connecting customers between the CRM and accounting removes the bulk of the typing in one move and fixes the report that nobody believes.

1. List the systems the record lives in today and who creates it in each.
2. Name the owner and the shared reference. Expect a short, useful argument.
3. Clean the existing records once. Merge the duplicates, fix the addresses, assign the reference. The automation keeps records in step from here; it doesn't repair the past.
4. Connect the owner to one other system. Run it on new records only for a few weeks while people watch the log.
5. Add the next system, then the next record type.

The one-off clean-up is the step people try to skip, and it's the one that decides whether the first weeks feel like relief or chaos. It's a few days of someone's attention, done once.

What changes for the team

Sales stops being asked for the customer's details a second time. Finance stops setting up customers at all; they appear, complete, when the deal is marked won. Operations opens a job and finds the client already there. The weekly argument about the customer count stops, because there is one count. And the person who used to spend Friday afternoon reconciling gets Friday afternoon back.

The same connection is what makes the weekly report possible. A report assembled from systems that disagree is a report nobody acts on; once the records agree, the report can assemble itself.

What to measure

• Hours of manual work removed each week: ask each person who re-keys today how long it takes, and count again a month after the connection goes live.
• Errors and re-work in your records: duplicate customers found, invoices sent to the wrong address, jobs with a missing reference, counted monthly.
• Records in step: a simple check that the customer count, and a sample of addresses and terms, agree across systems.

These sit on our Operational Efficiency page under keeping records in step across systems. If you'd like to talk through which systems you run and where the copies drift, that is what the first call is for.