RemitBench/Denial codes/CO-242
CO-242 denial code
Code 242 is about who delivered the care rather than what it was. The plan restricts coverage to its own network and this service came from outside it.
The code list's own wording: Services not provided by network/primary care providers.
- What it means
- The plan pays only for care from its network, or requires a primary care provider to be involved, and the provider on this claim did not meet that.
- Who owes the money
-
Read the letters
PRis common on genuine out of network care, and the patient generally does owe it, subject to whatever protections apply.COmeans you absorb it, which is the right answer when the provider is in network and the payer's record is wrong. - Is appealing worth it
- Worth it when the provider is actually in network. That is a records dispute rather than a coverage one, and it is usually resolved by credentialling rather than by an appeal department.
Check your own enrolment status before telling the patient anything. A provider who has joined the group and whose payer enrolment has not completed produces this denial on every claim, and the care was genuinely in network from the patient's point of view. Telling a patient they saw an out of network dentist when the paperwork simply had not caught up is a mistake that costs the relationship.
Why the payer sent it
- The provider is genuinely outside that plan's network.
- The provider is in network and their enrolment record is out of date.
- A new provider in the practice is not yet credentialled with that payer.
- The claim carried the wrong provider identifier, so a network provider looked like a stranger.
- The plan requires a primary care provider referral that was not obtained. See CO-288.
- The practice location is not enrolled, even though the provider is.
Remark codes you will see with it
| Remark code | What it adds |
|---|---|
| N130 | Read the plan document for the network rules. Its own page. |
| N95 | This provider type or specialty may not bill this service. |
Read the letters in front of the 242
- CO-242
- Contractual obligation. Your write-off. Correct where you are in network and something else went wrong.
- PR-242
- Patient responsibility. The usual pairing for genuine out of network care.
- PI-242
- Payer initiated. The patient owes nothing.
What to do next
-
Confirm the provider is enrolled with that payer for that date
Not whether they are credentialled generally. Whether this payer, this plan and this location show them as participating on the date of service.
If they are: this is a payer record error. Ask for reprocessing, and involve your credentialling contact rather than the appeals queue. If they are not: find out whether an application is pending, and whether that payer backdates on approval. Several do. -
Check the identifiers on the claim
A wrong rendering or billing identifier makes an in-network provider invisible. It is a cheap check and it explains a share of these.
-
Work out what the patient can be charged
Out of network billing rules vary, and some situations carry protections that limit what a patient can be charged regardless of network status. Establish that before the statement, not after.
-
Track credentialling as a schedule item
The real prevention. A new provider seeing patients before enrolment completes generates denials on every claim until it does. Knowing the completion date per payer lets you schedule around it.
Codes that get mixed up with 242
| Code | How it differs from 242 |
|---|---|
| 243 | Services not authorised by network providers. Authorisation rather than participation. |
| 288 | Referral absent. A missing step rather than a network status. See CO-288. |
| B7 | The provider was not certified or eligible on the date of service. See CO-B7. |
| 185 | The rendering provider is not eligible to perform the service. See CO-185. |
| 24 | Covered under a capitation agreement. See CO-24. |
Code 242 in dental
Dental networks are wide and dental credentialling is slow, so this is a common denial in growing practices. An associate joining a practice can be treating patients for months before every payer enrolment completes.
The associate problem
A new associate is the standard cause. Patients book with the practice, not the individual, and the plan pays by the individual. Until enrolment completes, every claim for that dentist bounces even though the practice is in network.
Two things reduce the damage: find out which payers backdate on approval, and where they do not, know the completion date so scheduling can work around it.
Tell the patient before the appointment, not after
If a patient will be out of network for their visit, that is information they can act on beforehand. Discovering it on a statement afterwards is the version that generates complaints.
Questions people ask about CO-242
Can I bill the patient for a CO-242?
Often yes when the provider is genuinely out of network, and the PR letters usually say so. Check first whether the provider actually is out of network, because a pending enrolment produces the same denial, and check what protections apply, because some situations limit what an out of network provider may charge regardless.
Our provider is in network. Why this denial?
Usually the payer's enrolment record, or the identifiers on the claim. A newly joined provider whose credentialling has not completed, a practice location that is not enrolled, or a wrong rendering identifier all make an in-network provider look like a stranger to the payer's system.
Related codes
RemitBench reads dental EOB PDFs and turns them into posting-ready lines, in your browser, with no upload. It does not read medical remittances today.
Open the appOpens your mail app with the message written. Nothing is sent from this page.