Denial Code Decoder
N130 — A pointer, not a reason
This remark code tells you to go and read the plan's own benefit documents for the restriction that applies. That is genuinely all it says — it names no element, no policy and no defect, so unlike most remark codes it cannot be worked on its own. The useful response is to stop reading the remittance and start reading the plan: the reason code it arrived with, and the plan's coverage document, are where the answer is.
Billable to the patient? The code does not say. Liability is decided by the reason code on the same line and its group, not by this remark.
Where this denial is born
- Front desk
- Coding
- Claim build
- Submission
- Adjudication
This denial is usually created at the highlighted stage — that is where prevention lives.
Answer the questions — follow the path
The same questions an experienced biller asks, in order. Your answers draw the route to the right action.
Is there a reason code on the same line that you can work?
A remark code qualifies a reason code; the reason code is the denial. N130 adds a direction, not a reason, so the reason code is where the work is.
The full decision tree
Is there a reason code on the same line that you can work?
A remark code qualifies a reason code; the reason code is the denial. N130 adds a direction, not a reason, so the reason code is where the work is.
- Yes →
Can you find the restriction in the plan's own documents?
Look in the plan's coverage policy for the service and in its summary of benefits — a plan must make the latter available without charge.
- Yes →
Work the reason code against the restriction you found. Take the action the reason code calls for, and use the restriction to decide whether it is correctable, appealable, or correct. Then record the restriction against that plan, so the next claim does not rediscover it.
- No →
Make the payer name the restriction. A remark code whose entire content is 'look it up' does not become workable by being read again. Ask payer support which policy or benefit limit was applied, get the identifier, and document the call reference.
- Yes →
- No →
Make the payer name the restriction. A remark code whose entire content is 'look it up' does not become workable by being read again. Ask payer support which policy or benefit limit was applied, get the identifier, and document the call reference.
Prevention
Keep the coverage documents for the plans you bill most, and read the benefit detail in the eligibility response rather than the active-or-inactive flag. This code is the payer telling you the answer was available before the claim went out.
Related reading
The code list, and when it was last checked
X12 maintains the Remittance Advice Remark Codes list, where this code is listed as N130. A remark code carries no adjustment group of its own — the group you see on the remittance line belongs to the reason code it arrived with. It has been on the list since October 31, 2002, and X12 last revised its entry on November 1, 2009.
Checked against the list revision dated July 1, 2026 on August 7, 2026, where it reads as an active code.
Sources
The paragraphs behind the guidance above. A page that tells you what to do about money should show you what the instruction rests on.
Drowning in N130 denials?
Our denial team works them for you — root cause to recovery.
Ready to improve your revenue cycle?
Tell us about your practice and we’ll tell you where we would start.