RecoveAR and the Denial Taxonomy: Turning 2026 CARC/RARC Codes Into a Ranked Worklist
Most AR teams inherit one flat denial queue where a fixable typo sits behind a medical-necessity fight. RecoveAR reads the 835, classifies every adjustment code, and sorts the work by what it actually is.
Why one flat queue leaks money
The problem is not the volume of denials. It is the sorting.
A denial code carries a group code, a reason, and a remark. Read together they tell you exactly which lane the work belongs in. Ignore them and every denial gets the same generic touch.
The pipeline, end to end
From 835 parse to CARC/RARC classification to a routed worklist
Follow one denied line as it moves through RecoveAR. The remittance comes in as an X12 835. The engine extracts the codes, decides soft or hard, and drops the line into the right track with its deadline attached.
Parse the 835 remittance
RecoveAR reads the X12 835 Health Care Claim Payment/Advice (v5010), walking each claim (CLP) and service line (SVC) to lift the adjustment segments.
Map the CARC + RARC to a taxonomy
The group code (CO, PR, OA, PI), the Claim Adjustment Reason Code, and every Remittance Advice Remark Code are read together and matched against the current 2026 code lists and the CAQH CORE 360 combinations.
Score, sort, and route
Each line is scored on recoverable dollars, payer timely-filing clock, and rework difficulty, then dropped into the correct track. High-value, near-deadline work floats to the top of the worklist.
↻ Soft denial → Rework
The claim can be fixed and resubmitted inside the filing window. No provider argument required, just clean data and the right code.
- Missing or invalid data, registration, or coding errors
- Retro-obtainable authorization or referral
- Coordination-of-benefits and payer-sequence fixes
- Wrong code combination flagged by the 835 remark
⚖ Hard denial → Appeal
The payer made a coverage or medical-necessity call. Recovery needs documentation, an appeal letter, and a body of evidence, not just a resubmit.
- Medical necessity and level-of-care denials
- Non-covered service or benefit exclusion
- Timely-filing and after-termination denials
- Experimental / investigational determinations
The taxonomy in practice
How common 2026 CARC codes map to a track
These are illustrative rows drawn from the standard X12 Claim Adjustment Reason Code list. The exact routing is governed by the group code and the accompanying RARC, which is why RecoveAR always reads the pair, never the CARC alone.
| CARC | Meaning | Typical group | Class | Track |
|---|---|---|---|---|
| 16 | Claim/service lacks information or has submission/billing error (paired with a RARC) | CO | Soft | Rework |
| 197 | Precertification / authorization / notification absent | CO | Soft | Rework (retro-auth) |
| 18 | Exact duplicate claim or service | OA | Soft | Rework (verify + suppress) |
| 11 | Diagnosis inconsistent with the procedure | CO | Soft | Rework (coding) |
| 50 | Non-covered, not deemed a medical necessity by the payer | CO | Hard | Appeal |
| 96 | Non-covered charge(s), see the paired RARC for the specific reason | CO / PR | Hard | Appeal or patient |
| 29 | Time limit for filing has expired | CO | Hard | Appeal (proof of filing) |
| 27 | Expenses incurred after coverage terminated | CO | Hard | Appeal or eligibility |
A note on read order: the same CARC can be soft or hard depending on the RARC it ships with. CARC 96 with a remark pointing to a data fix is rework; CARC 96 with a benefit-exclusion remark is an appeal. The pair decides, and the taxonomy encodes that.
Why the codes are trustworthy enough to route on
The CAQH CORE 360 Rule standardizes the combinations
The Phase III CAQH CORE 360 Uniform Use of CARCs and RARCs (835) Rule defines four business scenarios and the CARC/RARC/group-code combinations a plan is expected to use for each. That standardization is what makes a rules-based taxonomy dependable across payers.
Additional documentation required
Missing, invalid, or incomplete documentation the payer needs to adjudicate. Routes to rework.
Additional data required
Missing, invalid, or incomplete data on the submitted claim itself. Routes to rework.
Billed service not covered
The service is not covered by the health plan. Routes to appeal or to patient responsibility.
Benefit not separately payable
The billed service is bundled or not separately payable. Routes to coding review or appeal.
A worklist that stays current
The code lists move, so the taxonomy re-maps
CARC and RARC values are maintained externally and refreshed on a fixed schedule. RecoveAR re-syncs against each release so a code deactivated or re-defined in 2026 does not silently mis-route work.
Code additions and deactivations take effect; taxonomy re-mapped.
Mid-year update; new remark codes folded into routing rules.
Year-end update aligned to CMS remittance advice guidance.
Built on the real standards
What the taxonomy is grounded in
X12 835 v5010 · CARC/RARC code lists
The Health Care Claim Payment/Advice standard and its external Claim Adjustment Reason Code and Remittance Advice Remark Code lists, with 2026 updates applied on each scheduled release.
CMS Remittance Advice standards
CMS remittance advice requirements for the Medicare 835 and Standard Paper Remittance Advice govern how adjustment reasons are reported, so the taxonomy stays consistent with what payers actually transmit.
CAQH CORE 360 Rule
The Phase III CAQH CORE Uniform Use of CARCs and RARCs (835) Rule and its four CORE-defined business scenarios, which standardize the code combinations a plan may return.
Stop working denials in the order they arrived. Work them in the order they pay.
RecoveAR turns your 835 feed into a ranked worklist that already knows which denials are a five-minute rework and which need a real appeal. Your team spends its hours on recoverable dollars, not triage. We will map the taxonomy to your top payers and show it against a live remittance sample.
Book a RecoveAR walkthroughASP-RCM Solutions · denial management and AR recovery built on the standards your payers already use.
Related reading
Catch the edit before the claim drops, not after the denial.
How CorePulse, an AI medical coding engine, enforces CMS NCCI PTP edits and Medically Unlikely Edits at charge
Read →Case studyStop the denial before the needle, not after the claim.
How a pain practice builds front-end frequency and level-count guardrails against Medicare facet and epidural
Read →BriefingA claim can be paid in full and still be underpaid. Your 835 just calls it done.
A paid claim can still be underpaid. See how RecoveAR reconciles your X12 835 paid-vs-allowed lines against pa
Read →