An Anthem denial code tells you why a claim wasn’t paid, and reading it correctly is a two-step job: Anthem’s internal code (such as G18 or i53) identifies the specific reason on its side, and that internal code maps to a standardized HIPAA Claim Adjustment Reason Code (CARC) that appears on your 835 electronic remittance. The list of Anthem denial codes you’ll actually encounter is short in practice, and most denials come down to a handful of recurring causes: a procedure code that isn’t on your fee schedule, a missing modifier, a provider ID mismatch, or a filing deadline that has passed.
How to Read an Anthem Denial
Anthem’s denial system runs on two layers. The internal Anthem code describes the reason in Anthem’s own terms. The HIPAA CARC on the 835 remittance is the standardized version, maintained by X12, the organization chartered by the American National Standards Institute to develop electronic data interchange standards for healthcare.1X12. Claim Adjustment Reason Codes An 835 may show only the HIPAA remark code, not the internal Anthem code, so if the standardized code doesn’t give you enough to work with, you’ll need to cross-reference both.
G18 and CO-256: Service Not Allowed Under Contract
G18 is one of the most common Anthem denials. It’s defined as “disallow not allowed under contract,” meaning the service as billed isn’t payable under your contract.2Empire BlueCross BlueShield. Claim Denial Codes G18 and 256 On the 835, it maps to HIPAA Remark Code CO-256, “service not payable per managed care contract.”3Empire BlueCross BlueShield. Denial Update Bulletin
The trigger is that the CPT or HCPCS code you billed can’t be matched to the fee schedule tied to your contract. Anthem lists several common reasons that happens:
- The procedure code isn’t on the applicable state fee schedule at all.
- A required pricing modifier (NU, RR, TC, or 26) was left off, so the system can’t find a price. Rate-adjusting modifiers like 50, 51, or QX don’t cause this.
- The service is outside your contracted scope or provider type. A hospital facility billing professional services on a CMS-1500, or a transportation provider billing medical services, will hit this.
- The claim processed under the wrong Anthem provider ID, such as a group ID where a facility ID belonged.
- A facility claim combined an invalid revenue code with the procedure code.3Empire BlueCross BlueShield. Denial Update Bulletin
i53: Incorrect Procedure Code Edit
Denial code i53 has appeared on lab claims. In Anthem’s Ohio Medicaid program, an edit incorrectly required primary procedure code 80050, which is non-covered, causing lab claims to deny under i53. Anthem disabled the faulty edit in October 2025 and reprocessed the affected claims.4Anthem Blue Cross and Blue Shield. Ohio Medicaid CPSE Log, November 2025 If you’re seeing i53 on lab claims, check whether a known systemic error is in play before resubmitting.
CARC 29: Timely Filing Limit Expired
CARC 29 isn’t unique to Anthem, but it’s one you’ll see from Anthem and every other payer. The X12 definition is simply “The time limit for filing has expired.”1X12. Claim Adjustment Reason Codes The code has been in use since January 1995. Once this code posts, the fix is appeal with proof of timely submission rather than resubmission.
How to Resolve an Anthem Denial
The right fix depends on the code, but Anthem’s guidance on G18/CO-256 covers the general approach for most contract and coding denials. Start by confirming whether the procedure code you billed is on the applicable fee schedule. For Indiana Medicaid managed care, that means checking the Indiana Health Coverage Programs Professional and Outpatient Fee Schedules, which update monthly.2Empire BlueCross BlueShield. Claim Denial Codes G18 and 256
From there:
- If the denial came from a missing modifier or a bad revenue-and-procedure-code pairing, submit a corrected claim.
- If the claim processed under the wrong provider ID, contact Provider Services or submit a claim dispute form to request reprocessing.
- If the service genuinely falls outside your current contract, contact a provider contracting specialist about amending the agreement.3Empire BlueCross BlueShield. Denial Update Bulletin
If you’re contracted through an accountable care organization, a participating medical group, or an independent physician association, follow that group’s authorization and claims guidelines, which can differ from Anthem’s standard rules.2Empire BlueCross BlueShield. Claim Denial Codes G18 and 256
Checking Denials Yourself Through Availity
Anthem exposes much of its denial detail through Availity’s Payer Spaces portal. The Claims Status Listing lets you pull up your claims, see which have proactive insights flagged, review the specific denial reason, and get step-by-step instructions for moving the claim toward payment.5Anthem Provider News. Access to More Claim Denial Information Is Now Self-Service You can also revise claims, attach documentation, or remove claims filed in error. The data refreshes daily.
When the Denial Is Anthem’s Error
Not every denial is your fault. Anthem periodically identifies Claims Payment Systemic Errors (CPSEs), which are system-wide problems that cause widespread improper denials or underpayments. Anthem publishes CPSE logs for each state program. Recent Ohio Medicaid logs show the pattern: a Provider Master File logic error that failed to create in-network records and caused “no authorization” denials for in-network providers;6Anthem Blue Cross and Blue Shield. Ohio Medicaid CPSE Log, October 2025 attending providers with enrollment status “K” incorrectly denied as not registered with the state, corrected in October 2025;4Anthem Blue Cross and Blue Shield. Ohio Medicaid CPSE Log, November 2025 and the i53 lab denial already noted above.
When Anthem confirms a systemic error, it typically reprocesses the affected claims automatically. If you think a denial pattern you’re seeing matches a known CPSE, review the current log for your state and call Provider Services. The Ohio Medicaid line is 844-912-1226.4Anthem Blue Cross and Blue Shield. Ohio Medicaid CPSE Log, November 2025
Looking Up a Code You Don’t Recognize
The standardized codes on Anthem’s remittance aren’t Anthem’s. The Claim Adjustment Reason Codes, the Remittance Advice Remark Codes, and the Service Review Decision Reason Codes are all maintained by X12 through its external code repository.7X12. External Code Lists If a HIPAA remark on your 835 is unfamiliar, the X12 code list is the authoritative source for its definition.