How Long Does Provider Credentialing Take? Timelines by Payer and How to Shorten Them

The honest answer

It depends on the payer, the state and the state of your application. The question practices really mean is “when can I start billing?”, and the answer is the payer’s effective date, which can be weeks after the approval letter. Here is how the time breaks down for each payer type.

Medicare

A clean PECOS application is often processed within one to two months, and the Medicare Administrative Contractor can grant an effective date up to thirty days before the application was received (ninety days in some circumstances), which means a well-timed Medicare application rarely costs you revenue. Paper CMS-855 forms are slower than PECOS. Development requests (the MAC asking for a correction or a document) restart part of the clock and come with a deadline; miss it and the application is rejected and must be resubmitted.

Medicaid

Each state runs its own program and most states run managed care plans on top of it. New York, for example, enrolls providers through eMedNY and then each Medicaid managed care organization credentials the provider separately. Fee-for-service enrollment and MCO credentialing run on different clocks, and you need both to be paid for a managed-care patient. Budget two to four months and more for plans that credential on a monthly committee cycle.

Commercial payers

Most commercial plans pull your CAQH profile, run primary source verification, and present the file to a credentialing committee that meets on a schedule. Sixty to one hundred twenty days from a complete application is typical; some plans are faster, some are slower, and all are slower when the panel is full or the application needs a correction. After approval comes the participation agreement, and the effective date is usually tied to the contract, not the approval letter.

Where the time actually goes

1. Before submission. Gathering documents, building CAQH, confirming the group is enrolled. Weeks, if nobody owns it.
2. Payer intake. The payer logs the application and checks it for completeness. Incomplete applications are returned, not held.
3. Primary source verification. Licenses, education, board status, malpractice history, OIG and SAM exclusion checks. Mostly automated, but a mismatch (a maiden name on a diploma, a lapsed DEA) pauses it.
4. Committee. Monthly or biweekly. Miss the cut-off for one meeting and the file waits for the next.
5. Contracting and loading. Signature, countersignature, provider ID issued, loaded into the claims system. Claims submitted before loading finishes deny as “provider not found” even though you are approved.

Five things that shorten it

• Start before the start date. Begin ninety to one hundred twenty days before a provider’s first patient day. Most practices start the week they arrive.
• Submit complete. One correction cycle costs more time than any other single factor. Use a checklist and have a second person review the application.
• Keep CAQH attested. If the profile is stale, the payer waits for you without telling you.
• Follow up on a cadence. Every open application, every few days, with the confirmation number in hand. Applications that are chased move; applications that are not, do not.
• Ask for retroactive effective dates. Some payers grant them when asked at approval; almost none offer.

What you can do while you wait

See patients under a supervising or already-enrolled provider where your specialty and state allow it, verify eligibility so you know which patients belong to payers you are not yet in network with, and collect from patients on a self-pay basis where appropriate. Do not hold claims indefinitely: every payer has a timely filing limit, and an application approved on day one hundred twenty does not extend it.

How Core MB tracks it

Every application we file is visible in the client portal with its stage, the payer’s last response and the next follow-up date, so the question “where are we with Aetna?” has an answer without a phone call. That is the whole reason we built the software we run our credentialing service on.