Govern an ABA CARC and RARC Action Matrix

Define Zara's CARC and RARC action governance control

Zara's matrix is a decision-support register, not a universal denial dictionary. Each row names the adjustment level, code combination, payer interpretation, evidence needed, owner, allowed routes, stop condition, and effective period. Historical versions remain available for older service and remittance dates.

Build the versioned adjustment-code action matrix

Record group code; CARC; RARC and alert status; code text; start, modification, and stop date; payer and product; claim or line level; service context; remittance source; original claim; contract or program source; required evidence; operational interpretation; prohibited inference; owner; inquiry, correction, appeal, secondary, and balance routes; deadline; version; approval; and review trigger. Structured fields preserve identity, source, level, version, clock, comparison, access, action, hold, calculation, correction, retest, and closure. Narrative captures clinical meaning, uncertainty, disagreement, family communication, privacy, legal deferral, and the responsible owner's rationale.

Run Zara's workflow

Zara imports current code-list changes, compares them with payer instructions, and routes clinical or coding questions to qualified reviewers. She tests each row against an ordinary and exception remittance. A code combination with insufficient context produces an inquiry or hold rather than a preselected denial response.

Assign decisions to qualified owners

CARCs explain why a claim or line was paid differently than billed. RARCs can supplement an adjustment or provide informational alerts. Neither code set establishes clinical truth, coverage, patient liability, appeal rights, or the correct claim action by itself.

Work through Zara's fictional example

Zara reviews 30 fictional matrix rows used during the month. Twenty-two have current code text, status, payer scope, level, required evidence, action owner, deadline, and tested result. Two use stopped codes, two ignore informational alerts, one reverses claim and line scope, one assigns responsibility from a CARC alone, one lacks a payer source, and one has no hold path. Six repair. Two stay blocked. This synthetic cohort tests control logic and arithmetic only. It creates no coding, coverage, clean-claim, authorization, payment, patient-balance, disclosure, appeal, privacy, or legal conclusion for a real person, provider, plan, claim, or remittance.

Calculate Zara's measures

Initial row readiness is 22 of 30 rows, or 73.3%. Twenty-eight reach approved use or documented block, or 93.3%. Rows, codes, combinations, remittance items, claims, actions, and dollars remain separate units.

Address the main CARC and RARC action governance risk

A static spreadsheet can keep a deactivated code or payer-specific interpretation in production. One-to-one action rules can also send claims into appeal when the source actually calls for a corrected claim, inquiry, or secondary submission.

Test the versioned adjustment-code action matrix against exceptions

Zara tests new code, modified code, stopped code, informational alert, multiple RARCs, claim versus line, reversal, secondary payer, patient-responsibility group, provider-level adjustment, and unknown combination. Each fixture retains source version, expected state, actual state, affected unit, safeguard, owner, repair, retest, and disposition. Failed, unknown, and held items remain inside the predeclared cohort.

Document the stop condition

Block automated or manual action when the code status, combination, level, payer scope, original claim, or governing route is unclear. Preserve the remittance and seek source-supported clarification before changing claims or balances.

Hand off open work with evidence

Zara's handoff includes the row version, code-list date, payer source, tested remittance, allowed actions, prohibited inference, open question, deadline, and owner. The receiver reruns the row against its fixture before release.

Maintain Zara's control

Zara reviews the X12 update schedule, payer notices, production exceptions, and appeal outcomes. Each confirmed interpretation change creates a new effective version and regression fixture while older remittances retain their historical rule.

Run Zara's independent review

Zara assigns a reviewer who did not build the versioned adjustment-code action matrix. The reviewer reconstructs the CARC and RARC action governance source, state, calculation, action, and close from retained evidence. Earlier versions, failed tests, unknowns, and holds remain available. Hidden exceptions, unexplained values, overwritten history, missing population, or unauthorized decisions fail review.

Start with the adopted claim and status standards

