What Is the B7 Denial Code?

The official X12 definition of CARC B7 is: 'This provider was not certified/eligible to be paid for this procedure/service on this date of service.' Every word of that definition matters, and most B7 confusion comes from skipping over the last five words.

'This provider' — the denial is about the rendering (or billing) provider's status, not the patient, the diagnosis, or the procedure. The clinical service may have been entirely appropriate.

'not certified/eligible to be paid' — on the payer's enrollment and credentialing files, the provider was not in an active, payable status for the service billed. This covers a provider who was never enrolled, one whose enrollment had not yet taken effect, one whose enrollment lapsed or was deactivated, one whose revalidation was overdue, and one whose specialty/taxonomy on file does not permit that service.

'on this date of service' — B7 is a point-in-time test. The payer compares the date of service on the claim against the provider's enrollment effective and end dates. A provider who is fully active today can still get B7 on a claim for a service rendered during a window when their record had a gap. This is why you can fix the enrollment today and still need to rebill the back-dated claims.

The Group Code matters. B7 almost always travels with Group Code CO (Contractual Obligation), meaning the adjustment is the provider's responsibility under the payer contract and cannot be balance-billed to the patient. You cannot legitimately send a patient a bill because your own enrollment record had a gap. In our enrollment audits we typically see B7 spike right after a provider joins a group, right after a TIN or location change, and in the months around a missed CMS revalidation deadline — three predictable moments when the payer's record and reality fall out of sync.

B7 is informational about the provider's payable status, not about the claim's construction. A claim can be coded perfectly, documented perfectly, and clinically necessary, and still deny B7 because the rendering provider's record had an enrollment or credentialing gap on the date of service.

B7 has a small set of recurring root causes, and identifying which one applies tells you exactly which team owns the fix — enrollment, credentialing, or coding.

1. Enrollment effective-date gap. The provider is enrolled now, but the effective date on file is later than the date of service — common for new hires and new graduates who started seeing patients before the payer's enrollment took effect. For Medicare, an approved enrollment can retroactively cover up to 30 days before the application receipt date (longer in limited circumstances), so claims rendered before that retroactive window deny B7. This ties directly to gaps in provider enrollment.
2. Lapsed, incomplete, or never-completed credentialing. Commercial payers will not load a provider as payable until credentialing is complete and the contract is loaded. If a provider began seeing that payer's patients before credentialing finished — or if a re-credentialing cycle lapsed — claims deny B7. Robust provider credentialing prevents this.
3. Overdue Medicare revalidation. CMS requires providers and suppliers to revalidate enrollment periodically (generally every five years; every three years for DMEPOS). Miss the revalidation due date and the MAC can place a hold or deactivate the enrollment, denying claims as B7 until revalidation is processed.
4. Taxonomy / specialty mismatch. The provider's specialty or taxonomy code on file does not authorize the service billed — for example a service restricted to a specific specialty, or a claim submitted with a taxonomy that does not match the enrolled specialty. (This overlaps with CO-8; see the comparison table below.)
5. Deactivation, sanction, or exclusion. The provider was deactivated for non-response to a payer request, voluntarily/involuntarily termed from the network, or — most seriously — placed on the OIG LEIE exclusion list or a state Medicaid exclusion list. Excluded-provider claims are not payable and must not be resubmitted as if they were a clerical error.
6. Wrong provider identifier on the claim. The rendering NPI, group NPI, or PTAN on the claim does not match the enrolled provider/location combination — for instance billing under a group the provider is not linked to, or a location not on the enrollment. The provider is enrolled; the claim just pointed at the wrong record.

When the same provider's claims all deny B7 at once, the cause is upstream (a record gap), not claim-by-claim — fix the enrollment record once and rebill the affected claims as a batch.

Because B7 is an enrollment/credentialing denial, the fix lives in the provider's payer record, not in the claim's CPT/ICD-10 fields. Work it in this order.

