Fast answer: Consult the contractual agreement for restrictions, billing, or payment information related to the charges.
How to use RARC N381
RARC N381 should be read with the CARC and group code on the same claim or service line. For BCBS denials, the remark often tells you whether the next move is a corrected claim, attachment response, COB update, authorization proof, or appeal packet.
Common paired CARCs
Recommended workflow
- Separate true zero-pay denials from paid lines with contractual write-offs.
- Compare the allowed amount to the contract, product, network status, modifier, units, and place of service.
- Recalculate expected reimbursement at line level and show the exact variance.
- File a payment dispute when the plan used the wrong contract, fee schedule, provider status, or pricing rule.
- Post the adjustment when the allowance is correct and patient liability is not supported.
Evidence checklist
- ERA/EOB allowed amount
- Contract or fee schedule excerpt
- Expected payment calculation
- Network/product verification
- Modifier/unit documentation
- Prior payer EOB if secondary
FAQ
What does RARC N381 mean?
Consult the contractual agreement for restrictions, billing, or payment information related to the charges.
Is N381 enough to appeal a BCBS denial?
No. Pair the RARC with the CARC, group code, EOB text, claim line, and plan rule. The RARC explains the missing detail or context; the CARC explains the adjustment reason.
What should I attach for N381?
Start with ERA/EOB allowed amount, Contract or fee schedule excerpt, Expected payment calculation, Network/product verification. Add only the records that answer the specific remark code and denial reason.