Enrollment-Related Denials and Their Root Causes

When to use this playbook

• Claims are denying with CO-B7, CO-16 plus provider-related remark codes, CO-109, CO-197, CARC 170, 171, 183, 184, or 185.
• The payer says a provider is in-network, but claims still deny for provider eligibility or enrollment.
• Denied claims cluster around a new provider, location, TIN, acquisition, revalidation, or payer effective date.
• Patients are being told the practice is out of network even though the organization has a participation agreement.
• Your billing and credentialing teams are resubmitting claims without knowing whether the claim, authorization, or payer provider record is wrong.
• A material backlog has accumulated and timely-filing deadlines now affect what can be recovered.

What success looks like

Success means every denial cluster has a named root cause, supporting payer evidence, a recovery route, and an owner. Claims should move only after the provider’s eligibility, group affiliation, effective date, location, TIN, taxonomy, authorization data, and submitted claim data agree.

The denial code starts the investigation; it does not finish it. An electronic remittance advice combines a group code, a Claim Adjustment Reason Code, and sometimes a Remittance Advice Remark Code. CO identifies a contractual obligation assigned to the provider, while the CARC and RARC explain the adjustment in more detail. CMS remittance advice guidance

Map the denial code to the enrollment defect

CO-B7 means the provider was not certified or eligible to be paid for the procedure or service on the date of service. Because B7 addresses provider eligibility, the first investigation should test the effective date, provider type, taxonomy, payer product, group affiliation, and service location before anyone changes the diagnosis or procedure code.

CO-16 requires the accompanying remark code to identify the missing or conflicting provider data. CO-109 and CO-197 need separate treatment: 109 is usually a routing or payer-product problem, while 197 is an authorization denial that belongs in an enrollment review only when the authorization and claim identify different providers, entities, locations, or products.

Step 1: Stop blind resubmissions and build the denial file

Action: Export every affected claim into one working file. Include the payer and product, patient, date of service, claim number, billed amount, CARC, every RARC, original submission date, rendering NPI, billing NPI, TIN, taxonomy, place of service, service location, authorization number where relevant, and current status.

Collect both the 277CA acknowledgment and the 835 remittance. A 277CA identifies claims rejected before adjudication, while the 835 reports the payer’s adjudication and adjustment decision. CMS electronic-claim glossary

Triage order for a six-figure enrollment-denial backlog

Expected outcome: One sortable dataset that reveals whether denials cluster around a provider, payer product, TIN, location, date range, authorization configuration, or claim configuration.

Planning estimate: Two to four hours for an initial backlog extract, plus additional time if remittance data must be retrieved from multiple clearinghouses.

Gotchas: Billing-system descriptions often truncate or generalize the payer’s full message. Retrieve the raw ERA when possible. Do not assume a rejected transmission preserved timely filing merely because the practice attempted to send it.

Step 2: Classify the root cause at the provider-payer-date level

Action: For each denial cluster, compare the exact claim identity with the payer’s enrollment identity on the date of service. The investigation should end in one of four primary buckets.

Expected outcome: Each cluster has one primary root cause rather than a broad label such as “credentialing denial.”

Planning estimate: Thirty to sixty minutes per payer-provider cluster once enrollment letters, rosters, and claim files are available.

Gotchas: A participation agreement proves that a contractual relationship exists; it does not prove that every provider, product, TIN, and location was loaded correctly into claims adjudication. Obtain the current payer roster or portal record when available.

Step 3: Verify the submitted claim before escalating the payer record

Action: Inspect representative 837P files rather than relying only on the practice-management system’s display. Compare the submitted values with the payer enrollment record:

• Billing provider name and organizational NPI
• Billing provider TIN or EIN
• Rendering provider Type 1 NPI
• Rendering and billing taxonomy
• Service-facility name, address, and NPI
• Place of service
• Referring, ordering, or supervising provider NPI when required

On professional Medicare claims, the billing-provider TIN is reported in Loop 2010AA REF or Item 25, while service-facility information is reported through the applicable service-location loop or Item 32. CMS-1500 and 837P claim guidance Commercial claims likewise require the billing provider’s NPI and TIN, with individual NPIs used for rendering and service-facility providers. Aetna NPI transaction guidance

