> ## Documentation Index
> Fetch the complete documentation index at: https://mso.getlemma.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Enroll with payers, again

> Why payer enrollment doesn't transfer between states, what you can reuse, and how to manage the revenue gap while the new PC waits.

Payer enrollment is **per entity, per payer, per state**, and your new PC is a new entity with a new EIN and a new Type 2 NPI. Almost none of your existing enrollment carries over. Plan for another 90 to 180 days before the second state pays a claim.

## What does not transfer

|                      | Why not                                                                                                       |
| -------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Group contracts**  | Signed by a specific legal entity. The new PC is a different one, even with the same brand and the same MSO.  |
| **Group NPI**        | New entity, new EIN, new Type 2 NPI.                                                                          |
| **Provider linkage** | Even a clinician already credentialed with a payer in state one must be linked to the *new* group's contract. |
| **Medicaid**         | A different state program entirely, different application, different rules, different managed care plans.     |
| **EDI / ERA / EFT**  | Per payer per Tax ID. New enrollments for every payer.                                                        |
| **Fee schedules**    | Negotiated per contract and per market. Rates in the new state will differ, sometimes a lot.                  |

## What you can reuse

Genuine savings, if your first-state hygiene was good:

|                           | How it helps                                                                                |
| ------------------------- | ------------------------------------------------------------------------------------------- |
| **Clinician Type 1 NPIs** | Follow the person for life. Add the new practice location in NPPES.                         |
| **CAQH profiles**         | Update with the new state license and the new practice location; re-attest. No rebuild.     |
| **Payer relationships**   | A provider relations rep who knows your group can accelerate the new application. Use them. |
| **Your process**          | The tracking grid, the follow-up cadence, and the documents packet are all reusable.        |
| **Malpractice carrier**   | Often extends to the new state; confirm limits meet the new payers' minimums.               |

<Tip>
  **Contact your existing payers' provider relations before applying cold.** National carriers, UnitedHealthcare, Aetna, Cigna, Humana, often have a group-level process for adding a Tax ID to an existing relationship that is materially faster than a fresh application. Regional Blues generally do not, because each Blue licensee is a separate company.
</Tip>

## The Blues are separate companies

This surprises people expanding from a Blue-dominated market. "Blue Cross Blue Shield" is an association of roughly thirty independent licensee companies, each operating in its own geography. Your relationship with the Colorado Blue is not a relationship with the Arizona Blue: new contract, new credentialing, new everything.

What *does* work across Blues is **BlueCard**, the program that lets you bill your local Blue for a member of an out-of-area Blue. That handles the traveling patient. It does not substitute for network participation where you have an office. See [BCBS Association](/reference/payers/profiles/bcbs-association).

## Medicare in the new state

Medicare enrollment is federal but administered regionally through **Medicare Administrative Contractors (MACs)**. Practically:

* The new PC needs its own **CMS-855B** group enrollment
* Each clinician needs **CMS-855I** and a reassignment of benefits to the new group
* **CMS-588** for EFT to the new PC's bank account
* A different MAC may process it, with different local coverage determinations that affect medical necessity denials

An existing Medicare relationship in another state does not shorten this. See [Enroll in Medicare](/guides/enrollment/enroll-in-medicare).

## Medicaid is a different program entirely

Not a variation, a separate program with its own statute, portal, provider types, screening levels, site-visit requirements, and revalidation cycle. Budget the most time here.

And remember the two-layer structure: enrolling with the **state Medicaid agency** is necessary but often not sufficient. Most Medicaid beneficiaries are in **managed care plans** (Centene brands, Molina, regional plans), and each MCO requires its **own** contract and credentialing on top of state enrollment. A state with five Medicaid MCOs is six enrollments. See [Enroll in state Medicaid](/guides/enrollment/enroll-in-medicaid).

## Managing the revenue gap

The new PC will have expenses for months before it has revenue. Handle it deliberately:

**Sequence the launch around enrollment, not the lease.** Start payer applications the moment the new PC has an EIN and Type 2 NPI, before you sign a lease, before you hire, before you have a location. Applications don't require an operating practice.

