The three transition risks are data access, legacy A/R ownership and enrollment continuity, and all three have to be settled before you give notice. Once notice is given, your leverage to negotiate any of them is gone.
Most of the damage in a billing transition happens in the first two weeks, and most of it is decided before notice is given.
Before you give notice
- Read the termination clause. Notice period, penalties, and what happens to open A/R.
- Establish data rights. Claim-level history in a usable export, not summary reports, with access continuing past the end date.
- Decide who works the tail, for how long, at what rate — in writing with both parties.
- Confirm enrollment ownership. Payer enrollments and ERA/EFT routing should be in your name, not the vendor's.
During
- Agree a cutoff rule — by date of service or submission date — so nothing falls between definitions.
- Start ERA and EFT re-enrollment early. It is the longest lead time and the usual cause of the payment gap.
- Keep read access to the old system for the retention period.
- Track legacy A/R separately so it cannot be quietly abandoned.
After
Expect a dip. Enrollment takes time and the new team is learning your payers. Watch charge lag and first-pass rate weekly for the first two months — those two move first when something is misconfigured.
The part practices skip
Telling the outgoing vendor the timeline honestly. An adversarial exit produces an unworked tail, and the tail is your money. A clean handover is worth more than the satisfaction of a short notice period.
Read the termination clause before anything else
Notice periods, data return obligations and who works the run-out A/R are all in the contract you already signed. Read them before you start conversations, because they set what is actually negotiable.
Where the contract is silent on run-out A/R, assume the outgoing vendor will do little. Negotiate a tail arrangement — a reduced percentage for a defined period — while you are still a customer rather than after you have given notice.
Run the two in parallel
A clean cutover date sounds tidy and produces a gap. Overlap the vendors: the incoming one starts on new claims from a date, the outgoing one continues working claims already submitted, and both are measured on their own cohort.
That keeps accountability clear and stops both parties blaming the transition for whatever the numbers do next.
Keep measuring through the change
Collections dip after any system or vendor change, which means the dip itself tells you nothing. What tells you something is whether clean claim rate and days in A/R return to baseline within a quarter.
Record the baseline before the transition starts. Without it, every disappointing month is explained by the transition indefinitely, and nobody can say when the new arrangement should have settled.
Common questions
- What should I settle before leaving a billing company?
- Who owns and works the legacy A/R, in what format your data is returned, and whether payer enrollments and ERA routing move without interruption.
- Who works my old A/R after switching billers?
- Whoever your contract says. If it is silent, the outgoing vendor has little incentive and the incoming one has no context — which is how a quarter of collections disappears.
- How long does switching billing companies take?
- Plan a full quarter of overlap. Enrollment and ERA routing changes take weeks, and running both in parallel is cheaper than a gap.
- Will I lose payments during the transition?
- Only if ERA and EFT routing lapses. Those enrollments are payer-by-payer and do not move automatically, so they need tracking as a checklist.
- What data should I get back?
- The full claim and payment history in a usable export, not a PDF summary — plus open A/R with denial reasons and current status on each claim.
Denials Piling Up?
We handle the revenue cycle end to end — coding by certified coders, claim submission, denial management and appeals, and A/R follow-up, with six reported numbers every month.