Expected outcome: You can demonstrate either that the claim carried incorrect data or that a correctly constructed claim conflicts with the payer’s provider record.

Planning estimate: Fifteen to thirty minutes per representative claim format, followed by a batch query for other claims sharing the same values.

Gotchas: Do not replace an identifier merely because another combination pays. The replacement must reflect the entity, provider, and location that actually rendered and billed the service.

Step 4: Force a specific payer determination

Action: Open one payer case for each consistent root-cause cluster. Ask the payer to confirm each point separately:

1. Was the rendering provider active for the exact product and dates of service?
2. Was the provider affiliated with the billed group NPI and TIN?
3. What effective date appears in the claims-adjudication system?
4. Was the service location active under that TIN?
5. Did the payer recognize the submitted taxonomy and provider type?
6. Did any authorization identify a different provider, entity, product, or location than the claim?
7. Will the payer mass-reprocess the affected claims after correction, or must the practice submit corrected claims or disputes?

Large payers maintain separate provider-demographic and roster workflows because NPI, TIN, taxonomy, location, and group affiliations feed claims processing. UnitedHealthcare requires valid billing and rendering NPIs and relevant taxonomy codes and provides separate demographic and roster-update tools. 2026 UnitedHealthcare Administrative Guide

When patients see the practice as out of network despite a contract

A signed contract, a claims-adjudication record, and a member-facing directory can hold different statuses. Verify the exact product and network rather than the carrier name alone, then compare the directory listing with the individual NPI, group NPI, TIN, specialty, address, telephone number, and digital contact information submitted to the payer. Open a provider-data or directory correction case, preserve screenshots and confirmation numbers, and require confirmation in both the provider portal and the member-facing directory. If claims are also denying, open a separate claims or enrollment case because a directory correction does not necessarily repair adjudication.

Federal law requires plans and issuers to verify and update provider directory information at least every 90 days, update the directory database within two business days after receiving qualifying provider information, and respond to telephone network-status requests within one business day through written electronic or print communication. 42 U.S.C. 300gg-115

Providers and facilities must maintain processes for timely directory updates when network agreements begin or end, when material information changes, and when a plan requests an update. If a patient pays cost-sharing above the in-network amount in circumstances protected by the federal directory rules, the provider must refund the excess plus interest. The federal provisions cited here do not set one universal fixed fine for every inaccurate listing; state directory laws and payer contracts can add requirements and penalties. 42 U.S.C. 300gg-139

Expected outcome: A payer reference number, named correction, confirmed effective date, affected claim population, directory status where relevant, and written reprocessing or resubmission instructions.

Planning estimate: One to two hours to assemble and submit a well-documented case. Payer correction time is outside the practice’s control, so assign a follow-up date rather than leaving the case open-ended.

Gotchas: “The provider is participating” is not a complete answer. Participation must be confirmed against the exact product, group, TIN, location, affiliation, directory record, and date of service involved.

Step 5: Segment the backlog by recovery posture

Action: Add the payer’s timely-filing and dispute deadlines to every claim. Work claims nearest to a deadline first, even if higher-value claims exist elsewhere in the backlog.

Medicare fee-for-service claims generally must reach the correct Medicare Administrative Contractor within one calendar year of the date of service. A denial solely for late filing is not an appealable initial determination. CMS timely-filing guidance

Medicare redetermination requests generally have a 120-day deadline from receipt of the initial determination, while minor errors and omissions follow reopening or correction procedures rather than the ordinary appeal path. CMS Medicare redetermination guidance

For specified Medicare provider and supplier types, the effective date is generally the later of the approved application’s filing date or the date services began at the new location. Current federal rules permit up to 30 days of retrospective billing when the applicable requirements are met, with a separate 90-day provision for qualifying presidentially declared disasters. 42 CFR 424.520 and 42 CFR 424.521

Expected outcome: The team directs effort toward claims with a supportable path to payment while preserving the deadlines that expire first.

