Interpreting Claim Adjustments and Remittance Remarks
A primary insurer issues a payment, leaves patient responsibility, and applies a contractual adjustment. Later, a secondary insurer processes the same service. Posting that second remittance isn't simply adding another payment: the reviewer must preserve the first adjudication, distinguish prior-payer information from new activity, and confirm what balance, if any, remains.
Primary and secondary transactions need to be read together without treating the second payment as a repeat of the first. Coverage order, allowed amounts, prior payments, adjustments, and the COB record determine what belongs on the account.
One Service, More Than One Payer
Primary payment posting records the first payer’s adjudicated payment and adjustments against the correct claim and service lines. Secondary payment posting records a subsequent payer’s adjudication after considering the earlier payer’s processing. A patient may have further coverage, in which case the same principles extend to tertiary payments.
Coordination of benefits establishes which plan pays first and how later payers assess remaining covered amounts. Primary does not simply mean the plan that pays the largest amount, and secondary does not guarantee payment of everything left over. Coverage order and benefits must be established under applicable COB rules and the patient’s plan information. [1]
When and Where This Work Happens
Payer-order information commonly begins in patient access, eligibility, and insurance verification. Billing then assembles the primary claim, captures its adjudication, and prepares the subsequent-payer claim or crossover. Payment posting interprets the resulting ERAs/EOBs and validates that the account retains the correct financial history. AR and patient financial services investigate unresolved coverage and liability questions.
The sequence can change. A crossover may automatically send a Medicare-processed claim to an eligible supplemental insurer, while another claim may require a separate secondary submission. A reversal, corrected claim, retroactive eligibility change, or newly identified primary payer can require an established correction workflow rather than a routine secondary posting. [1]
What Information Must Be Available?
A secondary payment cannot be reconciled reliably from the secondary paid amount alone. The reviewer needs to know which service the payer processed and which components of the original charge have already been accounted for.
Electronic data elements worth recognizing
In an X12 835, CLP describes claim payment information; SVC identifies service-level adjudication; CAS reports adjustment group codes and reasons; AMT can report relevant allowed amounts; BPR and TRN help identify payments and reassociation; and PLB identifies provider-level adjustments. The availability and placement of details depend on the transaction. Revisit the dedicated EOB/ERA and PLB guides for full segment-level treatment.
Interpreting Group Codes, Prior Payments and OA-23
An adjustment reason code (CARC) should be read with its group code, not in isolation. PR describes patient responsibility; CO identifies contractual obligations; OA identifies other adjustments; and PI identifies payer-initiated reductions. The code and accompanying information must be considered under applicable payment and contract rules before any amount is transferred or written off.
OA-23 identifies the impact of earlier payer adjudication, including prior payments and/or adjustments. It is not a new payment, a second write-off to take, or patient responsibility merely because it appears on the secondary ERA. X12 explicitly describes the posting purpose of OA-23: preserving prior financial activity already recorded in AR rather than duplicating it. [2]
OA-23 is not necessarily identical to the primary payment alone, nor is it automatically the sum of every figure printed on the first EOB. It may include prior contractual reductions. X12 also explains that the impact is not invariably the arithmetic sum of all prior payment and contractual reductions in every scenario; the specific adjudication must be evaluated. [3]
The Primary Posting Workflow
- Confirm payer and account. Match identifiers, dates, charges, and service lines to the claim and patient record.
- Review adjudication. Identify actual payer payment, CO and PR adjustments, other group codes, and remarks.
- Check financial reasonableness. Reconcile each line to its charges and validate that adjustment categories reflect the remit and applicable policy.
- Post or route under approved workflow. Preserve line-level accuracy and documented accounting treatment; do not create a patient transfer just to force balance.
- Assess next-payer needs. Check whether the claim should cross over or whether secondary submission requires the primary EOB details.
- Verify resulting account status. The remaining amount may be awaiting another payer, under review, or potentially patient-responsible; the ledger should reflect that distinction.
Worked example: primary adjudication
Fictional outpatient service. A provider bills $500. Primary allows $350, pays $280, applies CO-45 of $150, and reports PR-2 coinsurance of $70. The figures reconcile: $280 + $150 + $70 = $500.
After the primary posts, $70 remains open for COB consideration. That doesn't authorize immediate patient billing when secondary coverage is pending.
The Secondary Posting Workflow
- Validate the secondary claim context. Confirm COB order, service date, and that the correct primary adjudication was transmitted or available.
- Locate primary transactions already recorded. Compare the secondary ERA with the primary EOB and current account history.
- Separate new activity from prior information. Identify OA-23, secondary payments, new CO/PR entries, claim status, and remarks.
- Reconcile at service and claim levels. Ensure totals agree without reposting earlier reductions or using a plug adjustment.
- Match actual cash. Verify the EFT/check associated with the ERA, incorporating provider-level adjustments only when present.
- Validate remaining liability. Consider both adjudications, contract terms, plan benefits, and any additional payer before treating a balance as billable.
- Document exceptions and confirm posting. Trace unresolved differences, route correction to the responsible party, and recheck the ledger.
Worked example: a secondary insurer pays part of coinsurance
Continue the $500 service. Secondary receives the primary adjudication showing $280 paid and $150 contractual reduction. Secondary adjudicates an additional $50 payment and reports $20 as remaining patient responsibility in this illustrative arrangement.
The secondary 835 equation for this example is $500 = $430 OA-23 + $50 new payment + $20 PR. Across the two remittances, the provider has $280 + $50 = $330 in insurer payments, $150 in contractual adjustments, and $20 remaining potentially patient-responsible. This illustrates one possible COB outcome, not a universal secondary reimbursement formula. [2]
What If the Secondary Payer Uses a Different Allowed Amount?
A secondary payer can calculate benefits under a different schedule from the primary payer. Do not assume the allowed amounts must match, that the difference automatically becomes a new adjustment, or that the secondary payer should always pay the primary PR amount. Read the secondary payer’s own adjudication, compare the prior payer details provided, and apply the relevant plan and contract rules.
Illustrative comparison
From these four figures alone, a reviewer cannot reliably reconstruct all of the secondary CAS entries or conclude that the patient owes $16. The relevant OA-23, secondary adjustments, benefit rules, and account history are still needed. Differences in displayed allowed amounts are clues for review, not permission to redistribute money by intuition.
Practical Exception Scenarios
Scenario A: OA-23 mistakenly posted as a second contractual adjustment
The primary payment and CO adjustment are already recorded. An automated routine reads the secondary OA-23 and reduces the account again. A credit appears even though no additional cash was received. The reviewer compares the primary and secondary remittances, identifies the duplicate ledger impact, and routes an authorized correction. The posting map should be reviewed by the designated configuration or control owner.
Scenario B: Secondary remittance total does not match EFT
An ERA shows $420 across its claim payments, but the actual EFT is $370. Rather than lowering patient responsibility or altering service payments by $50, the reviewer examines BPR/TRN information and PLB or other documented remittance activity. A $50 provider-level recovery, if documented, would reconcile the EFT: $420 − $50 = $370. The provider-level transaction is treated according to its own accounting workflow, not assigned arbitrarily to one patient.
Scenario C: Secondary pays zero
Zero payment isn't equivalent to zero processing. The secondary may leave a contractual amount, assign or change responsibility, request further information, or deny a service. Review the status, adjustment group/reason codes and remarks. The account should not be billed or written off merely because the secondary payment is zero.
Scenario D: Secondary coverage is added after the primary was posted
Verify the coverage period and payer order before submission. Review whether the prior payer information is correct and whether a corrected or new secondary claim is required. A payer-order change may require additional review of the primary claim, not just a second transaction posted to the existing balance.
Scenario E: A payment is retracted and later reapplied
Identify the original payment, reversal, replacement adjudication, and actual deposit effects. Preserve transaction history. A retraction shown on a remittance may not equal a new withdrawal from cash at that moment; different cycles can contain distinct adjudication and recovery events. The PLB and recoupment guide covers that sequence in detail.
Troubleshooting and Corrective Actions
A practical investigation sequence
First establish the cash amount and payer identity. Then reconcile the primary ledger to its EOB; identify the secondary remittance’s prior-payer representation; and isolate only new secondary cash and adjustments. Finally, validate any open balance under applicable rules. If an essential source record is missing, hold the exception or escalate instead of manufacturing an offset.
Posting Controls and Financial Consequences
Two controls are necessary: cash balancing confirms the received money is represented correctly, while account-level validation confirms that money and adjustments are assigned to the correct claims and services. A deposit may balance while two patient accounts contain equal and opposite errors. Likewise, a secondary 835 can balance mathematically while prior payments are duplicated in the patient ledger.
Recurring patterns warrant sample-based review: identify affected payers and dates, compare source EOB/ERA transactions with ledger postings, estimate the verified impact, and document escalation. Changes to write-off rules, payer contracts, or automation mapping belong to authorized personnel and should be tested before deployment. The future revenue integrity and automation guides will expand on systemic controls.
Posting and COB Review Checklist
- Confirm patient, account, service and payer order.
- Verify primary adjudication is final for the version being processed and accurately posted.
- Check whether crossover or separate secondary submission occurred.
- Review secondary service lines, OA-23, new payments, CO/PR/OA/PI and remarks.
- Do not repost prior payer cash or contractual reductions.
- Reconcile claim/service detail without substituting plug adjustments.
- Verify actual EFT against remittance totals and provider-level activity.
- Confirm whether further coverage exists before assigning final patient responsibility.
- Investigate zero-pay, reversed, or corrected remittances individually.
- Document corrections, outstanding issues and authorized escalation; validate the final ledger.
How It Connects to the Rest of the Revenue Cycle
Primary and secondary posting depends on accurate registration and insurance order, supported claims, correctly transmitted prior adjudication data, and sound cash controls. It feeds accounts receivable, denial follow-up, patient balance validation, refunds, and financial reporting. Related foundational guides explore EOB/ERA interpretation, EFT balancing, adjustment codes, PLBs, and unapplied cash in more detail. Those topics support this workflow, but none replaces validating each payer’s distinct adjudication.
References and Further Learning
These resources support the standards and examples discussed above. Confirm current applicability to the plan, transaction version, and organization before using them operationally.
References
Additional Learning
Educational Disclaimer
Revenue Cycle Uncovered is an independent educational resource. Content is provided for general informational purposes and does not represent the policies, practices, or positions of any employer or organization. Workflows, payer requirements, regulations, and operational practices may vary. Information should be independently verified when applied to specific situations.