1. Read the paired RARC and identify the rendering provider and date of service. The 835 may attach a RARC (for example N570 'Missing/incomplete/invalid credentialing data' or an N-code naming the identifier) that narrows the cause. Note which provider and which DOS triggered the denial.
2. Verify the provider's enrollment effective dates at the source. For Medicare, check the enrollment record and effective/revalidation dates in PECOS (and the PTAN/effective date with the MAC). For commercial payers, confirm credentialing status, contract load date, and the provider's link to the billing TIN/group with provider services. Compare those effective dates against the claim's date of service.
3. Pinpoint the gap type. Effective-date gap, lapsed credentialing, overdue revalidation, taxonomy mismatch, deactivation/exclusion, or wrong identifier — each routes to a different fix. Confirm the provider is not on the OIG LEIE before doing anything else; if excluded, stop and escalate (those claims are not payable).
4. Correct the enrollment record. Submit or complete the enrollment/revalidation, request the correct retroactive effective date where the payer's rules allow it, link the provider to the correct group/TIN/location, or correct the taxonomy on file. This is the load-bearing step — until the record is right, every rebill denies again.
5. Rebill the affected claims once the record is corrected. After the payer confirms the corrected effective dates or revalidation, resubmit the held/denied claims. For Medicare, claims for dates inside the corrected effective window can be reopened or resubmitted; for commercial payers, follow the corrected-claim/reconsideration path. Rebilling before the record is fixed just regenerates the B7.
6. Protect timely filing while you wait. Enrollment fixes can take weeks. Document the original timely submission, hold (do not abandon) the affected claims, and if the enrollment correction pushes you past the timely-filing window, appeal for a timely-filing exception citing the enrollment delay as the cause (see CARC 29 timely-filing guidance).
7. Close the gap upstream. If a revalidation lapse or a missing credentialing step caused the B7, add the provider's revalidation date to a tracked calendar and gate new-provider scheduling on confirmed payable status. End-to-end denial management services can own the categorization, the enrollment correction, the batch rebill, and the prevention loop.

Three provider-side denials get confused constantly because they all sound like 'the provider can't bill this.' They are distinct, and the fix differs. Read the exact code on your 835 before routing the denial.

Bottom line: B7 is about whether the provider was enrolled and payable at all on that date; CO-185 is about whether the specific rendering provider is eligible to perform that specific service; CO-8 is about whether the code matches the provider's specialty/taxonomy. They overlap at the edges — a taxonomy problem can surface as B7, CO-185, or CO-8 depending on the payer's edit — so always confirm enrollment effective dates first, then eligibility/scope, then taxonomy.

Like most CARCs, B7 can travel with a Remittance Advice Remark Code (RARC) that narrows the cause. Read the RARC exactly as printed on your 835 — payers do not always attach the same one, and the RARC is what routes the denial to the right fix.

If no RARC is attached, default to the enrollment investigation: pull PECOS (or the payer credentialing record), compare effective dates to the date of service, and check revalidation status. The absence of a RARC does not change that B7 is an enrollment/credentialing denial — it just means you have to find the specific gap yourself.

B7 shares the worklist with adjacent provider- and enrollment-related codes. Knowing which is which prevents misrouting an enrollment denial to the coding queue.

CO-185 — Rendering provider not eligible to perform the service. The closest cousin to B7. Where B7 says the provider was not enrolled/payable at all on the DOS, CO-185 says the specific rendering provider is not eligible for the specific service. Confirm the rendering provider and their scope.

CO-8 — Procedure inconsistent with provider type/specialty (taxonomy). A taxonomy mismatch. Frequently overlaps with B7 when the underlying issue is that the enrolled specialty does not match the billed code.

CO-16 — Claim/service lacks information. When the missing element a B7-adjacent denial flags is specifically a provider identifier or taxonomy, the payer may route it to CO-16 with an identifier RARC instead. Read the RARC and correct the named identifier. See our CO-16 explainer.

