By FlowClaim RCM Editorial Team
How to Read CARC and RARC Codes on an ERA
A remittance code is the starting point of an investigation. Read the complete adjustment, connect it to the service line, and decide what the account needs next.
An electronic remittance advice can explain payment, an adjustment, a denial, or several outcomes on one claim. When a billing team reduces that information to a single short label, important distinctions disappear. A contractual reduction may enter a denial queue, a missing-data problem may become a patient statement, or an unpaid line may be overlooked because another line paid.
This guide helps practice owners and billing managers read the information in a useful order. You do not need to memorize every code. You need a reliable way to find the current meaning, connect it to the right claim, and document a supported next action.
Understand the three layers of an adjustment
CMS describes claim adjustments using a group code, a Claim Adjustment Reason Code (CARC), and, where applicable, a Remittance Advice Remark Code (RARC). The group addresses responsibility, the CARC explains the adjustment, and a remark can add detail. Provider-level adjustments are a separate category. See CMS remittance guidance.
Keep these elements together in your worklist. A list of CARCs without the related group and remarks can send staff toward the wrong action. Preserve the original remittance as the reference even when the practice management system presents a simplified screen.
Read the remittance from payment to service line
Identify the payment and claim
Begin with the payer, payment date, payment reference, and associated claims. Match the claim to the correct patient account and encounter. If your practice receives multiple remittances from related payer products, confirm which product processed this claim before applying a contract or policy.
Inspect each affected line
Compare the service date, code, units, submitted charge, payment, and adjustments. An overall paid status does not prove that every line processed as expected. Conversely, one denied line does not necessarily make the entire claim unpaid. Keep the investigation aligned with the actual scope of the adjustment.
Reconcile the amounts
Account for how the charge was distributed across payment and adjustments. If the account screen and remittance do not reconcile, check for reversals, secondary payments, prior posting, or import problems before contacting the payer about a supposed underpayment. A posting discrepancy and a payment determination require different solutions.
Use current definitions instead of an old cheat sheet
Look up unfamiliar codes in the authoritative X12 external code lists. Read usage instructions and effective-status information, not only the short description. Use the correct list: claim-status codes and adjustment codes are different code sets, even when a number looks familiar.
Maintain an internal reference that links to the official source and records the date your team checked it. Treat the reference as a training aid. It should explain how to investigate common scenarios without promising that the same code always has the same resolution.
If the payer response appears inconsistent with a code’s usage, preserve the evidence and seek clarification. Do not silently change the received code to fit a familiar pattern. Reporting the discrepancy may also help the practice identify a mapping error in its own software.
Turn the combination into a specific question
Instead of assigning an account with “denied, call payer,” write the unanswered question. Examples include which submitted field failed, whether the payer received the replacement reference, or which contract provision supports the allowed amount. A precise question makes the next interaction shorter and easier to evaluate.
- For a data problem, compare the outgoing claim with its source record.
- For a duplicate response, locate and reconcile the original claim.
- For a deadline issue, reconstruct the submission history.
- For a coverage question, identify the policy applicable to the service.
- For a possible underpayment, compare the adjudication with the applicable payment terms.
These are investigation routes, not automatic resolutions. The actual claim, complete payer notice, and contract determine whether correction, review, supported adjustment, or another action is appropriate.
Illustration: a partially paid claim
Consider a hypothetical claim with several service lines. The payer pays one line, reduces another under payment terms, and identifies a submission problem on a third. A biller who sees only “partial payment” might send the entire claim back without addressing the affected field.
A more useful review separates the outcomes. The posting team verifies the contractual reduction, the correction team investigates the submission problem, and the account owner confirms that any replacement follows the payer’s instructions. Previously paid lines are handled according to those instructions rather than omitted or duplicated by assumption.
The account note explains which balance remains open and why. That lets the next employee understand the case without repeating the original investigation. It also prevents the practice from reporting every adjustment dollar as denied revenue.
Handle responsibility and patient statements carefully
Do not make an automatic patient-transfer rule from a familiar CARC alone. Review the group, benefits, prior payments, contract, and applicable billing restrictions. A statement should reflect supported patient responsibility after the account has been reconciled, not merely the balance left by an incomplete posting process.
If information is missing or responsibility is disputed, route the account for review and make the hold visible. Explain the unresolved issue in neutral language when communicating with the patient. Avoid telling the patient that the insurer “will not pay” when the team is still correcting a submission error.
Keep provider-level adjustments separate
If the deposit does not equal the sum of the claim payments, ask the posting team to review any provider-level adjustment and its reference. Do not distribute an unexplained difference across patient accounts merely to force the deposit to balance. Identify whether the amount relates to another transaction, a prior period, or a payer communication.
Assign unresolved reconciliation items to a named owner. Store the investigation with the payment batch and link any related account without changing balances prematurely. This keeps cash reconciliation and claim follow-up connected while preserving the audit trail for each.
Make remittance data useful for improvement
Store the original code combination separately from your internal root-cause label. The payer’s label describes its response; the internal label explains the process failure your team confirmed. For example, repeated data errors might ultimately trace to a registration template or claim-interface setting.
Review combinations by payer, product, provider, and service where useful. Include counts, affected dollars, resolution time, and repeat occurrences. Avoid comparing teams with different queue definitions without explaining the difference. A team working difficult appeals will not have the same daily closure pattern as one correcting simple field errors.
Use the findings to improve clean claim performance and A/R prioritization. Each recurring pattern should lead to a concrete change, a responsible person, and a follow-up check.
Frequently asked questions
Is every adjustment a denial?
No. Remittances can include ordinary payment adjustments as well as denied amounts. Classify the actual outcome before adding an account to a denial report or estimating lost revenue.
What if the software does not display the remark?
Retrieve the original remittance and ask the posting or software team where line-level remarks are stored. Preserve the source and investigate whether an import or display issue affects other accounts.
Should staff memorize the common codes?
Familiarity helps, but accurate interpretation depends on context and current usage. Teach employees how to retrieve the source, read the full combination, and document the next action.
Connect posting with resolution
FlowClaim provides payment posting, denial management, and RCM reporting. Request a free billing audit to review how your remittance information becomes follow-up work and management insight.