Why In-Network Claims Deny as Out-of-Network: Enrollment and Roster Errors

Updated November 5, 2026, based on X12, CAQH CORE, CMS, the U.S. Code and the Code of Federal Regulations as of that date.

When a contracted provider's claim denies as out-of-network, start by checking for a record mismatch. The rendering NPI, the group's tax ID, the service location or the specialty on the claim may not match a record the payer has linked to your in-network agreement. Sometimes the denial isn't about your contract at all: the member's plan is a narrower network than the one you joined, or the member has no benefit for that service.

Start by reading the adjustment codes on the 835 or the remittance. They tell you whether to fix a provider record, check the member's plan, or appeal. Then find the record that's wrong, correct it with the payer, confirm it loaded, and ask for the claims to be reprocessed.

Read the denial codes first

The X12 claim adjustment reason codes and remittance advice remark codes narrow the cause. These are the ones tied to network and enrollment problems, with what to check first:

• CARC 242, "Services not provided by network/primary care providers": whether the payer has the rendering provider loaded to your contract at this location.
• CARC 243, "Services not authorized by network/primary care providers": the referral or authorization from the member's assigned PCP or network.
• CARC 279, "Services not provided by Preferred network providers," which X12 says to use for member network limitations such as a narrow network: whether your contract includes the member's specific product.
• CARC B7, "This provider was not certified/eligible to be paid for this procedure/service on this date of service": the effective dates of the provider's enrollment or credentialing.
• CARC 8, "The procedure code is inconsistent with the provider type/specialty (taxonomy)," and RARC N95, "This provider type/provider specialty may not bill this service": the specialty and taxonomy on file versus the claim.
• CARC 204, "This service/equipment/drug is not covered under the patient's current benefit plan": the member's benefits, not your enrollment.
• RARC N570, "Missing/incomplete/invalid credentialing data": the provider's credentialing status with the payer.

The group code matters too. X12's group codes include CO for contractual obligation and PR for patient responsibility. A PR adjustment assigns the amount to the patient, so a network error on the payer's side can turn into a patient balance.

Some out-of-network denials aren't enrollment errors

Before you open a ticket about your roster, rule out the plan. CARC 279 exists because a payer can contract with you for some products and not others. A provider can be in network for a payer's commercial PPO and outside its narrow-network or exchange product. The same applies to a Medicare Advantage or Medicaid managed care plan your contract doesn't cover.

The eligibility response can show this. Under CAQH CORE's eligibility data content rule, when a service is covered in network only, the 271 must flag it as non-covered out of network, with EB01 set to I and EB12 set to N. It must also return separate in-network and out-of-network cost sharing when they differ. That tells you what the member's benefits are. For tiered benefits, the rule also says that when the plan can identify the inquiring provider, the 271 must return that provider's tiered network status. Outside that case, the rule doesn't address whether the payer has your rendering provider loaded at your location, so a clean benefits check can still be followed by a network denial.

Where the payer's record goes wrong

The No Surprises Act defines provider directory information in 42 U.S.C. 300gg-139 as names, addresses, specialty, phone numbers and digital contact information for individual providers, and names, addresses, phone numbers and digital contact information for each contracted group, clinic or facility. Check each of those fields against your claims. Look for:

• A new provider loaded under the wrong group, tax ID or location, or not loaded yet on the start date.
• A specialty or taxonomy that differs from what you bill, which shows up as CARC 8 or N95.
• A service address that doesn't match the location on the claim.
• A directory status such as "not accepting new patients" that's out of date. For Medicare Advantage, CMS's Medicare Managed Care Manual, Chapter 4, section 110.2.2, says plans should contact network providers quarterly to update this status, addresses and phone numbers.

Your NPPES record is part of this. Under 45 CFR 162.410, covered health care providers must report changes to their NPI data to NPPES within 30 days. Payers vary in how much they rely on NPPES taxonomy and addresses, so keep them in step with what you send in rosters.

