Following Payments from Remittance to Account Reconciliation
A single remittance can contain payments, denials, adjustments, and recoveries across multiple claims. Payment posting brings those transactions into the appropriate patient accounts, while reconciliation checks whether the amount reported by the payer agrees with the funds received.
Even when the amounts balance, a recovery or adjustment may still need to be traced to an earlier transaction. A difference between the remittance and the deposit calls for a different kind of review. Understanding these distinctions helps maintain accurate financial records and gives follow-up teams reliable account information.
Topics We'll Explore
EOB & ERA Interpretation
Claim payments, denials, adjustments, patient responsibility, and reading remittance details.
EFT Reconciliation & Deposit Balancing
Matching remittance totals to electronic funds transfers, deposits, and payment batches.
CARC, RARC & Adjustment Codes
Adjustment group codes, claim adjustment reasons, remark codes, and payer processing explanations.
PLBs, Recoupments & Retractions
Provider-level adjustments, overpayment recoveries, payment reversals, and their effects on reconciliation.
Primary & Secondary Payment Posting
Coordination of benefits, payer order, and applying payments from multiple insurers.
Unapplied Cash & Posting Exceptions
Unmatched payments, posting discrepancies, account research, and exception resolution.
Specialized Topics & Deep Dives
Focused articles on remittance activity, recoveries, posting systems, automation, and other specialized subjects.
Connecting Payments to the Larger Revenue Cycle
A remittance reflects decisions and transactions that may have begun well before the payment arrived. Understanding how those details connect to earlier claims, corrections, and coverage information helps explain what belongs on an account and what may still need attention.
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.