Published: September 18, 2026.
Open a mature transportation management system and search for a customer you know exists. Often you will find three versions of the same company: one created by a dispatcher in a hurry, one imported from a load board, and one with the correct billing address that nobody uses. Duplicate customer records quietly break reporting, split payment history, and let a credit hold apply to the wrong account.
Treat cleanup as a project, not a chore
Duplicate records do not fix themselves, and a one-time purge will not hold unless the intake process also changes. Run cleanup as a short project with a defined start and end. Pick a scope, such as the top hundred customers by revenue plus every customer with more than one record in the billing system.
Before touching anything, take a backup or confirm the system's restore point. Merging records is a data operation, and the carrier should be able to undo a mistake. Work in a copy of the database if the system allows it.
Define what counts as a duplicate
Not every similar name is the same company. "ABC Logistics" and "ABC Logistics LLC" may be one customer or two related entities. "Smith Transport" may exist in three states. The cleanup team needs rules before it starts merging.
A practical definition uses several matching signals together: legal name and any known doing-business-as name, physical address, phone number, billing email, tax identification number, and the broker or shipper reference number used on rate confirmations. When two records share a tax identification number, they are almost certainly one customer. When two records share only a name, they may be related but should not be merged without confirmation.
Build a surviving record and a merge map
For each duplicate cluster, choose one record to survive. That is the golden record. It should carry the most complete and current data: legal name, remit-to address, billing contact, credit status, tax identification, and any contract reference.
Then map every duplicate to the survivor. For each duplicate, list the loads, invoices, contacts, and notes that must move. Do not delete the duplicate ID outright if the system needs it for historical references. Many systems let you mark a duplicate as merged and redirect it, which preserves the audit trail.
Move history before you remove anything
The value of cleanup is a complete picture. Move open invoices and open loads first, then the payment history, then contacts and documents. Check that balances still reconcile after the merge. If a customer had a credit limit on one record and a hold on another, decide which state the survivor should carry and record the decision.
After the merge, spot-check a handful of invoices to confirm they now appear under the survivor. A merge that loses a single open invoice costs more trust than the cleanup gained.
Confirm with the customer before changing billing
When the merge changes a remit-to address, billing contact, or legal entity, confirm the change with the customer through the carrier's approved channel before the next invoice. Record the confirmation. A customer that receives an invoice with unfamiliar details may delay payment while it investigates.
For brokers and shippers that use portals, confirm the reference number the customer expects on invoices. The portal may key on a number stored on the duplicate record.
Prevent the next round of duplicates
Cleanup without prevention is temporary. Add validation at intake. Require a search before a new customer is created, and require a tax identification number or another unique key for any customer that will be billed. Limit who can create customer records, and route exceptions to the office.
For load board and portal imports, create a matching rule that flags a likely duplicate for review instead of auto-creating a new record. The goal is not to block work. It is to make the system ask one question before it splits a customer in two.
Keep the surviving data honest
While the records are open, correct stale details. Update phone numbers, contact names, and addresses. Mark inactive contacts. Remove internal shorthand from customer-facing fields. The cleanup is a rare chance to fix data that everyone has been working around.
Do not overwrite a customer's own legal name with a nickname for convenience. Keep the legal name and add the nickname as an alias so reports and search still work.
Questions teams usually ask
Should every duplicate be merged?
No. Some are genuinely separate entities, such as a broker's separate divisions or an owner's two companies. Merge only when the identifiers support it, and document the reason.
What if the system has no merge function?
Change the duplicate record's name to point to the survivor and stop using it, then move the open items manually. Keep a written merge map so the history can still be explained.
Who owns the decision to merge?
The office can propose and prepare the merge. The decision belongs to the person accountable for billing and customer data, often the carrier's back office or finance owner.
How do we know the cleanup worked?
Reporting should show fewer duplicate customers, more complete payment histories, and a decline in new duplicates after the intake rule is added. Track those three signs rather than counting records deleted.
A clean customer list makes every downstream routine easier, from rating to collections. The work is quiet, but the payoff shows up in accurate invoices and reports a manager can trust.
Need help with a TMS cleanup project? Talk with our team about how a trucking virtual assistant can lead the record review while your staff keeps freight moving.