A new medical practice should not wait until opening week to test whether it can get paid. The final 90 days before the first patient are the time to connect payer enrollment, scheduling, eligibility, authorizations, documentation, coding, claims, payments, patient billing, accounting, and reporting into one working revenue cycle.
This 90-day revenue cycle checklist is organized around decision gates rather than a loose collection of tasks. By opening day, the practice should know which provider-location-payer combinations are effective, how every charge becomes a claim, who resolves each exception, how money is posted and reconciled, and what the team will monitor during the first weeks of operation.
Quick Summary: What Must Be Ready Before Opening?
- 90–61 days before opening: lock the billing model, payer strategy, systems, ownership, policies, and implementation plan.
- 60–31 days before opening: configure provider and payer records, front-end workflows, claim rules, payments, reporting, and staff training.
- 30–15 days before opening: test complete patient and claim scenarios, reconcile results, close enrollment gaps, and correct failures.
- 14–1 days before opening: run readiness reviews, confirm effective dates, freeze critical configuration, prepare daily dashboards, and establish escalation coverage.
- Opening through day 30: use a controlled ramp with daily monitoring of registration errors, eligibility, rejections, denials, payments, and cash.
Acuity coordinates practice-launch work across credentialing, billing, technology, workflows, and operational readiness. Learn more about our medical practice startup services.
Why Does the Revenue Cycle Need a 90-Day Launch Plan?
A revenue cycle is a chain of dependent processes. A perfectly coded claim can still fail if the patient’s insurance was entered incorrectly, the provider was not effective at the location, an authorization was missing, the payer ID was wrong, the claim lacked a required identifier, or the ERA and EFT were not connected to the correct account.
The 90-day period creates time to find these problems before they affect real patients and cash flow. It also forces the launch team to distinguish between four readiness states:
- Selected: a vendor, payer, system, or policy has been chosen.
- Contracted: the agreement is signed and implementation can proceed.
- Configured: the people, system, account, and workflow are set up.
- Validated: a realistic end-to-end test produced the expected result.
Opening decisions should be based on validated readiness, not on a vendor’s promised delivery date or a payer’s verbal status.
Who Should Own the Revenue Cycle Launch?
Name one accountable launch owner and one decision-maker. The owner does not need to personally complete every task, but must maintain the dependency plan, risk register, status definitions, due dates, and escalation path.
The core team often includes:
- physician owner or executive sponsor;
- practice administrator or launch manager;
- credentialing and payer-enrollment lead;
- billing or RCM lead;
- coding and compliance resource;
- front-desk and scheduling lead;
- EHR and practice-management implementation lead;
- banking, accounting, and payment-processing contact;
- IT and security support; and
- outside legal, tax, or contracting advisers as appropriate.
Use a responsibility matrix that assigns a primary owner and backup for each revenue-cycle activity. If two teams both believe the other owns an authorization, claim edit, denial, or patient balance, the work is effectively unowned.
90–61 Days Before Opening: Build the Revenue-Cycle Foundation
1. Confirm the Legal, Provider, and Location Data
Create a controlled source of truth for the practice and every provider. Validate the legal business name, tax ID, Type 1 and Type 2 NPIs, taxonomy codes, service and billing addresses, phone numbers, licenses, ownership, bank account, W-9, and payer correspondence details.
Names, addresses, NPIs, TINs, and taxonomy information should be consistent across NPPES, PECOS, CAQH, payer applications, contracts, the EHR, practice-management system, clearinghouse, bank, and accounting records. CMS specifically notes that NPPES changes do not automatically update PECOS, so both records must be maintained. See the CMS PECOS fact sheet.
2. Build a Payer Readiness Matrix
Create one row for each provider, group, location, payer, and product combination. Track:
- application and contract status;
- participating products or networks;
- approval and effective dates;
- group and rendering-provider linkage;
- approved service location;
- payer ID and claim route;
- eligibility and claim-status connectivity;
- ERA and EFT status;
- portal access and authorized users;
- directory status; and
- the evidence supporting each completed status.
Use our provider credentialing timeline to understand why “application submitted” and “ready to bill” are not the same state.
For the operational fields, documents, status definitions, and first-claim checkpoints, use the full payer enrollment checklist for a new medical practice.
3. Choose the Billing Operating Model
Decide whether billing will be managed in-house, outsourced, or through a hybrid model. Document who owns registration quality, eligibility, authorizations, coding, charge entry, claim review, submission, rejections, denials, payment posting, A/R, patient balances, refunds, and reporting.
If the decision is still open, compare the full operating model in our guide to medical billing software versus outsourced billing for a new practice.
4. Finalize the Technology Stack and Interfaces
Confirm the EHR, practice-management/billing platform, clearinghouse, eligibility tools, patient portal, payment processor, statement vendor, telehealth system, accounting system, and analytics solution. Identify every interface, file, user account, and implementation dependency.
For each system, document:
- contract and implementation owner;
- production and training access;
- roles and least-privilege permissions;
- provider, location, payer, and bank configuration;
- data flow and interface direction;
- support contacts and severity definitions;
- backup and downtime workflow;
- data ownership and export rights; and
- security review and business associate agreement where applicable.
5. Approve the Financial and Patient-Payment Policies
Before staff training begins, approve written policies for:
- insurance participation and out-of-network situations;
- eligibility and benefit verification;
- referrals and prior authorization;
- patient estimates and financial responsibility;
- copay, deductible, coinsurance, deposit, and self-pay collection;
- credit balances, refunds, adjustments, and write-offs;
- payment plans, returned payments, statements, and collections;
- financial assistance when applicable;
- medical-record requests and payer documentation; and
- staff authority limits and required approvals.
6. Build the Cash-Flow Ramp
Model weekly cash from opening through at least the first three to six months. Include the schedule ramp, payer mix, expected charges, contractual adjustments, lag from service to claim, adjudication time, patient payments, refunds, vendor fees, payroll, rent, and debt obligations.
Maintain working capital for a slower-than-planned ramp. Payer enrollment, claim rejections, documentation delays, and implementation defects can postpone collections even when patient demand is strong.
60–31 Days Before Opening: Configure Workflows and Controls
7. Configure Providers, Locations, Payers, and Fee Schedules
Build provider records with the correct billing and rendering NPIs, taxonomy, credentials, service locations, supervising or ordering relationships where applicable, payer participation, and effective dates. Configure payer IDs, electronic connections, fee schedules, timely-filing rules, claim requirements, and contract terms.
Use controlled naming conventions. Duplicate payer plans, inconsistent provider names, and wrong location mappings create claim and reporting problems that can be difficult to diagnose after go-live.
8. Design Scheduling, Registration, and Eligibility Workflows
Define the required data for appointment creation, preregistration, check-in, and check-out. Staff should know how to handle:
- new versus established patients;
- legal name, date of birth, address, contact, and guarantor validation;
- subscriber and member information;
- primary, secondary, and tertiary coverage;
- coordination of benefits;
- payer product and network selection;
- coverage not found or inactive;
- workers’ compensation, auto, attorney, or liability cases;
- self-pay and uninsured patients; and
- patient consent, privacy, financial, and communication forms.
Eligibility results should be interpreted, not merely saved. Identify deductible, coinsurance, copay, benefit limitations, referral requirements, authorization indicators, and payer-specific caveats.
9. Define Referral and Prior-Authorization Ownership
Create procedure- and payer-specific workflows for determining whether a referral or authorization is required, obtaining it, matching it to the correct provider/location/service/date, documenting the number and approved units, monitoring expiration, and escalating changes.
Scheduling, clinical, and billing teams should see the same status. A patient should not arrive for a high-cost service while the authorization sits in an unmonitored inbox.
10. Build Documentation, Coding, and Charge-Capture Standards
Define the path from encounter to signed note to coded charge. Establish:
- required note templates and specialty documentation;
- time standards for completing and signing records;
- code, modifier, unit, diagnosis, and medical-necessity review;
- charge capture for office, facility, procedure, supply, drug, lab, and telehealth services as applicable;
- rules for missing, late, amended, or conflicting documentation;
- coding-query format and response time;
- who may change codes and how changes are audited; and
- periodic coding quality review.
11. Configure Claim Edits and Submission Controls
Build claim rules for provider identifiers, payer IDs, place of service, taxonomy, modifiers, referring/ordering providers, authorization numbers, diagnosis-to-procedure relationships, units, NDC information, attachments, and payer-specific requirements.
Define daily controls:
- encounters without charges;
- unsigned or incomplete notes;
- claims on hold and the reason;
- clearinghouse rejections;
- payer acceptance acknowledgments;
- claims not acknowledged within the expected window; and
- timely-filing exposure.
12. Set Up Payments, ERA/EFT, and Reconciliation
Complete ERA and EFT enrollment for priority payers, establish bank and merchant accounts, and configure electronic and manual payment posting. CMS states that Medicare EFT information can be completed through PECOS with required supporting documentation such as a voided check or bank letter. Review the CMS Medicare enrollment guidance.
Design a reconciliation process that connects:
- payer and patient remittances;
- EFT, check, card, cash, and portal deposits;
- payment and adjustment transactions in the billing system;
- unapplied and unidentified cash;
- refunds and credit balances; and
- the bank and accounting ledger.
No payment should be considered complete merely because it was posted. It must also be reconciled to the actual deposit.
13. Build Denial and A/R Workflows
Define how the team will classify, route, correct, appeal, and prevent denials. Set work standards by payer, balance, age, filing or appeal deadline, and root cause. Separate insurance A/R from patient A/R and assign each queue.
Useful prebuilt categories include registration, eligibility, authorization, enrollment, coding, documentation, duplicate, bundling, medical necessity, coordination of benefits, timely filing, noncovered service, and underpayment.
14. Establish the Launch Dashboard
Agree on KPI definitions before data exists. Include operational and financial measures such as:
- scheduled, completed, canceled, and no-show visits;
- eligibility and authorization exceptions;
- unsigned encounters and charge lag;
- claims created, submitted, accepted, rejected, and held;
- gross charges and expected reimbursement;
- payments and deposits;
- denials by payer and reason;
- A/R by age, payer, provider, and responsible party;
- unapplied cash, credit balances, and reconciliation differences; and
- patient collections at scheduling, check-in, check-out, portal, and statement stages.
30–15 Days Before Opening: Test the Entire Revenue Cycle
15. Build Realistic Test Scenarios
Do not test only a simple commercial office visit. Build scenarios based on the actual specialty, payer mix, locations, and services. Include:
- new and established patients;
- commercial, Medicare, Medicaid, Medicare Advantage, and self-pay cases as applicable;
- primary and secondary insurance;
- referral- and authorization-required services;
- procedures, drugs, supplies, labs, imaging, telehealth, or facility services relevant to the practice;
- corrected claims, voids, refunds, and credit balances;
- rejections, denials, record requests, and appeals;
- patient estimates, deposits, statements, and payment plans; and
- downtime and manual-continuity workflows.
16. Run a “Day in the Life” Simulation
Have each team member perform their real work using the production configuration or a faithful training environment. Start with appointment creation and continue through registration, eligibility, authorization, documentation, coding, charge entry, claim review, submission, response, payment, patient balance, deposit, and reconciliation.
Record each defect with severity, owner, due date, retest date, and evidence of closure. A successful screen demonstration is not enough; the workflow must work across teams.
17. Test Clearinghouse and Payer Connectivity
Confirm submitter IDs, payer IDs, trading-partner approvals, eligibility connections, claim acknowledgments, ERA routing, and access to payer portals. When a payer permits test transactions, validate the actual route. When it does not, document how the first live claims will be monitored.
18. Validate Patient-Facing Billing
Review the financial policy, estimate, receipt, statement, portal balance, payment page, phone script, and collections communication as a patient would experience them. Confirm contact information, plain-language explanations, payment options, and the path for questions or disputes.
19. Rehearse Exceptions and Escalations
Ask the team what happens when:
- coverage is inactive or the payer product is unclear;
- the provider is not loaded at the location;
- an authorization is missing or does not match the service;
- a note remains unsigned;
- the clearinghouse rejects the claim;
- the payer says the provider is out of network;
- an ERA arrives without the EFT or a deposit arrives without the remittance;
- the patient disputes the balance;
- the EHR or internet connection is unavailable; or
- the billing lead is absent.
Every answer should identify the immediate action, owner, communication, escalation threshold, and documentation.
14–1 Days Before Opening: Make the Go/No-Go Decision
20. Confirm Payer Effective Dates in Writing
For each provider-location-payer-product combination, confirm the approval, contract status, effective date, billing linkage, payer ID, directory information, and ERA/EFT route. Do not schedule in-network services based only on “credentialing complete” or “loaded soon.”
21. Close High-Severity Defects
Classify unresolved issues by impact:
- Go-live blocker: could prevent safe care, compliant billing, claim creation, payment receipt, or required patient communication.
- High risk: has a temporary control but could materially affect volume, cash, or patient experience.
- Manageable: has a documented workaround, owner, monitoring, and firm correction date.
Do not hide blockers inside a general project list. Escalate them to the opening decision-maker.
22. Freeze and Document Critical Configuration
Limit last-minute changes to provider, payer, location, fee-schedule, claim-rule, bank, access, and interface configuration. Record approved settings and require a change owner, reason, test, and rollback plan.
23. Prepare the First-30-Day Command Center
Set the meeting cadence, dashboard owners, contact tree, vendor coverage, payer escalation list, and daily issue log. Assign who will review:
- yesterday’s encounters and unbilled charges;
- eligibility and authorization exceptions;
- claims held, submitted, accepted, and rejected;
- first payer adjudications and denials;
- payments, deposits, and reconciliation;
- patient billing questions and complaints; and
- system, staffing, and workflow defects.
24. Use a Controlled Opening Schedule
A gradual schedule ramp gives the team time to correct defects before volume compounds them. Protect capacity for documentation, issue review, and training during the first weeks. A full schedule on day one can create a large backlog before the first remittance reveals a configuration problem.
Revenue-Cycle Readiness Checklist by Workstream
| Workstream | Opening-day proof |
|---|---|
| Payer enrollment | Effective provider, group, location, and product combinations are documented with evidence. |
| Scheduling and registration | Required fields, forms, insurance capture, and exception rules are tested. |
| Eligibility and authorization | Ownership, payer-specific workflows, documentation, and escalation are validated. |
| Documentation and coding | Templates, completion standards, charge capture, queries, and audit controls are active. |
| Claims | Provider/payer configuration, edits, submitter IDs, acknowledgments, and rejection queues work. |
| Payments | ERA/EFT, cards, cash, checks, posting, deposits, refunds, and reconciliation are configured. |
| Denials and A/R | Work queues, priorities, deadlines, root-cause codes, and escalation owners are defined. |
| Patient billing | Estimates, collections, receipts, statements, portal, calls, plans, and dispute handling are tested. |
| Reporting | KPI definitions, dashboards, distribution, and review cadence are approved. |
| Continuity | Backup staff, downtime workflows, vendor contacts, and data access are documented. |
What Should Happen During the First 30 Days After Opening?
Opening day is the beginning of revenue-cycle validation, not the end. During the first month:
- review unbilled encounters and claim rejections every day;
- monitor the first claims for each provider, location, payer, and major service;
- separate enrollment-related failures from registration, coding, authorization, and claim-rule errors;
- track payment lag against the cash-flow model;
- reconcile every deposit and investigate unidentified cash promptly;
- listen to patient billing questions for policy or communication defects;
- fix root causes, not only individual claims;
- keep a decision and change log; and
- hold a weekly executive review of cash, risk, staffing, and unresolved defects.
Acuity’s revenue cycle management services can continue beyond launch to manage claims, denials, A/R, payments, and performance reporting.
How Can Acuity Support a 90-Day Practice Launch?
Acuity can coordinate the revenue-cycle workstream from payer readiness through tested billing operations. Support may include credentialing and enrollment, billing model selection, workflow design, system and payer configuration, front-end controls, claims, ERA/EFT, denial and A/R design, KPI development, staff training, go-live testing, and early-claim monitoring.
Schedule a startup services consultation to turn your target opening date into an accountable 90-day revenue-cycle plan.
Frequently Asked Questions About Revenue-Cycle Launch Readiness
When should a new medical practice start setting up billing?
Begin as soon as the legal entity, service model, locations, providers, payer strategy, and target opening date are defined. The final 90 days should be used for configuration, integration, training, and testing—not for making every foundational decision from scratch.
Can a practice open before every payer is effective?
Possibly, but the practice needs a payer-specific plan that addresses network status, patient communication, scheduling, financial responsibility, claim handling, and applicable contract or legal requirements. Do not assume retroactive payment will be available.
What is the most important pre-opening billing test?
The most valuable test follows a realistic patient from scheduling through eligibility, authorization, documentation, coding, claim creation, submission, response, payment, patient balance, deposit, and reconciliation. It reveals failures between systems and teams.
Should ERA and EFT be completed before opening?
Complete them as early as payer processes allow. Some payers require separate enrollment after approval. Until ERA and EFT are active, document how remittances and payments will be received, posted, secured, and reconciled.
Which revenue-cycle KPIs matter during the first month?
Start with charge lag, unsigned encounters, claim holds, rejection rate, payer acceptance, first denials, payment lag, deposits, reconciliation differences, patient collections, and enrollment-related failures. Mature collection metrics need enough time and volume to become meaningful.
How much cash reserve should a new practice keep?
The answer depends on fixed expenses, payer mix, schedule ramp, reimbursement, debt, and owner risk tolerance. Build a conservative weekly cash model and fund a slower collection ramp than the best-case forecast. Obtain financial advice tailored to the practice.
Who should attend the final go-live review?
The physician or executive sponsor, practice administrator, credentialing lead, billing/RCM lead, EHR or implementation lead, front-desk lead, payment/accounting contact, and any vendor responsible for a critical unresolved dependency should attend.




