Key points
- Group denials by cause, not by payer: the same reason code from four payers is usually one internal process failure.
- CARC tells you the adjustment; RARC usually tells you what to fix. Reporting on CARC alone hides the actionable half.
- Every recurring denial category needs a named owner, or it comes back next month.
A denial queue sorted by payer and dollar amount is a work list. It is not analysis, and it will not reduce next month's denial rate. The shift that matters is grouping denials by what caused them, which means reading the reason codes as a set rather than as individual tasks.
CARC and RARC do different jobs
Claim Adjustment Reason Codes explain why the paid amount differs from the billed amount. Remittance Advice Remark Codes add the detail: which document was missing, which policy provision applied, which identifier was invalid. Many practices report only on CARC because it is the field their system surfaces most easily, and in doing so they discard the part of the remittance that tells them what to change.
Four buckets, four different owners
Almost every denial resolves into one of four categories, and each category belongs to a different part of the practice. Sorting them this way is what makes prevention assignable.
Front-end and registration
Coverage terminated, member ID invalid, coordination of benefits unresolved, no authorization on file. These are collected before the visit, so they are fixed before the visit — no amount of billing skill recovers them cleanly afterward.
Coding and documentation
Procedure inconsistent with diagnosis, bundled or included in another service, modifier missing or invalid, medical necessity not established. These belong to coding review, and the fix is usually a documentation template change rather than a coder correction.
Contractual and configuration
Non-covered service, exceeds fee schedule, benefit maximum reached. Some of these are legitimate contractual adjustments. Some are a fee schedule loaded incorrectly in the practice management system, which quietly understates expected reimbursement and looks like a write-off. Distinguishing the two requires comparing paid amounts against the contract, not against the charge.
Payer behavior and timeliness
Timely filing exceeded, duplicate claim, additional information requested. This bucket measures your own follow-up cadence more than the payer's conduct. Timely filing denials in particular are almost always self-inflicted: a claim that sat in a work queue rather than a claim the payer lost.
What a monthly denial review should produce
- 1A denial rate for the month, and the same figure for the trailing three months so a spike is visible as a spike.
- 2The top five reason-code groups by dollars and by volume — they are rarely the same list, and both matter.
- 3For each of the top groups: the assigned owner, the specific process change, and the date it took effect.
- 4A short list of denials that are genuinely un-preventable, so the team stops relitigating them.
The output is a page, not a dashboard. If the review does not end with somebody's name next to a change, the same codes will be at the top of the list next month.
Appeals still need a standard
Prevention does not eliminate appeals — it reduces the ones you should never have had. For the remainder, keep a per-payer record of appeal levels, deadlines, and the documentation each level requires, and file the strongest version first. Sending a thin appeal to preserve the deadline and a complete one later usually costs you the level rather than buying time.