A provider’s ability to get paid by a payer does not live in your software. It lives in credentialing, the provider’s standing with that payer, and no setting in any system fixes a gap in it. Across more than one location it multiplies, because a provider credentialed and enrolled at one location is not automatically either at another. This is what credentialing and enrollment actually take across locations, why a system switch or a new location is exactly where the gaps surface, and what one costs when it does. It sits inside the full picture in how to prepare for an AdvancedMD data migration. This is the credentialing job, in depth.
Credentialing is not a setting in the system
You can set up a perfect provider record in the new system, with the correct identifiers and every setting right, and still have that provider’s claims deny, because the thing that lets a provider bill a payer is not in the software at all. It is credentialing: the payer’s approval of that provider to be paid under a given practice, at a given location, from a given date. The record in the system tells the software how to format the claim. Credentialing tells the payer whether to pay it. Get the record perfect and the credentialing wrong, and you have a clean claim that denies every time.
Three different things people run together
Three separate things get collapsed into one, and the differences are where the trouble hides. The provider record is the setup inside the system, part of configuration, covered in configuring a new system for a day-one go-live. Credentialing is the payer’s approval of the provider to be paid, which lives outside the software. And electronic enrollment is connecting the practice to the payer’s channels so claims and remittances move, which is its own outside process, covered in payer and clearinghouse enrollment when you switch systems. You need all three, and having one does not give you the others. A provider can be credentialed but not connected electronically, or set up in the system but not credentialed, and each gap fails in its own way.
Tied to the practice, the location, and an effective date
Credentialing is not a property of the provider alone. It attaches to a specific provider, under a specific practice or group, at a specific location, effective from a specific date. Every one of those matters. A provider credentialed under one group is not credentialed under another. A provider credentialed at one location is not automatically credentialed at a second. And the effective date gates when claims can go out, because a claim for a date of service before the credentialing took effect is a claim the payer will not pay. Enrolling a provider with a payer commonly runs weeks to months, on the payer’s schedule, which is why this cannot be left to the end.
A provider is not automatically enrolled at a new location
This is the trap that catches groups with more than one location, and the one a move most often exposes. When a provider starts seeing patients at a new location, or the group opens or acquires one, the provider’s credentialing and enrollment do not follow automatically. Each has to be established for that provider, at that location, with each payer, on each payer’s timeline. A group that assumes a provider already good at location A can simply start billing at location B discovers, weeks in, that the claims from B are denying while the ones from A are fine. Across a roster of providers and a list of payers, that is not one gap. It is a grid of them, and the grid has to be checked cell by cell before go-live.
Why a switch or a new location exposes the gaps
Credentialing gaps tend to sit quietly until something makes the practice look. A system migration is one of those moments, and so is opening a location. The move forces someone to account for who is enrolled where, with which payer, effective when, and that accounting turns up assumptions no one had checked in years: a provider everyone believed was enrolled who never was at this location, an effective date that is wrong, a payer that was never set up for a provider who has been seeing its patients. None of these are created by the migration. They were already there. The migration is just the first time anyone looked.
Billing under a different provider than delivered the care
Many practices deliver care with one provider and bill it under another, an assistant or an advanced-practice provider working under a supervising or billing physician, and how that claim goes out depends entirely on the payer. Some want the claim under the supervisor, some under the rendering provider with the supervisor attached, and some will not pay the rendering provider at all. That relationship is a piece of setup that has to match each payer’s rules, provider by provider and payer by payer. Get it wrong and you either bill in a way the payer rejects, or, worse, bill in a way the payer pays and later claws back after a review. The clawback is the worse outcome, because it feels like income until it is reversed, sometimes long after it was spent.
What a credentialing gap costs
A credentialing gap has a simple, expensive signature: every claim for that provider, at that location, with that payer, denies, no matter how clean the configuration is. And because the cause lives outside the software, no amount of fixing the system resolves it. What it looks like on the ground is a provider working full days whose work is not getting paid, sometimes for weeks, while the enrollment is sorted out. The revenue is not lost the way a denied claim is lost, since credentialing can often be established and claims refiled, but it is delayed, and the delay lands during the exact stretch when a practice can least afford a cash gap it did not plan for.
How to handle credentialing across locations
Treat credentialing as its own workstream, on the same clock as the electronic enrollments, because it runs just as slow. Map the grid: every provider, at every location, with every payer, and confirm the status and effective date of each cell rather than assuming. Start early, since enrolling a provider with a payer runs weeks to months and cannot be compressed at the end. Match the supervised and billing-provider rules to each payer, so care delivered by one and billed under another goes out the way that payer wants it. And do not set a go-live date that assumes credentialing is done until the grid confirms it, because a provider who cannot bill on go-live morning is a provider working for free until the payer catches up.
Before go-live
On the credentialing side, these should be true.
- Every provider is confirmed credentialed and enrolled with each payer, at each location, with the effective dates right.
- The grid of provider, location, and payer has been checked cell by cell, not assumed from prior enrollment elsewhere.
- Where care is delivered by one provider and billed under another, the rules are matched payer by payer.
- Credentialing is tracked as its own workstream, started early, on the same clock as the electronic enrollments.
- No go-live date assumes credentialing is complete until the grid confirms it.
If the grid is not confirmed, some provider’s claims will deny on go-live morning for a reason no setup can fix. Credentialing is what turns a provider who is set up in the system into a provider who actually gets paid.
Common questions
Does provider credentialing transfer when you switch systems?
No. Credentialing is a provider’s standing with a payer, which lives outside the software, tied to the practice, the location, and an effective date. Changing systems does not move it, and a perfect provider record in the new system does not create it. It has to be confirmed separately.
Is credentialing the same as setting up a provider in the system?
No. The provider record in the system tells the software how to format a claim. Credentialing is the payer’s approval of that provider to be paid. You can have the record perfect and the credentialing missing, and the claim will be clean and still deny every time.
Is a provider enrolled at one location automatically enrolled at another?
No, and this is the trap for multi-location groups. Credentialing and enrollment attach to a specific provider, at a specific location, with each payer. A provider good at one location is not automatically good at a second. Each cell of that grid has to be established and confirmed on its own.
Why do credentialing gaps surface during a migration?
Because a migration forces someone to account for who is enrolled where, with which payer, effective when. That accounting turns up assumptions no one had checked in years. The gaps were already there. The migration is simply the first time anyone looked closely enough to find them.
How long does provider enrollment with a payer take?
Commonly weeks to months, on the payer’s schedule, not yours. It cannot be compressed at the end of a project, which is why credentialing has to run as its own workstream started early, on the same clock as the electronic enrollments, rather than assumed to be done by go-live.
What happens if a provider is not credentialed at go-live?
Every claim for that provider, at that location, with that payer, denies, no matter how clean the system setup is, because the cause is outside the software. The provider works full days unpaid until enrollment is sorted, and the cash gap lands when the practice can least afford it.
What is the difference between credentialing and electronic enrollment?
Credentialing is the payer’s approval of a provider to be paid. Electronic enrollment connects the practice to the payer’s channels so claims and remittances move. They are separate outside processes, and having one does not give you the other. A provider can be credentialed but not connected, or connected but not credentialed.
How is billing handled when one provider supervises another?
It depends on the payer. Some want the claim under the supervisor, some under the rendering provider with the supervisor attached, and some will not pay the rendering provider at all. The setup has to match each payer’s rules, or the claim rejects, or pays and gets clawed back later.
What is a clawback, and why is it worse than a rejection?
A clawback is when a payer pays a claim and later takes the money back after a review. It is worse than a rejection because it feels like income until it is reversed, sometimes long after it was spent, so the practice has already counted and used money it has to return.
How do I manage credentialing across multiple locations?
Map a grid of every provider, at every location, with every payer, and confirm the status and effective date of each cell rather than assuming. Start early, match the supervised billing rules per payer, and do not set a go-live date that assumes credentialing is done until the grid confirms it.
Can no amount of system configuration fix a credentialing gap?
Correct. The provider record can be perfect and the claims still deny, because credentialing lives with the payer, not in the software. Fixing the system does nothing for a gap outside it. The only fix is establishing the credentialing itself, which takes the payer’s time, not yours.
Where this leaves you
Credentialing is the piece of a migration that no setup can rescue, because it lives with the payer and not in your software. Map the grid, confirm every provider at every location with every payer, and start it as early as the electronic enrollments, and your providers get paid from day one instead of working while the payer catches up.