How to Build an 835 ERA Denial Worklist

Start with what the 835 actually says

An X12 835 Electronic Remittance Advice reports payer adjudication results. It can include payment totals, claim and service-line status, adjustments, group codes, Claim Adjustment Reason Codes (CARCs), Remittance Advice Remark Codes (RARCs), patient responsibility, and provider identifiers. Available fields vary with the payer's file.

The ERA does not contain the underlying clinical note and does not prove why documentation failed. It does not independently establish the full facts behind a denial. Use codes to route investigation, then inspect the claim, payer guidance, contracts, source records, and deadlines with qualified staff.

Understand the code combination

• Group code: categorizes financial responsibility or the type of adjustment, such as contractual, patient responsibility, or other adjustment categories.
• CARC: states the reason an amount was adjusted.
• RARC: adds explanation when the payer supplies one.

Keep all three together. Do not turn a short code description into a conclusion about the underlying record, the appropriate correction, or appeal rights. Confirm current definitions and payer-specific instructions.

Build the worklist in seven steps

1. Confirm file scope. Record payer, payment date, EFT or check trace, file identifier, and total paid.
2. Reconcile the header. Compare the remittance total with the expected deposit before working individual claims.
3. Filter the population. Separate paid, denied, partially paid, adjusted, and unmatched claims using the status and payment fields returned.
4. Capture code context. Preserve group code, CARC, RARC, claim-level and service-line amounts, and the payer's claim reference.
5. Group for efficient review. Filter by payer, rendering provider when present, group code, CARC/RARC combination, service date, or financial amount.
6. Prioritize. Apply the team's documented rules for deadlines, dollar exposure, repeated code patterns, missing information, and payer escalation.
7. Export and assign. Export review data, assign work in the team's existing process, record due dates and outcomes, and reconcile completed actions back to the claim record.

Recommended worklist fields

Prioritization checklist

• Is a filing, reconsideration, or appeal deadline approaching?
• Is the claim unpaid, partially paid, or adjusted?
• Does the payer/code combination recur across multiple claims?
• Is a rendering-provider identifier present and useful for routing?
• Does the code indicate that another source must be checked?
• Has the team verified the current code definition and payer instructions?
• Is the next step research, correction, resubmission, payer inquiry, appeal evaluation, posting, or closure under the team's policy?

Use OCP ERA Dashboard within its confirmed scope

The One Care Portal ERA Dashboard is an available standalone product. It reads standard X12 835 files and presents every claim, total billed and total paid, paid and denied claims, rendering-provider NPI filtering or grouping when present, CARC/RARC explanations, and exportable review data.

It is not represented as identifying the underlying cause, correcting claims, proving a documentation issue, assigning work, managing appeals, or integrating with Documentation Intelligence. Export the review data and assign follow-up in the team's existing process.

Related references

• CMS: Electronic Remittance Advice
• X12 Claim Adjustment Reason Codes
• X12 Remittance Advice Remark Codes
• One Care Portal guide to CARC and RARC codes
• Documentation quality and ERA denial review: two separate controls