The rejection taxonomy
Why credentialing applications get rejected.
After enough rescued files, you learn that seven reasons cover nearly every bounced application, and that none of them have anything to do with whether the clinician is any good. This page walks through all seven, what each one looks like from the payer’s side of the desk, and what it takes to keep them off your file.
Start with the math
What a bounce actually does to your calendar
The payer manuals we file against mostly state 45 to 90 days from a complete application to a credentialing decision, and the Wait Times Index shows each payer’s own figure. Those windows assume the file never leaves the queue. A rejected application does not rejoin that queue where it left off. It starts over, behind every file that arrived while yours was bouncing, and often on a fresh application form because payers version their paperwork. In practice, one rejection turns a two month enrollment into four or five months. Two rejections eats most of a year.
During that stretch the provider is either seeing patients the practice cannot bill in network, or sitting on a schedule that stays half empty because the panels have not opened. Either way the money is gone, and unlike a claim denial, there is no appeal that recovers it. The whole economic case for doing credentialing carefully sits in that gap, which is why everything below focuses on the first submission. It is the only one with no queue behind it.
The short list, before the detail
Credentialing applications get rejected for seven reasons: a CAQH attestation that expired during the payer’s review, legal name or TIN or address data that does not match across the W-9, CAQH, and the NPI registry, a document that expired between filing and review, an application filed to the wrong network or the wrong regional entity, work history gaps with no written explanation, a payer deficiency request nobody answered inside its window, and a failure at primary source verification such as a mistyped license number or an exclusion list match. Every one of them is administrative, and every one of them is preventable before the file goes out.
Read the letter carefully
Returned, rejected, denied: three different problems
Payers use these words precisely even when practices do not, and what you should do next depends on which one is on your letter.
Returned
The payer looked at the file, found something missing or inconsistent, and sent it back for correction without ruling on it. Usually the least damaging outcome, if someone answers quickly. Many payers hold your place in the queue for a returned file, but only inside a response window, and the window is short. Medicare gives 30 days on a development request and rejects the application outright when nobody answers.
Rejected
The payer closed the file without a decision. This is what happens when a returned file gets no answer, when an application lands in the wrong queue entirely, or when something basic fails at intake, an expired attestation, a signature page from an old form version, a missing W-9. A rejected file does not resume. Refiling means a new application and a new place at the back of the line.
Denied
The payer reviewed a complete file and said no. Network is full in your county, your specialty is not being added, something surfaced in verification that the committee would not pass. Denials are a different problem from everything else on this page. They get appealed or worked around with a different network strategy, and preparation alone does not prevent all of them. The other two outcomes, preparation prevents almost entirely.
The seven reasons
Why do credentialing files actually bounce?
Each one carries the stamp the file effectively comes back with, what it looks like in real life, and the check that keeps it off your application.
The CAQH attestation expired while the payer was reading
Here is the part nobody tells a new practice: most commercial payers never read the application you mailed them. They pull your file from CAQH, and a CAQH profile is only usable while its attestation is current, which lasts 120 days. So a practice files in week one, the payer's analyst opens the file in week seven, the attestation quietly died in week five, and the payer treats the entire profile as unverified. The application was fine the day it left. It was dead by the time anyone looked at it. Aetna and Humana both require CAQH ProView everywhere except Arkansas, per their own credentialing policies, and most other major commercial payers read from it too, so this one failure reaches most of a typical panel list.
We re-attest before filing anything that reads from CAQH, even when the current attestation has weeks left on it, and the next re-attestation goes on a calendar with a named owner so the profile stays alive through the payer's whole review, not just the day of filing.
The legal name, TIN, or address does not match across documents
Credentialing analysts spend their day comparing fields. Your application against your W-9. Your W-9 against CAQH. All of it against the NPI registry. The application says Mindful Health LLC, the W-9 says Mindful Health, LLC with a comma, NPPES still shows the office you moved out of last spring, and the group NPI's authorized official is a partner who left. None of those are errors a payer will fix for you, and no analyst calls to ask which version is right. The file goes back, and if it goes back to an inbox nobody watches, it becomes a rejection a month later.
One verified record feeds every application we file. Before anything goes out, the W-9, the CAQH profile, the NPI registry entry, and the payer form are reconciled to a single set of answers, down to punctuation in the legal name, because that is genuinely the level payers check at.
A document expired between gathering and review
A malpractice certificate with 40 days left looks perfectly fine on filing day. Then the payer's stated review window is 60 days, the analyst reaches your file at day 52, and the certificate of insurance in it expired ten days ago. Same story with a license renewing next month or a DEA registration near its date. The application was complete when it left your desk and incomplete when it was read, and the payer rules on what it reads. Practices lose weeks this way while feeling like they did everything right, because on the day they filed, they had.
Every expirable in the file gets checked against the payer's own stated review window before we submit, using the same published timelines we maintain in the Wait Times Index. When the math does not clear, we renew the document first and file second.
The application went to the wrong network or the wrong entity
Some applications fail without ever being read, because they were never in the right queue. A therapist files with UnitedHealthcare's medical network when behavioral health belongs to Optum's separate Provider Express process. A Texas practice mails its TRICARE file to the West region contractor, who stopped owning Texas when the regions were redrawn in 2025, along with Arkansas, Illinois, Louisiana, Oklahoma, and Wisconsin. An ABA clinic goes down the standard individual path when TRICARE requires a corporate application for autism care providers. These files do not come back with a correction letter. They sit, and the practice waits on a decision that was never going to arrive.
Every payer we file runs on a playbook checked against that payer's own provider manual, including which entity actually credentials your specialty and which regional contractor owns your state this year. The right door is a fact we look up, not an assumption we inherit.
Work history gaps with no explanation attached
Most payers want a continuous work history, commonly five years of it, and their credentialing committees are trained to stop at any gap of a few months or longer. Maternity leave, a cross-country move, a stretch of caregiving, six months building a private practice that did not appear on the CV because it felt too small to list. All ordinary. All fine once explained. But a committee that finds an unexplained gap does not assume the innocent version; it sends the file back with questions, and now a routine application has become a correspondence cycle with weeks between each round.
We reconcile the work history at intake, before any payer sees it, and attach a short written explanation to every gap. Committees accept explained gaps as a matter of routine. What they do not accept is silence, so we never file any.
A deficiency request nobody answered in time
When a payer wants corrections or missing items, it sends a request to whatever correspondence address is on file, and starts a clock. Medicare's is explicit: 30 days, and if the contractor hears nothing, the application is rejected, not paused. Commercial payers run the same play with less published grace. The dangerous part is where these letters land: an old office address, the inbox of a manager who left, a fax number from three years ago. The practice believes the application is processing. The payer already closed it. Months can pass before anyone discovers the difference.
Every open application we run has a named owner watching for payer correspondence, and our follow-up cadence means we are calling the payer on a schedule anyway, so a request that went astray gets discovered in days instead of months. Responses go back inside the window with exactly what was asked for.
Something failed primary source verification
Payers do not take your paperwork's word for anything. Licenses get checked with the state board, board certifications with the certifying body, education with the school, and every name runs against the OIG's federal exclusion list, which held more than 83,000 entries as of August 2026, plus the state lists that never fully sync with it. A license number with two digits transposed, a board certification listed as current when it lapsed in December, a common name that matches an exclusion entry and needs to be cleared. Some of these are typos and some are real problems, and until someone resolves them, the payer treats them identically: the file stops.
We run the payer's checks before the payer does. Identity against the NPI registry, license numbers at the source, exclusion screening across the whole roster monthly, so a transposed digit gets caught at our desk instead of at the committee's.
Payer specific statements on this page come from our verified payer playbooks, each checked against that payer’s own manuals and policies. Medicare rules checked against 42 CFR part 424. Exclusion figures from the OIG’s List of Excluded Individuals and Entities as of August 2026. Last verified August 2026. Next scheduled review November 2026. Reviewed by the Go Credentialing operations team.
Already bounced?
The recovery order, when it already happened
A bounced file is recoverable. Most of the damage after a rejection comes from refiling fast instead of refiling right, so the order below matters more than the speed.
Get the reason in writing
Call the payer and get the specific rejection reason, not the category. A rejection letter usually states the shortest version of a longer list, and refiling after fixing only the stated item earns a second bounce for the item they did not mention. Ask the representative to read every flag on the file, and write down the reference number for the call.
Fix the record, not the form
If the file bounced on a mismatch, correcting it on the application alone leaves the same wrong answer sitting in CAQH or NPPES, waiting to bounce the next payer too. Fix the source: update the registry, correct CAQH, re-attest, get a corrected W-9 signed. One clean record ends the problem everywhere at once.
Re-check every expirable against the new window
The refiled application starts a new review clock. The malpractice certificate, license, and DEA registration that cleared the old window may not clear the new one. Run the dates again against the payer's stated timeline before refiling, and renew first where the math is close.
Refile complete and calendar the follow-up
Refile through the payer's current process, confirm receipt with a reference number, and put follow-up calls on a schedule from day one. A file that bounced once has already proven that waiting quietly does not work with this payer.
Go one level deeper
The CAQH guide
The 120 day attestation cycle and the setup that prevents the most common bounce on this page.
Read itThe Wait Times Index
Every payer's stated queue with verification dates, so you know exactly what a restart costs with your payers.
Read itPayer playbooks
The per payer rules, including which entity credentials your specialty and where each payer's files stall.
Read itQuestions
Rejections, answered
What is the difference between a rejection and a denial?
A rejection is administrative. The file was incomplete, inconsistent, stale, or sitting in the wrong queue, and the payer closed it without ever deciding whether to let you in the network. A denial is that decision going against you after a complete review, usually on network need or something surfacing in verification. Rejections are almost entirely preventable with preparation. Denials need an appeal or a different network strategy, and the per payer playbooks cover how each payer handles both.
What does one rejection actually cost?
Count it in queue time. The payer manuals we file against mostly state 45 to 90 days from a complete application to a decision, and a rejected file goes to the back of a new queue rather than resuming in the old one. So one bounce commonly turns a two month enrollment into four or five months, during which the provider either sees patients the practice cannot bill in network or does not see them at all. For a clinician with ordinary volume, that stretch is usually tens of thousands of dollars. A second bounce roughly doubles it.
The payer says my application is complete. Am I safe?
Safer than before, but the file still needs watching. Complete means the payer has everything it asked for on that date. Verification, committee review, and contract loading still follow, documents can expire during that stretch, and a CAQH attestation can lapse mid-review and undo the completeness finding. We chase every application on a schedule until the effective date is in writing, because the acknowledgment letter is where several of the failures on this page begin, not end.
My application was rejected. What should I do first?
Call the payer and get every reason on the file, in specifics, before touching the application. Then fix the underlying record rather than just the form, re-check your expirable documents against the new review window, and refile with follow-up scheduled from day one. The recovery section above walks through each step. The one thing not to do is refile the same file quickly, because the same file gets the same result with a later date on it.
Can you rescue an application another company filed?
Yes, and a meaningful share of our work starts exactly there: files that sat for months, applications that went to a network that was never going to answer, work histories that came back with committee questions nobody addressed. We pull the actual status from the payer, fix the record once, and refile clean. Send what you have and we will tell you honestly whether yours is a fix or a restart, and what either one costs.
Filed clean the first time, or rescued if it already bounced.
Send your payers and what happened so far. You get an honest read on whether it is a fix or a restart, and a written plan either way.