Payers differ in which fields they use to match a claim to a contract: billing NPI, tax ID, rendering NPI, service location or some combination. The payer's provider manual or roster guide is the place to confirm it. The same goes for portal access. If a payer's portal doesn't recognize your group or tax ID, check how it registers organizations before assuming the contract is missing.

What the law requires from you and from the payer

Under 42 U.S.C. 300gg-139, providers and facilities must send directory information to a plan when a network agreement begins, when it ends, when that information materially changes, and at any other appropriate time, including on request. That covers new hires, moves, new locations and specialty changes.

Plans have matching duties under 42 U.S.C. 300gg-115. Group health plans and insurers must verify directory information at least every 90 days. They must update their public database within 2 business days of receiving information from a provider, and remove providers they can't verify. For Medicare Advantage, CMS's manual expects online directory updates within 30 days of receiving information, and 42 CFR 422.120 requires plans' public directory API to reflect updates within 30 calendar days.

These rules also protect the patient. If a member relied on a directory or plan response that wrongly listed a provider as in network, 300gg-115(b) caps the member's cost sharing at in-network levels. Under 300gg-139(b), a provider who billed more than that and was paid must refund the excess with interest. The Departments' FAQ Part 49, from August 2021, said that until further rulemaking, plans are expected to apply the directory rules using a good faith, reasonable interpretation of the statute.

How to confirm a roster loaded and fix the claims

1. Keep a record of every roster or change form you send: date, channel, and the providers and fields it changed.
2. After the payer's stated processing time, search its public provider directory for each provider by name and location. Check specialty, address, group affiliation and new-patient status. For Medicare Advantage plans, the public directory API is another place to check.
3. If the payer's portal has a provider or roster status lookup, check it there as well. If not, call provider services and get a reference number.
4. If you see an error, correct it through the payer's own channel, such as its roster template or provider data portal. Ask for the effective date to match the contract or credentialing approval date.
5. Pull every claim with the same denial for that provider since the start date. A 276/277 status inquiry or the payer's portal can show which are still pending.
6. Ask for reprocessing once the record is fixed. Payers differ on whether a corrected record triggers automatic reprocessing, a reconsideration request, or a formal appeal, and on the deadline for each. Check the provider manual, and track timely filing limits while you wait.

For more on keeping enrollment records clean, see our guide to provider enrollment automation. Our guide to denial management automation covers the appeal side.

Frequently asked questions

Why does a claim deny as out-of-network when the 271 showed active coverage?

The 271 reports the member's coverage and benefits. Active coverage doesn't confirm how the payer has loaded your rendering provider, location or specialty, which can still affect claims processing.

What's the difference between CARC 242 and CARC 279?

CARC 242 means the service wasn't provided by a network provider. CARC 279 is for member network limitations, such as a contracted provider that isn't in the member's narrow network.

How fast does a payer have to update its directory after I send changes?

For group health plans and insurers, federal law requires updating the public database within 2 business days of receiving the information. Medicare Advantage plans are expected to update online directories within 30 days. State law and your contract may set other timelines.

Do I have to refund the patient if the payer's directory was wrong?

If the plan's directory or a plan response told the member you were in network, their cost sharing is capped at in-network levels. If you billed more than that and the patient paid it, federal law requires you to refund the excess with interest.

Should I appeal or ask for reprocessing?

If the denial came from a record the payer has since fixed, ask for reprocessing first. Use an appeal when the payer disputes your network status, and follow its deadlines.

Chasing roster updates and reprocessing across payer portals?

Champ automates portal work like provider enrollment updates, directory checks and claim status follow-up. We set it up and run it, so your team sees only the finished results. If out-of-network denials keep coming back after go-live, learn more here.

This post is general information, not legal, compliance or billing advice. Rules vary by payer and state and change often, so confirm with the payer's provider services team or your contract manager before acting. Champ is not affiliated with or endorsed by CMS, X12, CAQH or the other agencies and plans mentioned here.