The denial codes that cost practices the most
What CO-16, CO-18, CO-45, CO-97, CO-109, CO-197 and PR-204 actually mean, why each one fires, and what has to change upstream so it stops repeating.
Read more
Insight
The risk in changing billing vendors is not the new vendor — it is the gap. Claims already in flight, denials part-worked, and aged A/R can fall between the outgoing and incoming teams while both reasonably assume the other is handling them. The single most important thing to settle in writing, before any transition date is chosen, is who works the legacy A/R and for how long. The second is EDI and ERA re-enrolment, which is administrative, is controlled by payers rather than by either vendor, and takes longer than most transition plans allow for.
At any cutover there is a population of claims already submitted, already denied, or mid-appeal. If the outgoing vendor stops working them on the termination date and the incoming vendor starts only with new charges, that population simply ages — through appeal deadlines and eventually through filing limits — while everyone assumes it is covered. Settle explicitly whether the outgoing vendor works it to conclusion, whether the incoming vendor takes it on, and on what commercial terms, since aged A/R is more labour per dollar than current claims and pricing built for current volume rarely fits it.
Electronic claim submission and electronic remittance are enrolled per payer, and changing the receiving party requires payer-side processing that neither vendor controls. Until it completes, remittances may continue routing to the outgoing vendor or arrive on paper, and payment posting stalls even though claims are going out normally. This is administrative work with an unavoidable lead time, and it is the most common cause of a transition that looked clean on paper producing a posting backlog in its first weeks. It can and should be started before a go-live date is fixed.
Before access is withdrawn, export the full aging report by payer and by bucket, the list of open denials with their codes and dates, payer contracts and fee schedules, credentialing records with effective dates and re-credentialing deadlines, and patient statement history. If billing was performed inside your own practice management system this is largely unnecessary, because the data never left. If it was performed in the vendor's platform, this export is your only opportunity, and the window is the notice period. Confirm in advance what format the export arrives in — a report that cannot be loaded into anything is not a usable record.
A hard cutover on a single date maximises the chance of something falling through. A short overlap — where the incoming team begins on new charges while the outgoing team completes work in flight — costs a period of double running and removes the gap entirely. During that period the useful things to watch are whether claims are actually going out daily, whether remittances are posting, and whether the aging buckets are moving in the right direction. Those three tell you more about a transition than any status report.
Keep reading
What CO-16, CO-18, CO-45, CO-97, CO-109, CO-197 and PR-204 actually mean, why each one fires, and what has to change upstream so it stops repeating.
Read more
How clean claim rate and first-pass resolution are calculated, why the two differ, and the upstream steps that actually move them.
Read more
The days in accounts receivable formula, why the aging buckets matter more than the headline number, and the specific causes behind a rising A/R.
Read more
FAQ
Whoever the contract says, which is why it must be agreed in writing before the transition date. There is no default arrangement, and the assumption that the incoming vendor inherits it is frequently wrong. Aged A/R is more labour-intensive per dollar than current claims and is usually priced separately.
Long enough for claims in flight to adjudicate and for EDI and ERA re-enrolment to complete across your main payers. Since re-enrolment is payer-controlled and does not complete uniformly, the overlap is usually set by the slowest payer rather than by a target date.
It can, and the disruption is nearly always in payment posting rather than claim submission — remittance routing lags behind the change while claims go out normally. Starting EDI and ERA re-enrolment early and running an overlap are the two things that most reduce it.
Next step
Send us your specialty, claim volume and current billing setup. We will come back with a proposal you can act on.