Read the old contract first, then give notice. Practices that do it the other way round tend to learn about the notice period, the data clause and the A/R tail after the new vendor has already been told a start date. This page covers the switch itself. For choosing the next vendor, see how to choose a medical billing company, and for the switch section of that guide, see the 60-day transition plan.
Structured asset: three checklist tables, each with an owner column so every task has a named party. The figures on this page are limited to the dates and windows in the federal rules cited under Sources. Notice periods, fees and handover deadlines come from your own contract, so none are quoted here as typical.
Check the exit terms before you give notice
Pull the signed agreement and the business associate agreement (BAA), and read the termination, fees and data clauses together. The BAA is separate paper in many practices and often says different things from the services agreement.
| Check | What to look for | Owner |
|---|---|---|
| Notice period and form | The number of days, whether it must be written, who it goes to, and whether it can be given before the term ends. Put the end date on the calendar the day you read it. | Practice |
| Termination without cause | Whether you may leave before the term ends, and any early-termination fee or minimum-fee balance that applies. | Practice, counsel |
| Auto-renewal | The date the renewal window closes. A missed window can start a new term. | Practice |
| Fees after termination | Whether the vendor keeps earning its percentage on claims it submitted, on payments received after the end date, or on a flat wind-down fee. The how-to-choose guide recommends contract language that ends the vendor's fee rights when the relationship ends and gives you ownership of outstanding A/R. | Practice, counsel |
| Data export clause | Format, deadline and price for a full export. See the next section for what to list in it. | Practice, outgoing vendor |
| BAA return or destruction | The BAA should say what happens to protected health information (PHI) at termination. Federal rules require the BAA to provide for return or destruction of PHI where feasible, and to keep protections in place where it is not (45 CFR 164.504(e)(2)(ii)(J)). The rule sets no deadline or file format, so the contract has to. | Practice, outgoing vendor |
| Payer enrollments in the vendor's name | List every clearinghouse account, payer portal login and EFT enrollment the vendor set up. For each, note whether it sits under the practice's tax ID and legal name or under the vendor's. | Practice, outgoing vendor |
Before you sign with the next vendor, run the same table on its contract. A vendor that asks for a long notice period and a fee on collections after exit has written the next switch into the first one.
Data and claims handover: what to request
Ask for the export in writing, with a date, and ask for it before the last day of service, not after. Your patient and billing records belong to the practice; the vendor holds them as a business associate under the BAA. The request below is a working list. Check it against what your contract promises, and name the file format for each item.
| Request | Why it matters | Owner |
|---|---|---|
| Open A/R report by payer, by claim, with date of service, billed amount and last action | The base for dividing claims between vendors. Ask for the report as a spreadsheet or CSV so the new vendor can load it. | Outgoing vendor |
| Claim history for the period you want to audit, including claim status and denial reasons | Shows which denials are worked, which are waiting on a payer and which have timed out. | Outgoing vendor |
| Remittance data: 835 electronic remittance files and posted payment detail | Lets the new vendor match payments to claims and see what was already posted. | Outgoing vendor |
| Patient balances and statement history | Keeps patient collections from restarting at zero or billing the same balance twice. | Outgoing vendor |
| Charge and fee schedule data, adjustment and write-off codes | So the new vendor posts the same way and reports can be compared. | Outgoing vendor |
| Appeal letters, payer correspondence and call notes on open claims | Stops the new vendor from repeating contacts, and shows what a payer has already said. | Outgoing vendor |
| Clearinghouse, EFT and payer portal access list | Everything that must move to the practice or the new vendor. | Practice, outgoing vendor |
| Written confirmation of PHI return or destruction after cutover | Closes the BAA obligation and gives you a record. | Outgoing vendor |
| A test load of the export into the new vendor's system | Finds missing fields while the old vendor is still under contract and can fix them. | Incoming vendor |
Keep your own copy of the open A/R report and the remittance files in a location the practice controls. If the outgoing vendor misses the date, you hold the baseline that shows what was open on the day you left.
Open A/R: who works claims already in flight
The common failure is not that nobody wants the old claims. It is that neither vendor has been told in writing that they are responsible for them. Decide the rule before cutover and write it into both contracts.
- Pick a cutover date by date of service. Claims for dates of service before the cutover date stay in the old vendor's bucket. Dates of service on or after it go to the new vendor. A date-of-service line is easier to audit than a submission-date line because the EHR already holds the date of service.
- Name who works the old bucket, for how long and at what price. If the outgoing vendor is to keep working its claims after the end date, the contract should say for how many days and what it may charge. If the incoming vendor is to take them over, ask what it charges for aged claims; see outsource vs in-house billing for the fee types that apply to claims created before a vendor's start.
- Mind the filing deadline. Medicare generally requires a claim to be filed within one calendar year of the date of service (42 CFR 424.44). Other payers set their own filing and appeal windows. Sort the open A/R report by the oldest dates of service first and ask each payer for its limit; claims near the limit are worked first, whoever owns them.
- Keep payments traceable. Payments that arrive after cutover on old claims need a rule: which account receives them, who posts them and who is told. Medicare pays a billing agent only when the agent's compensation is unrelated to the amounts billed or collected (42 CFR 424.80(b)(5)), so Medicare payments should already be going to an account in the practice's name; confirm that before you file any change. The CMS-588 form governs that account.
- Hold a weekly A/R review across both buckets. One report, both vendors on the call, each aged claim with a named owner. The billing audit checklist lists the checks for a review like this.
A sample timeline
The timeline below is a planning template built on the 60-day transition plan in the how-to-choose guide. It is not a benchmark. Your notice period, the new vendor's setup schedule and each payer's enrollment processing time set the real dates. Day 0 is the first day the new vendor submits claims. Count backward from the end date in your contract.
| When | Task | Owner |
|---|---|---|
| Before notice | Read both contracts, complete the exit-terms table, get counsel's view on fees and data clauses, and sign the new vendor only once its exit terms pass the same table. | Practice |
| Notice date | Give written notice in the form the contract requires. Send the data request the same day with a requested delivery date. | Practice |
| Weeks 1 to 2 | Receive and check the export. Confirm the file format with the incoming vendor. Start the test load. | Outgoing vendor, incoming vendor |
| Weeks 3 to 4 | Incoming vendor connects to the EHR or practice management system, loads fee schedules and starts clearinghouse and payer enrollments. Payers set their own processing times, so ask each one for its current time and plan around the slowest. | Incoming vendor, payers |
| Weeks 5 to 6 | Parallel run begins (next section). New claims go to the new vendor from the cutover date of service; old claims stay with the outgoing vendor. | Both vendors |
| Weeks 7 to 8 | Move the remaining open A/R to the owner named in the contract. Review the aging report together. Collect the outgoing vendor's final accounting. | Both vendors, practice |
| Within 90 days of the change | Report the change to Medicare if it affects your enrollment record. Physician practices have 90 days to report most enrollment changes (42 CFR 424.516(d)(2)); ask your Medicare Administrative Contractor whether a billing agent change is among them. | Practice |
| After cutover | Get written confirmation of PHI return or destruction. Keep the open A/R and remittance copies you took on day one. | Outgoing vendor, practice |
| Weeks 9 and on | Weekly review against the pre-switch baseline. The first 90 days guide sets the numbers to track and what each one means. | Practice, incoming vendor |
How to run both vendors in parallel
A parallel run means the outgoing vendor keeps working the old claims while the new vendor starts billing new ones, and someone checks every week that no claim falls between them. It is different from running both vendors on the same claims, which creates duplicate submissions. Keep the buckets separate and reconcile them.
- Split by the cutover date. One date of service, set in writing. Every charge belongs to exactly one bucket.
- Reconcile charges each week. Pull the charges entered in the EHR for the week. Each one should appear in the new vendor's submitted-claims report, or be in the old bucket by date of service. A charge that appears in neither is a gap. Chase it that week.
- Check for duplicates. The same claim should not be live with both vendors. Ask both vendors for a list of claim numbers submitted since the cutover date and compare.
- Test the payment path. Confirm that the first remittances for new claims reach the account you intended, and that old-claim payments are posted by the vendor named in the plan.
- Agree the exit test in advance. Set the conditions for ending the overlap before it starts, for example: every aged claim has a named owner, the open A/R report totals match between the two vendors, and the first new-claim remittances have posted. When the conditions are met, end the overlap and send the termination confirmation.
- Watch the early numbers. Days in A/R, clean claim rate and denial rate for the post-switch book are covered in the first 90 days guide. Compare them with the baseline you captured before notice.
Parallel running means paying two vendors for a time. Ask both what the overlap will cost, in writing, before you start. If the cost is a concern, shorten the overlap by cleaning up the open A/R first rather than by skipping the reconciliation.
Compare Billing Companies Before You Give Notice
GetPracticeHelp matches independent practices with vetted billing and RCM companies by specialty and payer mix, so the exit terms of the next contract can be read before you commit to a switch date.
Get Matched Now →Sources
- 45 CFR 164.504(e)(2)(ii)(J), business associate contract terms on return or destruction of PHI at termination: eCFR, 45 CFR 164.504.
- 42 CFR 424.44, time limits for filing Medicare claims: eCFR, 42 CFR 424.44.
- 42 CFR 424.80(b)(5), payment to a billing agent: eCFR, 42 CFR 424.80. The EFT account rule is in the CMS-588 EFT Authorization Agreement.
- 42 CFR 424.516(d)(2), 90 days to report most enrollment changes: eCFR, 42 CFR 424.516.
- GetPracticeHelp's own guides: the 60-day transition plan and contract recommendations in How to Choose a Medical Billing Company, and the review metrics in the first 90 days guide.