Onboarding with a new billing company should be a defined project with named owners — and the three things that determine whether it goes well are who works claims already submitted, who owns your aged accounts receivable during the transition, and whether payer enrollment is held by your practice rather than by the outgoing vendor. Most disappointment with a billing partner traces to the first ninety days rather than to ongoing capability. This guide covers what a proper onboarding contains, the four failures that cost practices the most, a realistic week-by-week shape, and how to tell during the sales conversation whether the implementation will be real.
Why the first ninety days decide everything
A billing relationship that goes wrong usually went wrong at the start, and the reason is that transitions have gaps nobody was assigned to.
The outgoing arrangement stops. The new one begins. Between those two points sit claims already submitted, balances already outstanding, enrollment records already established, and staff who know one system and not the other. Every one of those is somebody's responsibility — and if the contract does not say whose, the answer defaults to nobody.
Transition failures are ownership failures, not competence failures. What the practice experiences during those weeks is chaos with a contractual cause: work that belongs to nobody because nothing said whose it was. The incoming team is working forward from its start date, the outgoing team has stopped, and the material in between quietly ages out.
Which is why onboarding when switching billing companies is really a question about who owns what, agreed in writing, before anything moves.
The four failures that cost the most
| Failure | What happens | Preventable by |
|---|---|---|
| Aged receivable inherited by nobody | Old balances age past collectability | One clause at signing |
| Claims in flight abandoned | Submitted claims fall between two teams | A defined cut-over date and owner |
| Enrollment tied to the outgoing vendor | Submission gap after handover | Verifying enrollment ownership |
| No baseline agreed | Ninety days later, nobody can tell if it worked | Recording the numbers first |
Aged receivable is the single most expensive omission and by far the most common. The new partner works claims from the date they start. Everything older sits untouched, ages past the point where payers will consider it, and is eventually written off. The balance you had on handover day becomes a loss nobody decided to take.
Claims in flight is the same problem on a shorter horizon. A claim submitted the week before the switch belongs to the outgoing vendor by timing and to nobody by practice. Denials on those claims frequently go unworked because each side assumes the other has them.
Enrollment is the one that stops submission entirely. If payer enrollment was administered by the outgoing vendor rather than held by the practice, the new partner may find it cannot submit at all until the position is corrected — and correction takes weeks. This is why credentialing held as a practice asset rather than a vendor service matters in a way that only becomes visible at moments like this.
No baseline is the quiet one, and the easiest to fix. Without recorded numbers from before the change, the review at ninety days becomes an argument between somebody's impression and somebody else's report.
What a proper onboarding contains
Eight components. A vendor that can describe all eight is describing a process; one that describes three is describing a login.
- A named implementation owner on their side. One person accountable for the whole transition, not a shared queue and not a rotating contact.
- A written transition plan with dates. What happens when, and who does it. This should exist before signing, not after.
- Explicit handling of aged receivable. Who works it, to what age, with what reporting. In writing.
- A defined cut-over for claims in flight. A date after which new claims go to the new partner, and a stated owner for everything before it.
- Enrollment verification before go-live. Confirmation that the practice holds its payer enrollment and that submission will not be interrupted.
- Baseline metrics recorded. Denial abandonment, aged receivable, days in receivable, net collection rate — taken before anything changes.
- Role-based training with materials that persist. Not one session for everyone — different training for the front desk, the biller and the clinicians, with recordings or written walkthroughs they can return to.
- A defined review point with a date. A specific day, agreed at the very start, when both sides sit down and look at the numbers against the recorded baseline.
Training delivered once, live, to a room, is largely gone within a fortnight and useless to anyone hired afterward. Materials that persist — recorded walkthroughs, annotated screenshots, short written procedures — are what make the knowledge survive.
Who owns what, in writing
| Item | Outgoing vendor | New partner | Your practice |
|---|---|---|---|
| Claims submitted before cut-over | Works to resolution | — | Confirms the date |
| Claims after cut-over | — | Works to resolution | — |
| Aged receivable at handover | Named in contract | Named in contract | Verifies monthly |
| Payer enrollment | Releases if held | Verifies before go-live | Holds it |
| Baseline metrics | Provides final report | Records starting point | Keeps the record |
| Configuration decisions | — | Asks | Decides promptly |
The aged receivable row is deliberately shown as needing a name in the contract rather than a default. Whichever party takes it, the requirement is that the agreement says which — because the failure mode is not a bad decision, it is no decision at all. The bottom row is the one practices overlook: configuration questions waiting a fortnight for an answer extend the timeline by a fortnight, and the delay gets attributed to the vendor.
A realistic week-by-week shape
The sequence is more consistent than the duration.
Before go-live. Contract terms settled including the four ownership questions. Baseline metrics recorded. Enrollment verified. Transition plan agreed with dates. Practice data assembled and validated.
Week one. Configuration and setup. Fee schedules, payer list, provider records, claim rules. Initial training for the front desk and whoever handles charges.
Weeks two to four. First claims submitted through the new arrangement. Configuration errors surface, and surfacing them is the point. Expect a higher denial rate in this window than in steady state — it should be falling by week four rather than persisting.
Month two. Steady submission. Denial patterns from the first weeks identified and corrected upstream. Aged receivable work visibly under way, with reporting on it. Second-round training for anything the first round did not cover.
Month three. Review against baseline. Denial abandonment, days in receivable, net collection rate compared with the numbers recorded before the change.
Months four to six. Normal operation, with the relationship's actual working rhythm established. Anything still unresolved at this point is a pattern rather than a transition symptom.
What your practice has to do
Onboarding is not something a vendor does to you. Four responsibilities sit on the practice side.
Assign an internal owner. One person accountable for the transition from your side, with the time to be accountable. A project split across everyone belongs to no one.
Provide clean data and provide it once. Fee schedules, payer list, provider records, existing enrollment documentation. Assembled properly at the start, this takes a few hours. Assembled piecemeal in response to requests, it takes weeks and delays go-live.
Make people available for training. The single most common practice-side failure. Training scheduled and then cancelled because the clinic was busy is the reason a practice is still struggling in month three.
Decide things when asked. Configuration questions have to be answered — which providers, which fee schedules, which workflows. A vendor waiting a fortnight for a decision is a vendor whose timeline has slipped for reasons that are not theirs.
What looks alarming but is not
Three things happen in every transition and worry practices unnecessarily.
Denials rise in the first few weeks. New configuration meets real payer rules and the mismatches surface. Watch the trend rather than the level: falling by week four is healthy, flat at week six is not.
Cash flow dips briefly. The gap between the outgoing arrangement's last submissions and the new one's first payments produces a short trough. Plan for it rather than being surprised. Our guide to improving cash flow in a medical practice covers how to manage the timing.
Staff feel noticeably slower. People who knew one system well are learning another from scratch. This is temporary and the main reason transitions feel worse in week two than they are.
What should worry you
Nobody can tell you who is working your aged receivable. If the answer is vague at week three, it is not being worked.
Denials are flat rather than falling by week four or five. Configuration errors that persist are not being corrected upstream.
You cannot see claim-level detail yourself. Depending on the vendor's summary for the only view of performance is a structural problem, not a transition symptom.
Training was one session and nothing else. Especially if new staff have no way to learn the system.
Your implementation contact has changed twice. Turnover during a transition is a genuine risk signal. Raise all of these early and directly — transition problems addressed in month one are fixable; the same problems left until month four have quietly become the working arrangement.
Questions to ask before signing
- Who owns my aged accounts receivable during and after the transition, and to what age is it worked?
- What is the cut-over date for claims in flight, and who works everything submitted before it?
- Is my payer enrollment held by my practice or administered by my current vendor, and how do we verify that?
- Who is my named implementation owner, and how long do they stay involved?
- What does the written transition plan look like — can I see one from a recent client?
- What training do you provide, in what format, and what persists afterward for people I hire later?
- What baseline metrics will we record, and when do we review against them?
The first question is the most revealing. A vendor with a clear, specific answer has run transitions properly before. One that treats it as an unusual question has not — and the cost of that inexperience lands on your oldest, most collectable balances. ClinicMind has been a G2 Leader for 16 consecutive quarters, is ONC-certified, and has served practices since 1999, with Quality of Support as its documented review strength.
What to measure
| Metric | When | What it tells you |
|---|---|---|
| Denial rate, weekly | From week one | Whether configuration errors are being corrected |
| Denied claims abandoned | Baseline, then month three | The core performance measure |
| Accounts receivable past 120 days | Baseline, then monthly | Whether aged balances are being worked |
| Days in accounts receivable | Baseline, then monthly | Cycle efficiency |
| Aged receivable at handover | Baseline | The number most likely to be lost |
| Net collection rate | Baseline, then month three | The outcome measure |
The aged receivable at handover row is the one to record separately and watch specifically — it is the balance most likely to disappear during a transition, and the only protection is knowing what it was and asking about it monthly.
What this has in common with an EHR migration
Practices frequently change billing partner and clinical system at the same time. The same four ownership questions apply — aged receivable, claims in flight, enrollment, baseline. Two additional ones arrive with the clinical system: whether historical clinical data transfers usably, and whether documentation templates are configured before go-live.
Doing both at once is more disruptive and, done properly, shorter overall than doing them sequentially. The deciding factor is capacity: a practice with the attention to run one project well should not run two. Our guide to migrating from ChiroTouch to another EHR covers the clinical side. Where the two are combined, the argument for a single platform is stronger than usual — one implementation owner, one plan, one set of terms, and no boundary between the clinical record and the claim for information to fall through.
Frequently asked questions
What should onboarding look like when switching billing companies?
A defined project with named owners rather than a credential and a start date. Eight components: a named implementation owner, a written plan with dates agreed before signing, explicit handling of aged receivable, a defined cut-over for claims in flight, enrollment verified before go-live, baseline metrics recorded, role-based training with materials that persist, and a review point agreed at the start. A vendor who can describe all eight is describing a process.
What is the most expensive transition failure when switching billing companies?
Aged accounts receivable inherited by nobody. The new partner works claims from their start date, everything older sits untouched, ages past the point payers will consider it, and is eventually written off. It is preventable with one clause at signing specifying who works it, to what age, with what reporting.
How long does a billing transition take?
Configuration and initial training in week one, first claims in weeks two to four, steady submission and upstream corrections in month two, and a formal review against baseline at month three. Normal operation from months four to six. Anything still unresolved after that is a pattern rather than a transition symptom.
Is it normal for denials to rise at the start of a billing transition?
Yes, in the first few weeks — new configuration meets real payer rules and the mismatches surface. Watch the trend rather than the level: falling by week four is healthy, flat at week six is not. Cash flow also dips briefly in the gap between the old arrangement's last submissions and the new one's first payments — plan for it rather than being surprised.
What should worry me during billing onboarding?
Nobody can say clearly who is working your aged receivable by week three; denials are flat rather than falling by week four or five; you cannot see claim-level detail yourself; training was one live session with nothing that persists; and your implementation contact has changed twice. Raise all of these early and directly.
What should I ask before signing with a billing company?
Who owns aged receivable during and after the transition and to what age it is worked. The cut-over date for claims in flight and who works everything before it. Whether payer enrollment is held by your practice or the outgoing vendor. Your named implementation owner and how long they stay involved. Whether you can see a written transition plan from a recent client. What training persists for future hires. And what baseline metrics you will record.
Should I change billing company and EHR at the same time?
It is more disruptive and, done properly, shorter overall than sequentially. The same four ownership questions apply, plus whether historical clinical data transfers usably and whether documentation templates are configured before go-live. The deciding factor is capacity — a practice with the attention to run one project well should not attempt two. Where combined, a single platform removes one implementation and one set of terms.
The bottom line
Most disappointment with a billing partner traces to the first ninety days, and transition failures are ownership failures rather than competence failures. The outgoing arrangement stops, the new one starts, and everything in between — claims already submitted, balances already outstanding, enrollment already established — belongs to nobody unless the contract says otherwise.
Settle four things in writing before anything moves: who works your aged receivable and to what age, the cut-over date for claims in flight and who owns what precedes it, whether payer enrollment is held by your practice rather than the outgoing vendor, and what baseline numbers you are recording. Then expect denials to rise briefly and cash to dip in the first weeks — both normal — and watch whether they improve on the expected curve rather than reacting to the level. To see how a billing service runs onboarding as a defined project inside the same platform as the clinical record, explore ClinicMind's full billing service.