CO-29 — Timely filing limit exceeded. The classic downstream effect of a B7 cluster: enrollment fixes drag, and by the time the record is corrected the claims have aged past the filing window. Protect timely filing while the enrollment is being corrected. See our timely-filing guide.

CO-18 — Exact duplicate claim/service. Resubmitting B7 claims as fresh originals after fixing enrollment — instead of through the corrected-claim/reopening path — can trigger a duplicate denial. Use the payer's reopening or corrected-claim process.

The discipline that keeps a B7 worklist fast is categorizing by provider and gap type at intake, so all of one provider's B7 claims are corrected and rebilled together once the record is fixed. For the broader code map, see the CARC denial codes list.

The B7 logic is identical across payers — the provider was not payable on the date of service — but the triggers and the correction mechanics differ.

Medicare (MACs). Medicare B7s cluster around enrollment effective dates and revalidation. An approved Medicare enrollment grants limited retroactive billing (generally up to 30 days before the application receipt date, longer only in specific circumstances), so claims for services before that window deny B7. Overdue revalidation is the other big driver: miss the MAC's revalidation due date and the enrollment can be deactivated, denying everything as B7 until revalidation processes. Verify the PTAN, effective date, and revalidation status with the MAC, correct the enrollment in PECOS, then reopen or resubmit the affected claims.

Medicaid (state programs and MCOs). Medicaid B7s skew toward incomplete or lapsed state enrollment and MCO-specific credentialing. A provider can be enrolled with the state Medicaid program yet not loaded by a specific Medicaid MCO, producing B7 from that MCO while fee-for-service pays. Each state and each MCO has its own enrollment portal, revalidation cadence, and corrected-claim process — verify the specific plan's requirements. Confirm both state enrollment and MCO loading before rebilling.

Commercial payers. Commercial B7s most often trace to credentialing that was never completed, a contract not yet loaded, or a provider not linked to the billing TIN/group. Many commercial payers will not back-date credentialing, which makes pre-service confirmation of payable status the only reliable prevention. Submit corrected claims or reconsiderations through the payer's process once the provider is loaded; do not resubmit as new originals.

Across all three, the universal accelerant is gating: do not let a new or changed provider's claims go out until enrollment and credentialing are confirmed payable for each payer. A few weeks of held claims is far cheaper than a quarter of B7 rework and timely-filing write-offs.

Most B7s are corrected by fixing the enrollment record and rebilling, not by appealing — there is nothing to dispute when the record genuinely had a gap. But two B7 scenarios are legitimately appealable: (1) the provider was enrolled and payable on the date of service and the payer's edit fired in error, and (2) the enrollment correction pushed otherwise-clean claims past the timely-filing window.

Before you appeal, confirm you have proof: the PECOS or payer enrollment record showing the effective date covered the date of service, the credentialing approval/contract load date, and (for timely-filing exceptions) proof of the original timely submission. Without that documentation, the appeal will fail and you should be correcting the record instead.

Copy-paste appeal paragraph (provider was payable on the DOS):

'We are requesting reconsideration of the B7 denial on claim [CLAIM #] for [PATIENT NAME], date of service [DOS], rendering provider [PROVIDER NAME, NPI]. The denial states the provider was not certified/eligible to be paid for this service on this date of service. Enclosed documentation confirms that the rendering provider was actively enrolled, credentialed, and contracted with [PAYER] for [SERVICE] on [DOS]: see the enrollment effective date of [EFFECTIVE DATE] (PECOS/payer record attached), which precedes the date of service, and the credentialing/contract approval dated [DATE]. Because the provider was payable on the date of service, the B7 adjustment was applied in error. We respectfully request that the claim be reprocessed and paid.'

For a timely-filing exception caused by an enrollment delay, add: 'The original claim was submitted timely on [DATE] (proof attached). Any delay in resubmission resulted solely from [PAYER]'s enrollment/credentialing processing, which was outside the provider's control. We request a timely-filing exception and reprocessing.'

For reusable appeal structure across denial types, see our medical billing appeal letter template.