Blog·October 26, 2026
What Happens to Bills and Trust When You Merge Contacts in Clio
Somebody on your team finds two records for the same client. Same name, same phone number, one has the email and the other has the address. Obvious duplicate. They combine them, delete the extra one and move on.
Then a few weeks later, the bookkeeper opens an old bill and finds that its client has been deleted.
Merging contacts sounds like an address book chore. In a law firm, it's an accounting event wearing an address book costume.
A contact merge isn't really a merge
Clio doesn't actually fuse two contacts together. You're moving the records associated with one contact to the other, then deleting the duplicate.
Matters are pretty straightforward. Change the client on the matter and it moves to the contact you're keeping.
Bills are where it gets interesting.
A bill remembers both the matter it belongs to and the client it was issued to. Changing the client on a matter doesn't go back and change the client on bills that already exist. The matter can now belong to the right person while its old bills still point to the duplicate.
You probably won't notice that from the matter. You'll notice it when somebody opens the bill later.
If the duplicate has an unpaid bill, Clio won't let you delete the contact. That's inconvenient, but it's also useful. There's still something that needs to be dealt with before that contact goes away.
Paid and void bills don't stop the deletion. They stay on their matters, along with their transactions and payments, but Clio shows [Client deleted] as the client on those bills.
The accounting history hasn't disappeared. It's just not something you're going to find later by pulling up that client.
Trust is different
Trust records are a good reason to stop before deleting anything.
If the duplicate has a trust balance or trust history, somebody needs to make sure those records are where they belong before the contact goes away. Trust accounting isn't a good place for "we'll sort it out later."
There are other things that can stop a deletion too. Firms using Clio's personal injury features may have a duplicate that's still listed as a medical provider, payer or lien holder, or as a party on a proposed recovery. Clio won't delete the contact while those records still point to it.
In that case, the fix is in Clio. Update the personal injury record to use the right contact, then finish cleaning up the duplicate. Clio refusing the deletion is doing exactly what you want it to do.
For an individual duplicate, the questions are fairly simple:
- Are there any unpaid bills?
- Are there paid or void bills that will show the client as deleted?
- Are there any trust records?
- Is the contact being used as a provider, payer, lien holder or recovery party?
If none of those apply, it's probably a straightforward cleanup. If one does, deal with it before deleting the duplicate.
What MERGEguard checks before a merge
MERGEguard checks these things before it deletes a duplicate contact.
An unpaid bill stops the merge before the duplicate is deleted. Since Clio can't change the client on an existing bill, the bill needs to be voided and generated again under the contact you're keeping, and then the merge can finish.
Paid and void bills don't stop the merge, but MERGEguard shows them during review so you know they're there before you continue. The bills stay on their matters, and Clio will show [Client deleted] as the client.
Trust records stop the merge too. MERGEguard tells you what needs to be moved in Clio before you try again.
And if Clio refuses to delete a contact because it's still being used in a personal injury record, MERGEguard tells you what Clio is objecting to so you know where to look.
MERGEguard isn't trying to make accounting decisions for you. It handles the straightforward parts and stops when there's something a person needs to look at.
Cleaning up your contacts should make things easier to find, not give your bookkeeper a scavenger hunt.