Current 45 CFR 162.1102 identifies the adopted professional-claim standard. The CMS claims-status page identifies the 276 request and 277 response. Zara still records the actual payer, product, route, transaction version, receiver, and artifact before applying either source to the versioned adjustment-code action matrix.

Keep the Medicare stage example inside Medicare

The March 2026 CMS Medicare claim-status guide distinguishes 999 front-end processing, 277CA claim-level acknowledgment, payer control assignment, clean-claim payment-status timing, and duplicate risk during editing. Zara uses those facts only for the applicable Medicare route; other payers and contracts require their own evidence for CARC and RARC action governance.

Read remittance codes with their level and context

CMS's Medicare remittance page separates claim, service-line, and provider-level adjustments and explains group codes, CARCs, RARCs, and PLB in Medicare scope. Zara links the code combination to the raw remittance, original claim, payer source, and qualified decision rather than treating one code as a complete outcome.

Use current X12 code-list status

The X12 external-code-list index defines the scopes of CARCs, RARCs, claim status, and related lists. The current CARC list explains why a claim or line was paid differently than billed. The current RARC list separates supplemental remarks from informational alerts. Zara stores these meanings in the versioned adjustment-code action matrix.

Version updates instead of overwriting history

The X12 code-update listing shows a July 1, 2026 update and notes a corrected RARC N922 effective date on August 3, 2026. Zara retains start, modification, and stop dates, source-check time, and historical mappings so an older remittance is evaluated against the relevant code-set state.

Distinguish receipt and correction identifiers

X12 RFI 2099 says 999 acceptance does not necessarily establish carrier receipt date. X12 RFI 2060 explains the payer-control-number requirement for the standard replacement or void path after adjudication and notes that pending routes can differ. Zara preserves transaction, claim, payer, and version identities separately.

Protect payer order and payment data

The CMS coordination-of-benefits page describes the covered-entity COB transaction. HHS payment guidance and minimum-necessary guidance apply only when their HIPAA conditions are met. Zara verifies payer order, entity status, purpose, recipient, role-based access, and the narrow data needed for the CARC and RARC action governance work.

Keep clinical and compliance authority scoped

The CASP public summary and BACB Ethics Code supply limited clinical and professional context. The OIG GCPG is voluntary and nonbinding. Zara keeps clinical authorship, coding decisions, payer actions, disclosure authority, financial entries, and legal conclusions with their qualified owners throughout the versioned adjustment-code action matrix.

Related resources

• Reconcile ABA Allowed Amount, Contract Adjustment, and Payment.
• Track Payer Claim Control Numbers Across ABA Claim Versions.
• Validate Payer-Specific Clean-Claim Status for ABA Reporting.
• Preserve ABA Timely-Filing Evidence Across Claim Actions.

Sources

• Council of Autism Service Providers, ABA Practice Guidelines Version 3.0 public summary.
• Behavior Analyst Certification Board, Ethics Code for Behavior Analysts.
• Electronic Code of Federal Regulations, 45 CFR 162.1102, standard for health care claims.
• Centers for Medicare and Medicaid Services, Health Care Claims Status.
• Centers for Medicare and Medicaid Services, Checking Medicare Claim Status, March 2026.
• Centers for Medicare and Medicaid Services, Health Care Payment and Remittance Advice.
• X12, External Code Lists.
• X12, Claim Adjustment Reason Codes.
• X12, Remittance Advice Remark Codes.
• X12, Code Updates Listing.
• X12, RFI 2099, 999 Confirming Claim Receipt.
• X12, RFI 2060, Withdrawal or Void Claim and Response.
• Centers for Medicare and Medicaid Services, Coordination of Benefits transaction.
• U.S. Department of Health and Human Services, Uses and Disclosures for Treatment, Payment, and Health Care Operations.
• U.S. Department of Health and Human Services, Minimum Necessary Requirement.
• U.S. Department of Health and Human Services Office of Inspector General, General Compliance Program Guidance.