A medical billing outsourcing transition takes about 90 days: 30 days of contracting, access and enrollment paperwork; 30 days of go-live, with new charges going to the vendor while legacy A/R is worked down in parallel; and 30 days of stabilisation against agreed metrics. The step easiest to miss is the Medicare EDI notice, and it stalls the first claims.

Practices that decide to outsource medical billing usually want it done by the first of next month. It can be, on paper. In practice the first month is paperwork, the second is the real cutover, and the third is where you find out whether it worked. Here is the timeline we run, with the rules that set the dates.

Before day 1: two decisions that shape everything

The cutover date for dates of service. Pick a date. Encounters on or after it belong to the new vendor; encounters before it are legacy A/R. Everything in the plan hangs off that line, including who is paid for what.

Who works the legacy A/R. Three options: your outgoing biller or department works it down, the new vendor takes it on for a separately stated fee, or it is split by payer. Decide in the contract, not in week six. The deadline behind this decision is fixed: Medicare claims must be filed within one calendar year of the date of service (42 CFR 424.44), and commercial payers set their own deadlines by contract. Legacy A/R that nobody owns becomes a write-off.

Days 1 to 30: contracts, access and enrollment

Sign the BAA before any PHI moves. HIPAA requires a business associate contract before a covered entity discloses protected health information to a vendor, and 45 CFR 164.504(e) sets what it must contain. No chart access, no export, no shared login until it is signed. A vendor that asks for access first is telling you something.

System access. Read-and-post access to the practice management system and EHR, the clearinghouse account, and every payer portal, with named user accounts rather than shared credentials. Inventory each one; it is also the checklist for revoking access from whoever is leaving.

Medicare EDI notice. CMS requires every provider to complete an EDI enrollment before exchanging transactions through a billing service or clearinghouse, and to give the Medicare Administrative Contractor written notice of which transactions that billing service is authorized to submit or receive, updated whenever the authorization changes (CMS, EDI System Access and Privacy, last modified 10 September 2024). This is the step that gets forgotten. Without it the vendor’s first Medicare batch can be rejected, and the clock on that month’s cash starts late.

Enrollment records. Physicians and their organizations must report changes to Medicare enrollment information within 90 days, and changes of ownership, practice location or adverse legal action within 30 days (42 CFR 424.516(d)). If the billing-agency details on file are changing, file the update inside the window. Confirm CAQH attestation dates and any pending payer applications at the same time, because a provider whose enrollment is not active will not get paid regardless of who bills.

Fee schedules and payer rules. Load contracted rates by payer so underpayments are visible from the first remittance. Collect the payer-specific quirks your current team carries in its head: which plans want paper attachments, which require a referral on file, which deny a modifier on sight.

Baseline metrics. Pull the HFMA MAP Keys you will judge the vendor on: Clean Claim Rate (CL-1), Total Charge Lag Days (PB-4), Remittance Denial Rate (AR-5), Aged A/R as a Percentage of Total Billed A/R (AR-1) and Net Days in A/R (FM-1), using HFMA’s published definitions. Without a baseline, month three is an argument about feelings.

Days 31 to 60: go-live and parallel running

First claims out. The vendor starts billing encounters from the cutover date. Watch the clearinghouse acceptance report daily for the first two weeks; rejections here are almost always setup errors (a wrong NPI, an unlinked provider, a missing taxonomy), and they are cheap to fix on day 32 and expensive on day 60.

Set cash-flow expectations correctly. Medicare cannot pay an electronic clean claim before the 14th day after receipt (the payment floor) and must pay or deny it within 30 days (the payment ceiling), per the Medicare Claims Processing Manual, Chapter 1, §§80.2.1.1 and 80.2.1.2. So if the first batch goes out on day 31, the first Medicare deposits from the new vendor land in the middle of the second month, and commercial payers vary. A dip in deposits during this window is arithmetic, not a warning sign, as long as legacy A/R is still being collected on the other side of the cutover.

Parallel running. Legacy claims keep flowing from whoever owns them; new claims flow from the vendor. Hold a weekly call with both, with one agenda: rejections, denials, and anything that crossed the cutover line incorrectly.

Denial workflow. Agree who answers a payer’s request for records, who talks to the provider about documentation, and how fast. The first denials from the new setup will arrive in this window and set the pattern.

Days 61 to 90: stabilise and measure

Compare against the baseline. By day 75 you have enough remittances to read CL-1 and AR-5 for the new vendor’s claims. Charge lag (PB-4) should already be visible. FM-1 and AR-1 will still be distorted by the legacy book, so compare them on post-cutover A/R only.

Patient statements. Confirm the statement cycle restarted on schedule and that the return address, phone number and payment options on the statement are right. Patients notice a change in billing before anyone else does.

Close out legacy A/R. Set a date by which remaining legacy balances are either resolved, transferred to the vendor at the agreed fee, or written off with a reason code. Do not let a legacy book run indefinitely.

Credentialing gaps. Any provider whose claims were held during the transition for enrollment reasons should be enrolled by now or on a tracked timeline. This is where having credentialing and billing under one roof pays off: the same team that holds the claim releases it when the payer confirms.

What the practice keeps doing

Outsourcing moves the back end. Scheduling, registration, charge capture and provider documentation stay with you, and they decide how clean the vendor’s claims can be. Eligibility verification is part of AMS’s scope when it is contracted for; your front desk still collects the insurance card and copay at check-in and re-verifies coverage at the January plan change. Our earlier post on what medical billing outsourcing includes draws that line in more detail.

Where transitions fail

In our experience it is rarely the vendor’s software. It is the EDI notice that was never filed, the legacy A/R nobody owned, the payer portal still logged in under a departed employee’s name, and the practice that expected month-two cash to match month-zero cash. Each is avoidable with the checklist above.

For a sense of what a stable state can look like, one AMS client, a three-location neurology and sleep practice, reported steady cash flow within three months and now runs a 98.9 percent first-pass clean-claim rate with next-day claims processing. That is one practice’s result over the ongoing engagement, not a promise; the write-up is in our case studies. Definitions for the terms used above are in the billing glossary in our resources library.

If your 2027 budget assumes a 1 January cutover, the paperwork month is December, which means signing in November. That is a good reason to look now at how our outsourced medical billing services run the first 90 days.

About the Author

AMS Solutions is a full-service medical billing and revenue cycle management company serving physicians and healthcare practices nationwide since 1992. Our team writes about medical billing, claim denial prevention, coding updates, and practice revenue, helping providers get paid accurately and efficiently so they can focus on patient care.

Free Consultation

Schedule Meeting