What Happens to Your Existing A/R When You Switch Billing Companies

Most billing transitions are planned around the wrong thing. The attention goes to new claims — system access, EDI enrollment, clearinghouse setup, the first submission date — while the money already sitting in your aging buckets is described as something that will be "sorted out." Legacy accounts receivable is where transitions actually fail, and it fails quietly, because nobody is looking at balances that belong to a period everyone has mentally closed.

The mechanics are unsentimental. Your outgoing biller's economic interest in your old claims ends the moment the relationship does. Your incoming biller has no institutional memory of those claims, no notes on the calls already made, and often no contractual obligation to touch them. If nobody decides who works legacy A/R before the switch, the default outcome is that nobody works it.

Decide these five things before anything moves

• Who works legacy balances, and for how long. Options are the outgoing biller on a wind-down agreement, the incoming biller under a defined scope, your own staff, or a split by aging bucket. Any of these can work. Silence cannot.
• How that work is paid for. Percentage-of-collections arrangements are built around claims a biller submitted themselves. Working someone else's unfinished claims is different work with a different success profile, and it should be priced explicitly rather than assumed into an existing rate.
• What "worked" means. A defined disposition for every balance — collected, appealed, billed to the patient, or written off with a reason — beats an activity promise.
• Who holds and hands over the data. Claim-level notes, appeal history, correspondence, payer call logs, and the aging report as of the cutover date. Get the format and the delivery date in writing, and take a snapshot yourself on the last day.
• Where payments land during the overlap. Remittances arriving after cutover need a posting owner and a reconciliation routine, or cash gets received and never applied.

• Snapshot taken
• Triaged
• Filing-limit sweep
• Worked
• Reconciled
• Closed

The riskiest month of any billing change is the first one — and the money at risk is old money nobody is watching.

Triage legacy A/R before you work it

Not every open balance deserves the same effort, and treating the pile as undifferentiated guarantees that the wrong claims get attention first. A defensible triage runs in this order.

1. Filing and appeal deadlines

Anything approaching a payer filing limit or appeal window goes first, regardless of dollar value, because it is the only category where delay converts a collectible balance into a permanent loss. This sweep should happen in the first days of the transition, not after the new claim flow is comfortable.

2. Large balances with a clear defect

High-value claims with an identifiable, correctable problem — a missing authorization number on file, a coordination-of-benefits issue, a documented service that was denied for necessity — offer the best return on effort.

3. Clustered small balances with a shared cause

Twenty small claims denied for the same reason are one project, not twenty. Clustering is what makes low-value recovery economic at all.

4. Genuinely uneconomic balances

Some balances cost more to pursue than they will ever return. Those should be written off deliberately, with a reason recorded and the practice's approval — not abandoned informally at the bottom of a queue. An explicit write-off policy is part of the transition plan, not an afterthought.

Contract terms that decide how bad the transition is

Most of the pain in a billing change is written into the agreement you signed at the start, which is why exit terms belong in the evaluation conversation rather than the departure one.

• Notice period and effective date. Know how much notice is required and what happens to claims in flight on the last day.
• Post-termination collections. If your biller continues earning on payments that arrive after termination, the scope and duration of that obligation should be stated — including whether they keep working denials during it.
• Data return. Format, completeness and timeline for claim-level records and notes, plus what happens to data held in a system you do not own.
• System ownership. If claims were run on the biller's practice management software rather than yours, establish now what you can extract and what you cannot.
• Credentialing artefacts. Payer portal credentials, CAQH access and enrollment records should not leave with the vendor; see credentialing: what to expect.

What a competent first ninety days looks like

Week one is inventory and the filing-limit sweep. Weeks two and three run new claim setup in parallel with the first pass on high-value legacy defects. By the end of the first month you should have a written recovery plan naming what will be worked, what will be written off and why. From there, legacy and current A/R get reported separately — blending them lets a healthy new claim flow disguise a static old tail, which is exactly the distortion described in days in A/R.

Expect a cash dip. Even a well-run transition has a lag between the last submissions of the old arrangement and the first payments of the new one, driven mostly by payer enrollment and portal access rather than by anyone's effort. Plan for it in your cash forecast instead of being surprised by it, and be sceptical of any vendor who promises there will be none.

How we handle it

We inventory open A/R by payer and aging bucket, triage by filing-limit exposure first, and give you a written recovery plan before we work anything — the same approach described on our denial management and A/R recovery page, run alongside new-claim medical billing. Legacy and current balances stay separated in reporting for as long as legacy balances exist.

If you are still deciding whether to move at all, read in-house or outsourced billing first, then questions to ask a billing company — the legacy-A/R questions in that list are the ones most often skipped.