When to use this playbook
- You are opening a physician, therapy, behavioral health, or other clinical practice and want insurance billing available on opening day.
- You have signed a lease or chosen an opening date and need to know how far ahead to start credentialing.
- You need the correct dependency sequence for entity formation, EIN, Type 1 and Type 2 NPIs, DataSpring, Medicare, Medicaid, commercial payers, and claims setup.
- You are launching several providers and need to coordinate individual enrollment, group enrollment, contracting, effective dates, and billing activation.
- You are deciding whether to manage the work internally or hand it to a credentialing and payer-contracting partner.
What success looks like
Success is not “application submitted” or even “credentialing approved.” The practice has one consistent legal identity across its IRS, NPPES, DataSpring, payer, contract, and claims records. Every provider is linked to the correct group, tax ID, location, network product, and effective date, and the billing system can transmit claims and receive remittance files.
For insurance billing on day one, begin the foundational work at least 120 days before the target opening. A 180-day runway is safer for a three-provider launch, Medicaid managed care, several states, or payers with separate contracting and credentialing stages. Published timelines range from about 45 to 60 days for Cigna credentialing to 90 to 120 days across Aetna's broader onboarding sequence, while Arctic Health averages 60 to 90 days after a file is ready. Cigna Healthcare credentialing Aetna provider onboarding timeline Arctic Health
The operating model is worth naming: serial foundation, parallel payer tracks, final claims activation. Entity, tax, NPI, insurance, and provider-data work must happen in order. Medicare, Medicaid, and commercial applications can then move in parallel, but billing activation waits for written effective dates and correctly loaded payer records.
Know the three payer processes before you start
Credentialing, enrollment, and contracting solve different problems. Treating them as one application is how a practice ends up professionally approved but unable to submit a payable in-network claim.
| Process | What it does | Required outcome | Common failure |
|---|---|---|---|
| Credentialing | Verifies the provider's licensure, training, work history, malpractice coverage, and professional qualifications. | The payer approves the provider for network participation. | The practice assumes a complete DataSpring or CAQH profile means the payer has approved the provider. |
| Enrollment | Registers the provider, organization, locations, tax ID, affiliations, and billing identifiers in the payer's systems. | The payer can recognize the correct rendering and billing relationship when a claim arrives. | The provider is approved individually but is not affiliated with the group or service location. |
| Contracting | Establishes network participation terms, covered products, reimbursement, and the effective date. | A fully executed agreement and a usable participation date. | The practice treats credentialing approval as proof that the contract is active. |
UnitedHealthcare requires credentialing and contracting before a provider begins seeing members as in-network. Aetna also separates credentialing from network contracting and uses the CAQH Provider Data Portal for professional credentialing. UnitedHealthcare network participation Aetna network participation
Step-by-step process
The order below is a dependency sequence, not merely a checklist. An upstream mismatch can delay every payer application that depends on it, while a clean foundation lets the government and commercial tracks run at the same time.
The new-practice insurance billing dependency table
| Step | What it requires | What it unblocks | Planning window | Consequence of doing it out of order |
|---|---|---|---|---|
| 1. Legal entity and EIN | Final legal name, ownership structure, responsible party, and state formation | Business banking, W-9, Type 2 NPI, group payer records, contracts, and EFT | State filing time varies; an online EIN can be issued in minutes after formation | A later entity-name or tax-ID correction can force changes across NPPES, DataSpring, PECOS, payer applications, and contracts. |
| 2. Type 1 and Type 2 NPIs | Provider identity, organization identity, taxonomy codes, EIN, and practice address | Individual applications, group applications, Medicare enrollment, affiliations, and claims configuration | Usually days through the online NPPES process; paper applications take longer | Without the Type 2 NPI, an organizational practice cannot complete group enrollment. Downstream payer queues do not begin. |
| 3. DataSpring provider profiles | Type 1 NPI, licenses, education, work history, locations, disclosures, and supporting documents | Commercial credentialing files that rely on the CAQH Provider Data Portal | Several hours to several days when documents are ready | An incomplete, unattested, stale, or unauthorized profile can leave an application in intake rather than credentialing review. |
| 4. Malpractice coverage and final document packet | Final provider names, entity, locations, specialties, and requested coverage dates | Final DataSpring attestation and payer applications that require proof of active professional liability coverage | Carrier-dependent; complete before the payer submission wave | The payer can hold the file as incomplete, creating another documentation and review cycle. |
| 5. Medicare through PECOS | NPIs, EIN or TIN, practice locations, ownership, authorized officials, EFT details, and the correct enrollment path | Original Medicare billing privileges and provider-to-group reassignments | CMS identifies approximately 45 days for MAC review, with longer processing possible | The wrong enrollment type or a missing group relationship can consume a full review cycle without creating a billable arrangement. |
| 6. State Medicaid enrollment | State-specific provider, organization, ownership, license, and screening data | Eligibility to participate in Medicaid fee-for-service and Medicaid managed care networks | State-specific and often multiweek | An MCO application cannot substitute for required enrollment with the state Medicaid agency. |
| 7. Medicaid MCO applications | State Medicaid enrollment plus each plan's network, contracting, credentialing, and roster requirements | Access to members enrolled in each selected Medicaid managed care plan | Plan-specific and separate from the state timeline | State approval alone does not activate every MCO. The practice can remain unable to bill most local Medicaid membership. |
| 8. Commercial payer applications | Entity, EIN, NPIs, complete DataSpring profiles, malpractice coverage, locations, and target products | Credentialing, contracting, provider loading, and commercial network effective dates | About 45 to 120 days in published payer examples, sometimes longer | A deficient application can extend the payer's normal timeline or be closed before review is completed. |
| 9. Contract and effective-date confirmation | Credentialing approval, executed participation terms, group affiliations, and payer-system loading | Accurate in-network scheduling and claims release | May follow credentialing by days or several additional weeks | Seeing patients based on approval alone creates claims that can deny because the contract, group, product, or location is not active. |
| 10. EDI, ERA, and EFT activation | Approved payer records, billing NPIs, TIN, bank information, clearinghouse or billing vendor, and payer IDs | Electronic claims, remittance files, and payments | Payer-specific; complete before releasing the first claim | The practice can be in-network on paper but still lack a working route to submit claims or reconcile payments. |
Evidence used: IRS EIN guidance, CMS NPI fact sheet, DataSpring clinician guidance, UnitedHealthcare credentialing requirements, CMS Medicare enrollment applications, CMS Medicaid Provider Enrollment Compendium, and CMS EDI enrollment guidance.
Step 1: Form the practice entity and obtain its EIN
Action: Finalize the legal entity that will contract with payers and receive insurance payments. Obtain the EIN under the entity's exact legal name, then use that same name and tax ID on the W-9, bank account, NPPES record, Medicare enrollment, commercial applications, and contracts.
Expected outcome: One stable legal and tax identity for the billing organization.
What this blocks: The organizational NPI, group payer applications, group contracts, EFT enrollment, and provider-to-group affiliations cannot be configured reliably until the entity and tax identity are final.
Gotchas: Do not build the payer file under a working name and then change the legal name or EIN after applications are underway. That turns a foundational setup task into corrections across every downstream system.
Step 2: Obtain the correct Type 1 and Type 2 NPIs
Action: Confirm that every rendering clinician has a Type 1 individual NPI. Obtain a Type 2 organizational NPI for a corporation, partnership, professional entity, or other organization that will bill as the group. A true sole proprietor is treated as a Type 1 provider for NPI purposes, while an organization billing under its own entity uses a Type 2 NPI.
Expected outcome: The practice can identify both the clinician who performed the service and the entity billing for it.
What this blocks: Medicare's CMS-855B group enrollment expressly requires the organizational NPI. Commercial and Medicaid group applications also depend on the practice's billing identity, so applying for payers before the Type 2 NPI exists does not create a usable shortcut.
Gotchas: The legal business name and TIN entered in NPPES must match the organization information used in PECOS and payer records. Select the provider and organization taxonomy codes carefully because they flow into enrollment and claims configuration. CMS NPI application guidance
Step 3: Build each provider's DataSpring profile
Action: Complete the CAQH Provider Data Portal profile, formerly CAQH ProView and now operated by DataSpring, powered by CAQH. Enter the provider's licenses, education, training, work history, specialties, practice locations, disclosures, and identifying information.
Expected outcome: One payer-ready professional profile that authorized commercial plans can retrieve.
What this blocks: Aetna and many other commercial payers rely on the portal for credentialing data. A profile that merely exists does not unblock review unless it is complete, attested, current, and authorized for the applicable payer.
Gotchas: DataSpring requires re-attestation every 120 days for most providers. Put the re-attestation date on an operating calendar rather than waiting for a payer to report that the profile has expired. DataSpring Provider Data Portal guide
Step 4: Bind malpractice coverage and finish the document packet
Action: Secure professional liability coverage with the correct provider names, entity, locations, specialties, limits, and effective dates. Upload the insurance face sheet or certificate to DataSpring and include it in the standardized payer packet.
Expected outcome: Credentialing files can be treated as complete rather than held for proof of coverage.
What this blocks: Several payers gate credentialing on active malpractice coverage or an accepted state-approved alternative. UnitedHealthcare includes active professional liability insurance among its credentialing requirements.
Gotchas: Do not wait for the first payer deficiency notice to purchase coverage. The provider name, policy number, expiration date, and practice information should match the profile and uploaded document.
Step 5: Standardize the complete credentialing packet
Action: Create one controlled source of truth for every provider and the practice entity.
| Category | Items to prepare | Consistency check |
|---|---|---|
| Entity and tax | Formation record, EIN confirmation, W-9, ownership details, authorized officials, bank and EFT information | Legal name and TIN match NPPES and every payer application |
| Provider identity | Type 1 NPI, licenses, taxonomy, government ID data requested by the applicable program, and contact information | Name and credentials match the license and NPPES record |
| Qualifications | Education, postgraduate training, board certification, specialty, work history, and explanations for material work-history gaps | Dates agree across the CV, DataSpring profile, and payer forms |
| Practice operations | Service locations, correspondence address, billing address, office hours, phone numbers, telehealth locations, and admitting arrangements where requested | Every location is tied to the correct entity, provider, taxonomy, and intended payer products |
| Risk and compliance | Malpractice face sheet, claims history, DEA or controlled-substance registration when applicable, disclosures, and sanctions information | Coverage and credentials remain active through the anticipated review period |
Expected outcome: Every payer receives the same names, dates, identifiers, locations, and supporting records.
Gotchas: Inconsistency causes more delays than a clearly missing document. A payer can resolve an identified missing item, but conflicting entity names, addresses, work histories, and affiliations force the reviewer to determine which version is correct.
Step 6: Enroll the individuals and group with Medicare through PECOS
Action: Use PECOS for Original Medicare enrollment. Physicians and non-physician practitioners use the CMS-855I enrollment path. Clinics and group practices use CMS-855B. The CMS-855I now includes reassignment actions formerly handled through CMS-855R, allowing the clinician's Medicare benefits to be reassigned to the group that will bill for the services.
Expected outcome: The organization is enrolled, each clinician is enrolled, and the required clinician-to-group billing relationships are active.
What this blocks: A CMS-855I approval without the required group enrollment or reassignment does not establish the intended group billing relationship. CMS-855O is for professionals who enroll solely to order or certify services, not clinicians who intend to bill Medicare for patient care.
Gotchas: Ownership, authorized-official, location, EFT, NPI, and TIN details must align. Medicare Administrative Contractors process the applications and can request additional documentation. Use the detailed Medicare enrollment form guide when the practice structure involves more than a standard physician or therapy group. CMS Medicare provider enrollment
Step 7: Complete state Medicaid enrollment before the MCO layer
Action: Enroll the providers and organization with the state Medicaid agency. Complete the state's screening, ownership, license, location, affiliation, and program requirements before treating managed care participation as complete.
Expected outcome: The providers and billing entity are recognized by the state Medicaid program.
What this blocks: Federal requirements generally require Medicaid managed care network providers to be enrolled with the state agency. A contract or application with an MCO does not replace the state enrollment layer.
Gotchas: Medicaid is not one national application. Each state has its own portal, classifications, screening process, identifiers, effective dates, and maintenance requirements.
Step 8: Apply to each target Medicaid MCO separately
Action: After starting or completing the required state enrollment, apply to the managed care plans serving the practice's target patients. Complete each plan's contracting, credentialing, roster, location, and product steps.
Expected outcome: The practice can serve members assigned to each selected Medicaid plan, not just fee-for-service Medicaid.
What this blocks: State Medicaid approval does not automatically activate UnitedHealthcare Community Plan, Molina, Centene plans, Elevance-affiliated plans, or other MCOs operating in that state.
Gotchas: Track the state and each MCO as separate payer relationships with separate approval and effective dates. The state-by-state Medicaid and MCO guide explains how the layers differ.
Step 9: Submit commercial applications as a coordinated wave
Action: Apply to the commercial plans that match the practice's patient mix, referral sources, specialty, and geography. Begin the commercial wave as soon as the entity, NPIs, DataSpring profiles, malpractice coverage, and standardized documents are complete. Medicare, Medicaid, and commercial applications do not need to wait for one another after those dependencies are satisfied.
Expected outcome: Every target payer has a complete application tied to the correct provider, group, TIN, locations, and network products.
What this blocks: Broad applications submitted before the group identity and provider files are ready create deficiency work rather than useful queue time.
Gotchas: Blue Cross Blue Shield applications usually run through the relevant local company rather than one national credentialing office. Medical and behavioral networks can also use different entry points under the same parent organization.
Step 10: Track every payer like a revenue workflow
Action: Track the submission date, confirmation number, payer contact, missing items, DataSpring access, contracting stage, next follow-up date, approval, effective date, provider loading, and billing status for each provider-payer-product combination.
Expected outcome: A stalled application has a named owner and next action rather than a generic “pending” status.
What this blocks: Payer review does not reliably advance through passive waiting. Cigna can close an application when requested missing information is not supplied, and other plans can stop review until deficiencies are resolved.
Gotchas: Ask whether the file is in intake, credentialing verification, committee review, contracting, roster loading, or claims-system loading. Those stages require different interventions. Cigna credentialing process
Step 11: Review contracts and confirm the real effective date
Action: Review the participation agreement, covered products, fee schedule, location scope, notice terms, and effective date before signing. After execution, confirm that the payer loaded the provider under the correct group, TIN, locations, and products.
Expected outcome: The practice knows which patients can be represented as in-network and the earliest covered date of service.
What this blocks: Credentialing approval alone does not prove that claims will process at contracted rates. The operational go-live requires the contract, enrollment relationship, effective date, and claims record to align.
Gotchas: Cigna notes that directory and claims-system loading can take up to 10 additional business days after credentialing approval. Treat the written effective date and loaded billing relationship as the finish line, not the approval email.
Step 12: Activate EDI, ERA, EFT, and the billing workflow
Action: Connect the practice-management system, billing service, or clearinghouse to each payer. Complete electronic data interchange enrollment for claims, electronic remittance advice enrollment for payment explanations, and electronic funds transfer enrollment for deposits. Configure payer IDs, rendering and billing NPIs, TIN, taxonomy, locations, and group affiliations.
Expected outcome: The practice can verify eligibility, transmit a clean claim, receive an acknowledgment, post the remittance, and reconcile the payment.
What this blocks: Payer approval without EDI and remittance setup leaves the practice with no reliable claims or payment workflow. CMS requires its EDI agreement before electronic Medicare claims or other EDI transactions are submitted.
Gotchas: Test the complete chain before the first high-volume billing day. Aetna and other payers use separate enrollment workflows for ERA and EFT, so network participation does not activate those transactions automatically. Aetna electronic payment and remittance
Step 13: Set up ongoing maintenance from day one
Action: Put DataSpring re-attestation, license and malpractice expirations, Medicare revalidation, payer recredentialing, roster maintenance, address changes, ownership changes, and contract notices into a recurring operating process.
Expected outcome: The practice stays in-network after launch instead of drifting into provider-directory errors, eligibility denials, or terminated participation.
Gotchas: Credentialing is not a one-time opening project. Every provider, payer, location, and product remains an active relationship that requires maintenance.
Typical launch timeline for a new practice
| Time before opening | Work that should be underway | Launch risk if delayed |
|---|---|---|
| 180 to 120 days | Form the entity, obtain the EIN, finalize the billing identity, obtain Type 1 and Type 2 NPIs, secure licenses and malpractice coverage, and assemble the document packet. | The payer review clock cannot start with a usable application. |
| 120 to 90 days | Complete and attest DataSpring profiles. Submit Medicare, state Medicaid, Medicaid MCO, and priority commercial payer applications in parallel. | A day-one insurance launch becomes dependent on retroactivity that may not exist. |
| 90 to 30 days | Answer deficiencies, follow up with payers, complete contracting, review fee schedules, and verify provider-to-group affiliations. | Applications remain nominally pending without reaching approval or contracting. |
| 30 days to opening | Confirm written effective dates, complete payer-system loading, activate EDI, ERA, and EFT, configure billing rules, and segment the patient schedule by payer readiness. | The practice opens with approvals but no reliable claims or payment path. |
| Opening week | Bill only under confirmed arrangements, monitor clearinghouse acknowledgments, and audit the first claims and remittances. | Enrollment or configuration errors compound across the first billing cycle. |
Signing a lease next quarter is a reason to start now, not a reason to wait for construction or equipment setup. Payer timelines run independently of the physical buildout, and many applications need the final entity, address, identifiers, insurance, and provider documents long before the first patient arrives.
Seeing patients and billing while credentialing is pending
A properly licensed clinician can generally see patients before commercial payer approval, but a submitted application does not make the clinician in-network. The practice needs a defensible payment path before the visit: confirmed in-network participation, written retrospective coverage, accurate out-of-network billing, disclosed self-pay, or rescheduling.
| Status on the service date | Can the visit be represented as in-network? | Likely claim outcome | Operational response |
|---|---|---|---|
| Application pending with no written effective date | No | The claim can reject, deny, or process outside the anticipated network relationship. | Use a clearly disclosed self-pay or out-of-network arrangement, or reschedule. |
| Written retrospective date covers the service | Only as allowed by the payer's written instructions | The claim may be payable after the provider record is loaded. | Confirm whether to hold, submit, or resubmit the claim and preserve the timely filing deadline. |
| Credentialing approved, but contract or group loading is incomplete | No | The claim can deny for provider eligibility, affiliation, location, or network status. | Correct the payer record before treating approval as go-live. |
| Effective date and billing relationship are active | Yes, for the confirmed products and locations | The claim can be processed under the in-network arrangement. | Verify eligibility, authorization, claim identifiers, and timely filing before submission. |
| Service occurred before every approved or retrospective date | No | A later approval does not automatically make the earlier service payable. | Use the valid patient-payment arrangement established before care. Do not substitute another provider's NPI. |
Medicare has a defined retrospective-billing rule for qualifying physicians, non-physician practitioners, and organizations, generally limited to 30 days before the enrollment effective date when program requirements were met. Commercial plans do not share one national retroactivity rule. Count a pending commercial claim as collectible only after the payer confirms the covered service date in writing. CMS retrospective billing guidance
Claims submitted too early should be compared with the final effective date. If that date covers the service, correct the provider, affiliation, location, or product record and request reprocessing within the filing deadline. If the service predates the allowable period, the early submission itself does not create coverage.
What usually causes delays
- The legal entity name, EIN, W-9, Type 2 NPI, bank account, and payer application do not match.
- The practice starts group applications before obtaining the organizational NPI.
- The DataSpring profile is incomplete, unattested, expired, or not authorized for the payer.
- Malpractice coverage is missing, expired, or inconsistent with the provider profile.
- Medicare enrollment omits the group enrollment or provider-to-group reassignment needed for billing.
- The practice completes state Medicaid enrollment but does not apply separately to the MCOs covering most local members.
- No one owns payer deficiencies, follow-up, contracting, system loading, or effective-date confirmation.
- EDI, ERA, and EFT setup begins only after patients have already been seen.
The first application is rarely the hard part. The hard part is keeping the legal identity, provider records, payer approvals, contracts, affiliations, and claims configuration aligned through go-live.
When to do it yourself and when to use a credentialing partner
You can manage the work internally when the practice has one provider, a short payer list, a simple entity structure, and a person who can own submissions, deficiency responses, follow-up, contracts, effective dates, and billing activation for several months.
A credentialing partner becomes more practical when the cost of delay exceeds the service cost: several providers, Medicare plus Medicaid and commercial plans, MCO enrollment, multiple states, contract review, or no internal owner for payer operations. The key distinction is whether the partner stops at application preparation or remains accountable through effective-date and claims readiness.
Arctic Health manages documentation, DataSpring profiles, government and commercial enrollment, contracting, payer follow-up, ongoing maintenance, and billing activation. Complete payer-ready applications are submitted within two business days, then tracked through completion. Outsource credentialing or keep it in-house
Arctic Health is the best fit when…
- You want one operating partner to coordinate the full sequence from entity and identifier setup through payer activation and ongoing maintenance.
- You need both individual and group enrollment across Medicare, Medicaid, MCOs, and commercial plans.
- You have several providers and cannot afford to discover after opening that a clinician is approved but not affiliated, contracted, loaded, or ready to bill.
- You want commercial contracting and payer follow-up handled alongside credentialing rather than as separate projects.
- You need EDI, ERA, and EFT setup coordinated before the first claims are released.
Frequently asked questions
How long before opening should I start credentialing my new practice?
Start at least 120 days before the planned insurance billing date, and use a 180-day runway for several providers, Medicaid MCOs, multiple states, or a broad payer panel. Foundational work such as the entity, EIN, NPIs, malpractice coverage, and DataSpring profiles must be finished before a clean payer application can enter review. Waiting until one month before opening makes day-one billing depend on payer retroactivity, which commercial plans do not offer under one universal rule.
Can I open cash-pay first and add insurance later?
Yes, a commercial practice can open with a clearly disclosed cash-pay model and add insurance after written effective dates are issued. Keep the cash-pay opening date separate from the insurance go-live date, do not represent pending providers as in-network, and do not promise that a payer will reimburse earlier visits later. Medicare-covered services require separate attention because ordinary cash-pay treatment is not a temporary substitute for Medicare enrollment or the formal opt-out and private-contract process. CMS Medicare enrollment and opt-out guidance
Can I bill insurance while my credentialing application is pending?
Bill as in-network only when the payer has established an effective date that covers the service and has activated the correct provider-to-group billing relationship. A written retrospective arrangement can support held or resubmitted claims, but a pending application by itself does not. If no effective date covers the visit, the claim can deny, process out of network, or remain uncollectible under the anticipated contract.
What happens to claims submitted before my effective date?
Claims for services before the allowable effective or retrospective date commonly deny or process outside the network arrangement. If the final effective date covers the service, correct any provider-record problem and request reprocessing or submit a corrected claim within the payer's filing deadline. If the date does not cover the service, the original submission does not create payment rights, and the practice must not replace the actual rendering provider with a credentialed provider's NPI.
How much does credentialing with the major payers cost?
Credentialing has no single national price because the real scope is measured by providers, payers, products, states, locations, group applications, government programs, contracting, and maintenance. The IRS issues EINs without a fee, NPPES does not charge for an NPI, the DataSpring Provider Data Portal is free for clinicians and practices, and physicians, non-physician practitioners, and their groups do not pay a Medicare enrollment application fee. The variable costs are entity formation, licenses, malpractice coverage, staff time, billing infrastructure, and any outside service. DataSpring Provider Data Portal resources CMS Medicare application-fee rules
Do I need malpractice insurance before I can be credentialed?
Secure malpractice coverage before the main payer submission wave because DataSpring collects professional-liability information and several payers require proof of coverage in a complete credentialing file. UnitedHealthcare requires active professional liability insurance or an accepted state-approved alternative. Waiting until a payer requests the face sheet can move the file back into deficiency handling rather than substantive review.
Which insurance panels should a solo therapist join first?
Join the panels that repeatedly appear in real patient inquiries, referrals, and eligibility checks, not every recognizable national brand. Optum and Evernorth deserve early review when UnitedHealthcare and Cigna products are common. Carelon and Magellan move up the list when they administer locally important employer, Anthem-affiliated, Medicaid, or public-sector benefits. Compare each panel's offered rates, license eligibility, products, documentation burden, and referral demand before signing. Behavioral health panel decision guide
References
- Arctic Health credentialing and payer enrollment services
- IRS employer identification number guidance
- CMS NPI fact sheet
- DataSpring clinician and Provider Data Portal guidance
- CMS PECOS enrollment applications
- CMS Medicaid Provider Enrollment Compendium
- Aetna network participation guidance
- UnitedHealthcare network participation guidance
- Cigna Healthcare credentialing guidance
- CMS Medicare EDI enrollment guidance