**Fund the gap properly.** The MSO covering the new PC's costs is fine; the MSO covering them with no documentation is not. Use a written intercompany promissory note with a real rate — no less than the applicable federal rate for the term — and a repayment schedule. See [Intercompany loans between MSO and PC](/reference/legal/intercompany-loan-note).

**Consider a phased opening.** Cash-pay or self-pay services can start before network participation. Just be clear with patients about their out-of-network status and comply with Good Faith Estimate requirements for uninsured and self-pay patients under the No Surprises Act. See [The No Surprises Act, briefly](/concepts/compliance/no-surprises-act).

**Ask for retro-effective dates in writing** at application time, not after. Some payers grant them; you will never get one you didn't ask for.

<Warning>
  **Do not bill state two's services under state one's PC.** It is the most tempting shortcut in expansion and it is straightforwardly improper: wrong entity, wrong Tax ID, services rendered by a clinician not linked to that contract, and in many cases a licensure problem on top. It is a false claims exposure, not a billing irregularity. Wait for enrollment, or don't see insured patients yet.
</Warning>

## The tracking grid, expanded

Your single-state grid becomes a three-dimensional one. Track, per row:

| Column                  | Example                              |
| ----------------------- | ------------------------------------ |
| Entity                  | Meridian Dermatology of AZ, P.C.     |
| Tax ID                  | 88-XXXXXXX                           |
| Group NPI               | 1XXXXXXXXX                           |
| Payer                   | Regional Blue (AZ)                   |
| Clinician               | Dr. Reyes                            |
| Contract status         | Executed                             |
| Contract effective date | 2026-11-01                           |
| Credentialing status    | Committee review                     |
| Provider effective date | Pending                              |
| EDI enrolled            | ✅                                    |
| ERA enrolled            | ✅ (pointed at current clearinghouse) |
| EFT enrolled            | ✅ (AZ PC operating account)          |
| Timely filing limit     | 90 days                              |
| Recredentialing due     | —                                    |

At two states and three payers this fits in a spreadsheet. At five states and ten payers with twenty clinicians it does not, and credentialing software becomes worth its cost. See [Track licenses, revalidations, and expirables](/guides/enrollment/maintain-revalidations).

## Checklist

* [ ] New PC's Type 2 NPI obtained
* [ ] Existing payers' provider relations contacted about adding the new Tax ID
* [ ] Applications submitted before the lease, not after
* [ ] Medicare 855B, 855I, and 588 submitted for the new entity
* [ ] State Medicaid application submitted
* [ ] Every Medicaid MCO identified and separately applied to
* [ ] Clinician CAQH profiles updated with the new state license and location, and re-attested
* [ ] Retro-effective dates requested in writing
* [ ] EDI, ERA, and EFT enrolled per payer, with EFT pointed at the **new PC's** account
* [ ] Revenue gap funded with a documented note, not an undocumented transfer
* [ ] Tracking grid expanded to entity × payer × clinician

## Next

<Card title="Banking and books for entity #3" icon="arrow-right" href="/start/second-state/banking-and-books">
  Where multi-entity operations start to hurt.
</Card>


## Related topics

- [Enroll and contract with commercial payers](/guides/enrollment/enroll-with-commercial-payers.md)
- [Enroll in Medicare (PECOS)](/guides/enrollment/enroll-in-medicare.md)
- [Enroll in state Medicaid](/guides/enrollment/enroll-in-medicaid.md)
- [Set up EDI, ERA, and EFT with each payer](/guides/enrollment/set-up-edi-era-eft.md)
- [The US payer landscape](/concepts/payments/the-payer-landscape.md)
- [Why multi-state groups have one PC per state](/concepts/entities/one-pc-per-state.md)
- [Payer enrollment & submission links](/reference/payers/enrollment-links.md)
- [Blue Cross Blue Shield Association and the Blue plans](/reference/payers/profiles/bcbs-association.md)
- [Medicaid](/reference/payers/profiles/medicaid.md)