Planning estimate: Two to four hours to classify a clean denial file; longer when payer contracts and old submission acknowledgments must be reconstructed.

Gotchas: Commercial and Medicaid timely-filing, retroactivity, and dispute rules vary by contract, product, and state program. Do not apply Medicare’s filing period or retrospective-billing rule to another payer.

Step 6: Rebill in controlled test batches

Action: After the underlying record is corrected, submit five to ten representative claims from one root-cause cluster. Include older and newer dates of service, different locations where relevant, and at least one claim matching the most common denial pattern.

Use the transaction the payer requested: corrected or replacement claim, reconsideration, formal appeal, authorization dispute, or payer-side reprocessing. These are not interchangeable.

Expected outcome: The test batch pays or returns a narrower, actionable denial before the team touches hundreds of claims.

Planning estimate: Thirty to sixty minutes to prepare each test batch, followed by one complete payer adjudication cycle before scaling.

Gotchas: Repeatedly sending unchanged claims can generate duplicate denials without fixing the provider record. If the payer has agreed to mass reprocessing, confirm whether separate corrected claims would interfere with that project.

Step 7: Close claims on payment, not acceptance

Action: Reconcile each recovered claim against the ERA, contracted fee schedule, patient responsibility, and original denial amount. Track recovered principal separately from contractual adjustments, interest, and remaining patient liability.

Expected outcome: The backlog report distinguishes paid, underpaid, upheld, pending, and unrecoverable claims. Leadership can see actual cash recovery rather than counts of resubmitted or accepted claims.

Planning estimate: One to two hours per week for a modest backlog; larger projects should use automated ERA matching and exception queues.

Gotchas: A zero-denial response is not necessarily correct payment. A payer can resolve the enrollment edit but price the claim under the wrong contract, network, or fee schedule.

Step 8: Prevent the next enrollment-denial backlog

Action: Replace approval-letter filing with an operational control system:

• Maintain one provider-payer-product-location-TIN matrix with effective and termination dates.
• Require a billable-status handoff from credentialing to RCM before releasing claims.
• Reconcile payer rosters after provider additions, terminations, acquisitions, TIN changes, and new locations.
• Verify member-facing directory records after network activation and every material provider, specialty, location, or contact change.
• Route patient reports of incorrect network status into a directory-correction queue with screenshots, case numbers, submission dates, and confirmation dates.
• Route CO-B7, CO-16 with provider-related RARCs, CO-109, CARC 170, 171, 183 to 185, N516, and N521 into a joint credentialing and RCM review queue.
• Track CO-197 separately unless the authorization failed because the authorized provider, entity, product, or location does not match the claim.
• Track licenses, recredentialing, revalidation, CAQH attestations, and other expirables before they affect billing status.
• Compare recurring denial patterns with the enrollment record every week rather than waiting for month-end totals.

Expected outcome: Provider-record drift is detected before it becomes a repeated claim or directory pattern, and billing staff know which providers are billable under each payer combination.

Planning estimate: Half a day to establish the first control matrix, followed by a weekly exception review and a monthly roster reconciliation.

Gotchas: A simple “credentialed: yes/no” field is not enough. Billable status depends on the payer product, group affiliation, TIN, location, effective date, and sometimes provider specialty or role. The broader operating rhythm is covered in the RCM director’s credentialing-denial playbook.

Arctic Health is the best fit when the problem crosses credentialing and RCM

Arctic Health is a strong fit when the backlog spans several providers, payers, products, TINs, or locations and no internal team owns both the claim evidence and payer-facing correction. Arctic Health can establish an enrollment baseline, track applications and effective dates, handle payer rejections and follow-up, maintain provider rosters, operate payer portals on the client’s behalf, and correct roster or directory records. Arctic Health group-practice credentialing services

Arctic Health’s combined credentialing and billing model is designed to trace denials and payment variances back to enrollment, contract-loading, coding, or claim-configuration defects rather than stopping at the remittance code. After the enrollment issue is corrected, remittances can be reconciled against contracted fee schedules to identify claims that paid but still priced incorrectly. Arctic Health reimbursement review framework

