CMS issued a 2026 update related to CAQH CORE 360 CARC, RARC, and CAGC combinations for 835 Electronic Remittance Advice workflows
Healthcare EDI compliance is not only about sending and receiving files. It is also about using the information inside those files correctly. That is especially true for the X12 835 Electronic Remittance Advice. The 835 tells providers, billing teams, and revenue cycle systems what happened after a claim was adjudicated: what was paid, denied, adjusted, reduced, recouped, or assigned to patient responsibility.
When the adjustment and denial information is not interpreted consistently, the impact can move quickly from EDI into payment posting, denial management, secondary billing, patient billing, and reconciliation.
CMS Updates: Main Issues
CMS published a Medicare Claims Processing update dated May 27, 2026, related to the CAQH CORE 360 Uniform Use of CARC, RARC, and CAGC combinations for the 835 Electronic Remittance Advice. The effective date is October 1, 2026, with implementation on October 5, 2026.
The update instructs Medicare contractors and Shared System Maintainers to make system changes according to CORE 360 uniform rules for Claim Adjustment Reason Codes, Remittance Advice Remark Codes, and Claim Adjustment Group Codes.
In simple terms, this is about making sure remittance advice uses standardized code combinations for defined adjustment and denial business scenarios.
What CARC, RARC, and CAGC Mean
CARC, RARC, and CAGC codes work together to explain the business reason behind a payment adjustment or denial:
- CARC explains why a claim or service line was adjusted.
- RARC provides additional explanation when more detail is needed.
- CAGC groups the adjustment into a broader category, such as contractual obligation, payer responsibility, provider responsibility, or patient responsibility.
The CAQH CORE 360 rule explains that these code combinations are used in the X12 835 to report payment adjustments and denials, and that the code lists require ongoing maintenance because codes may be added, revised, or stopped over time.
Why This Matters for EDI and Revenue Cycle Teams
For healthcare EDI teams, the update is a reminder that 835 processing must be maintained, tested, and monitored. If systems use outdated code logic, remittance information may still arrive, but the business interpretation can be wrong. That can lead to incorrect payment posting, missed denial follow-up, wrong patient balances, secondary billing delays, or manual research by revenue cycle teams.
Teams should review how their systems, vendors, clearinghouses, and internal workflows handle current CARC/RARC/CAGC combinations. This includes mapping, display logic, denial routing, reporting, exception queues, and staff-facing descriptions.
The CMS 2026 update is a practical reminder for healthcare EDI, billing, and denial management teams to review remittance code maintenance before changes reach production.
At EDI Academy, we help healthcare EDI and revenue cycle professionals understand the details behind EDI transactions, identify risks early, and prevent avoidable errors in claims, remittance, payment, and denial workflows.