US Medical BillingRevenue cycle solutions
Credentialing

Enrollment Maintenance: The Records That Lapse

Onboarding a new provider has an owner, a deadline, and everybody watching. Keeping an established one enrolled has none of those — and enrollment expires. That asymmetry is why the most damaging credentialing failures happen to practices that finished credentialing years ago.

Updated 7 min read

On this page

Key takeaways

Enrollment is a standing obligation, not a project

Everything about how credentialing is staffed and discussed treats it as a project: a provider is hired, a process runs, the provider becomes billable, done. That framing is accurate for the first part and quietly wrong afterward, because the record it produced does not stay true on its own.

It fails in two different ways, and they need different defenses. It expires — on a cycle, triggered by time. And it breaks — on events, triggered by something changing. The first is a calendar problem and the second is a communication problem, and neither is the problem that onboarding trains a practice to solve.

The asymmetry is the whole article

The clock: revalidation

Revalidation is re-proving an enrollment that already exists. Medicare requires enrolled providers to revalidate on a cycle CMS publishes; commercial payers run their own re-credentialing on their own schedules. The provider has not necessarily changed anything — the trigger is time.

That is precisely why it is missed. Every other credentialing task is prompted by an event somebody noticed: a hire, a move, a new payer. Revalidation is prompted by a date, and dates do not walk into anyone's office. The notice arrives, goes to an inbox or an address that may be several reorganizations old, and nothing else about the day mentions it.

The consequence is out of proportion to the task

We do not publish the cycles or the notice periods, because they are not ours to publish: they are set by provider type, they differ between payers, and they change. The applicable cycle is whatever CMS or that payer currently publishes. What is durable is that a cycle exists at all — and that nothing in the ordinary run of a day will remind you of it.

The events: what breaks a working record

The second failure mode is a change somewhere in the practice that invalidates a record nobody was thinking about. These are ordinary business events, and none of them looks like a credentialing task at the moment it happens.

Ordinary changes that break enrollment, and why each one is missed.
Ordinary changes that break enrollment, and why each one is missed.
The changeWhat it breaksWhy nobody catches it
A new practice locationThe provider's recognition at that address — see Enrollment Pathways for why a site and a provider-at-a-site are separate facts.It is celebrated as growth. Nothing about opening a location feels like a payer question until the claims from it are refused.
A provider moves between groupsThe reassignment linking them, which Enrollment Pathways covers as its own failure mode.Both parties look enrolled, because both are. Only the link is missing, and nobody sees the absence of a filing.
A license or certification expiresThe credential the enrollment rests on. Renewing it with the board is not telling the payers.The provider renewed it. As far as they are concerned it is handled — and it is, with the board.
A name, tax ID, or ownership changeThe identity the payer's record is keyed to. The entity billing is no longer the entity enrolled.It is handled as a legal or finance event. Enrollment is downstream of a decision made in a different room.
A lapsed CAQH attestationPayers' ability to pull current data — which stalls credentialing that is in flight.Nothing announces it. The symptom appears somewhere else: an application that has stopped moving for a reason no one at the practice can see.

The third column is the pattern. Every one of these is somebody's success — a new site, a hire, a renewed license, a restructure — and in every case the enrollment consequence is invisible from where the decision was made. That is not carelessness; it is what happens when a dependency runs in one direction and the information runs in the other.

What actually defends against it

Neither failure is prevented by care, because neither is caused by carelessness. The clock is not missed because somebody was sloppy; it is missed because nothing prompted anybody. The defenses have to supply the prompt.

A diary, owned by a person
Revalidation cycles, re-credentialing dates, license and certification expiry — dated, with an owner. This is unglamorous and it is the entire defense against the clock, because the clock will never announce itself.
A list of what is live, per provider, per payer
The same list effective dates calls for, kept current rather than assembled once. A record that has lapsed should change what billing does, and it cannot if billing does not know.
Enrollment in the room for change decisions
Not a veto — a question. New location, group change, restructure: someone asks what it means for the payer records. The cost of asking is a minute; the cost of not asking is every claim from that site until it is found.
A denial pattern that triggers an enrollment check
The last line, and the one that catches what the others miss. When refusals cluster on one provider, one payer, one reason, check the record before working the claims — because the claims are not the problem.

The signal is the same as an enrollment gap

Common questions

Our physician has been here for years. Why did their claims suddenly stop paying?

Check whether the enrollment lapsed before checking anything about the claims. Enrollment expires on a cycle — Medicare requires revalidation on a schedule CMS publishes, commercial payers run their own re-credentialing — and the trigger is time rather than anything changing. A revalidation that is not completed can lead to deactivation, and a deactivated provider's claims stop paying regardless of the care, the coding, or the claim. Nobody did anything wrong. The record behind the claims lapsed.

We opened a second location. Do we need to do anything?

Almost certainly — and this is the change most often missed, because opening a location is celebrated as growth and nothing about it feels like a payer question until claims from the new address are refused. Enrollment Pathways explains why a site and a provider-at-a-site are separate facts on a payer's record. The operational rule is simply to ask what a new address means for each payer before the first patient is seen there.

The provider renewed their license. Isn't that enough?

It is enough for the board and not necessarily for the payers. The enrollment rests on the credential, and renewing it with the issuing body is not the same as the payers knowing. From the provider's point of view it is handled — and it is, with the board. What has to be tracked separately is whether the enrollment records that depend on it have been updated.

How often is revalidation required?

We do not publish the cycles, and the reason is that they are set by CMS and by each payer, differ by provider type, and change. A figure copied into an article is a number with a shelf life on a page that offers no expiry date — and this is a matter decided by dates. The applicable cycle is whatever CMS or the payer currently publishes for that provider type. What is durable is that a cycle exists, that missing it can deactivate an enrollment, and that nothing in daily operations will remind you of it.

Authoritative sources

Ready to improve your revenue cycle?

Explore our services and knowledge base to see how we can help.