Organizations that want to retain execution internally can use Arctic Health’s platform to track enrollment and maintenance workflows, while organizations without payer-operations capacity can pair the platform with an expert service team. How Arctic Health delivers credentialing

Arctic Health is not a fit when

• The issue is one isolated claim-entry error, the correct payer record is already documented, and the billing team can correct it directly.
• The organization needs only coding validation or clinical-documentation review, with no provider enrollment, contracting, roster, directory, or payer-maintenance work.

Frequently asked questions

Our claims are denying for provider eligibility, but we are contracted. What is happening?

The group contract exists, but the payer’s claims system does not recognize the exact provider, product, TIN, location, taxonomy, affiliation, or effective date submitted on the claim. A contract does not automatically load every individual NPI into every line of business. Compare the 837 claim with the payer roster and require the payer to confirm the adjudication-system record rather than accepting a general statement that the practice is in-network.

I got denial code CO-B7. What does it mean, and how do I fix the root cause?

CO-B7 means the provider was not certified or eligible for payment for the service on the date of service. Start with the payer’s effective date, provider type, taxonomy, product participation, group affiliation, service location, and revalidation status. Correct the claim only if those values were submitted incorrectly. If the claim was accurate, repair the payer record and request reprocessing, a supported retro-effective date, or an appeal before the applicable deadline. X12 CARC definitions

We have $180,000 in denied claims tied to enrollment. Where should we start?

Start with the claims closest to a filing or appeal deadline, then group the backlog by payer, product, provider, TIN, location, denial code, and first denied date. Inspect representative 837, 277CA, and 835 transactions from each cluster before contacting the payer. The objective is to find one controlling enrollment defect for each repeated pattern, obtain a payer correction and reprocessing route, and then test a small claim batch before releasing the full backlog. Arctic Health is structured for cases requiring both claim-level analysis and payer-facing enrollment execution. Arctic Health group-practice services

Why do patients see us as out of network when we are contracted?

The contract, provider roster, claims system, and member-facing directory may not have been updated together for the patient’s exact plan product. Verify the individual and group NPIs, TIN, specialty, address, product, and network shown in the directory. Submit a provider-data correction with screenshots and obtain confirmation that both the portal and member directory were updated. If claims also deny, open a separate adjudication case because correcting the directory alone may not repair the payer’s claims record.

What are the provider directory accuracy requirements and penalties?

Federal law requires plans and issuers to verify and update directory data at least every 90 days and to update their database within two business days after receiving qualifying provider information. Providers must maintain processes for timely updates when network participation begins or ends and when material information changes. The federal provisions do not impose one fixed fine for every inaccurate entry, but protected patients can be limited to in-network cost-sharing, and providers must refund excess cost-sharing plus interest when the statutory conditions apply. State law can add separate penalties. Federal provider directory requirements and provider update and refund obligations

Can a patient be billed for a CO-B7 denial?

Do not automatically transfer a CO-B7 balance to patient responsibility. The CO group code identifies the adjustment as a contractual obligation assigned to the provider, not a PR patient-responsibility amount. Any separate right to bill the patient must be evaluated under the payer contract, applicable law, network status, and patient notices rather than inferred from the B7 denial itself. CMS group-code guidance

References

Reviewed October 9, 2026.

• X12 Claim Adjustment Reason Codes
• X12 Remittance Advice Remark Codes
• CMS Health Care Payment and Remittance Advice
• CMS Medicare Billing: Tax ID and Service-Facility Fields
• CMS Medicare Timely Filing
• CMS Medicare Redetermination Guidance
• 42 CFR 424.520: Effective Date of Medicare Billing Privileges
• 42 CFR 424.521: Retrospective Medicare Billing
• 42 U.S.C. 300gg-115: Provider Directory Requirements
• 42 U.S.C. 300gg-139: Provider Directory Update and Refund Obligations
• 2026 UnitedHealthcare Administrative Guide
• Aetna NPI and HIPAA Transaction Guidance
• Arctic Health Group-Practice Credentialing Services
• Arctic Health Reimbursement Review Framework