Claim adjudication is the payer's processing of submitted claim data under its rules and records. It may produce payment, adjustments, requests, denials, or other statuses. This glossary explains the terms used to interpret that result.
For review rights, use the claims, denials, and appeals glossary. For the difference between an initial rejection and a denial, read claim rejection versus denial.
Adjudication
Definition: Adjudication is the payer's process for evaluating claim data and determining how the claim is handled under the applicable plan and rules.
Real-life example: The payer checks eligibility, coding, authorization, benefits, network status, and submitted information.
Why it matters and what it does: It turns a claim into a processing result. It does not prove that every underlying clinical or contractual issue has been correctly resolved.
Claim status
Definition: Claim status describes where a claim is in the submission or payer process.
Real-life example: A status tool reports received, pending, finalized, rejected, or not found.
Why it matters and what it does: It tells staff what to investigate next. A status is not always the final adjudication.
Clean claim
Definition: A clean claim contains the required information and can be processed without obtaining additional data from the submitter or another source, under the applicable rule.
Real-life example: The payer accepts the claim and processes it without returning a data defect.
Why it matters and what it does: It supports timely processing. A clean claim can still be denied under benefit or coverage rules.
Pended claim
Definition: A pended claim is held for additional review, information, or system processing before final adjudication.
Real-life example: The payer pauses the claim while waiting for records.
Why it matters and what it does: It requires follow-up but is not automatically a denial. Staff should identify the exact pending reason and deadline.
Paid claim
Definition: A paid claim is a finalized claim for which the payer issued some payment.
Real-life example: A remittance reports a payment and one or more adjustments.
Why it matters and what it does: Payment does not necessarily mean the full expected amount was allowed. The claim must be reconciled line by line.
Denied claim
Definition: A denied claim is one the payer processed but did not pay in whole or in part for a stated reason.
Real-life example: The remittance denies a line based on a reported authorization or benefit issue.
Why it matters and what it does: It creates a need to determine whether correction, documentation, appeal, or contractual adjustment is appropriate.
Rejected claim
Definition: A rejected claim fails an intake, format, or data requirement and may not enter full adjudication.
Real-life example: A clearinghouse returns a missing or invalid identifier error.
Why it matters and what it does: It usually calls for correcting accurate data and resubmitting. It should not be appealed as if it were a final benefit denial unless the payer's process says otherwise.
Allowed charge
Definition: The allowed charge is the amount the payer recognizes for adjudication under the applicable plan and provider arrangement.
Real-life example: The remittance compares the billed charge with a lower allowed amount.
Why it matters and what it does: It forms the basis for payment and adjustments. It does not automatically establish the collectible patient balance.
Paid amount
Definition: The paid amount is the money the payer issues for the claim or line after applying its calculation.
Real-life example: The payer subtracts stated cost sharing and adjustments from the allowed amount.
Why it matters and what it does: It must be matched to the remittance and deposited funds. A zero payment can have very different reasons and should not be interpreted without codes and notes.
Contractual adjustment
Definition: A contractual adjustment is a reduction required by an applicable provider agreement or payment arrangement.
Real-life example: A participating provider posts the difference required by its contracted rate.
Why it matters and what it does: It reflects written obligations. Staff should not invent an adjustment merely because a payer labels an amount as nonallowed.
Claim Adjustment Reason Code
Definition: A Claim Adjustment Reason Code, or CARC, states a standardized reason for a financial adjustment on a remittance.
Real-life example: The ERA includes a CARC beside the adjusted amount.
Why it matters and what it does: It gives the broad reason for the adjustment. It may require a related remark code and plan context for full meaning.
Remittance Advice Remark Code
Definition: A Remittance Advice Remark Code, or RARC, supplies additional standardized explanation about claim or line processing.
Real-life example: A remark identifies missing information or a policy detail connected to the adjustment.
Why it matters and what it does: It adds specificity. It should be read with the CARC, group code, claim data, and payer notice.
Claim adjustment group code
Definition: A claim adjustment group code categorizes the general financial responsibility associated with an adjustment.
Real-life example: The remittance uses one group for contractual obligation and another for stated patient responsibility.
Why it matters and what it does: It guides posting but does not override law, contracts, prior payments, or other facts. Patient billing still requires validation.
Provider-level balance adjustment
Definition: A provider-level balance, or PLB, adjustment changes a payment at the provider level rather than attaching only to one claim line.
Real-life example: A remittance includes an offset for a prior overpayment.
Why it matters and what it does: It can make the deposit differ from the sum of current claim payments. Reconciliation must trace the reference and reason.
Recoupment
Definition: Recoupment is a payer's recovery of money it states was previously overpaid, often through refund demand or offset.
Real-life example: A later payment is reduced to recover an earlier amount.
Why it matters and what it does: It affects both cash and claim history. Staff should verify the notice, authority, deadline, appeal rights, and accounting treatment before closing the item.
How do claim outcomes and adjustments connect?
Adjudication is the payer's processing of a claim under its data, plan rules, edits, and agreements. A claim may be rejected before adjudication because the transaction cannot be accepted, pended while information is reviewed, denied under a stated reason, or paid in whole or part. A clean claim generally concerns whether a submission satisfies applicable processing requirements; it is not a promise that every line is covered or payable.
The allowed charge, paid amount, and contractual adjustment answer different questions. The allowed charge is the amount recognized under the payer's method or agreement. The paid amount is what the payer actually issues after its calculations. A contractual adjustment may reflect an enforceable agreement, but staff should not infer a write-off solely from a label on one system screen. Claim adjustment reason codes, remittance advice remark codes, and claim adjustment group codes supply structured context that must be read together with the full remittance and relevant contract.
A provider-level balance adjustment can affect a payment outside a single claim line, and a recoupment can reduce a later payment to recover a previously issued amount. Reconciliation therefore requires matching the claim, remittance, bank deposit, patient account, and any payer correspondence. If totals do not tie, the team should identify the exact claim or provider-level difference before posting. Patient responsibility should be finalized only after the payer result, governing agreements, prior payments, applicable law, and any active dispute are reviewed.
How should adjudication results be reconciled?
Match every claim line to the remittance, payment, authorization, provider agreement, and patient ledger. CMS explains how remittance advice reports adjudication and adjustment codes. The plan's own current notice controls the case-specific result.
This glossary is general administrative information, not legal, accounting, coding, debt-collection, contract, patient-billing, or coverage advice. Adjudication and adjustment rules vary by payer, plan, provider, agreement, claim, state, and date.
