Executive summary. Header totals can reconcile perfectly while individual claim lines sit misapplied, unpaid, duplicated, or adjusted underneath them.
Definition
Line-level remittance matching links a payment or adjustment detail to the specific claim and service line it resolves.
Use stable transaction identity
Match on payer control references, claim references, service dates, amounts, and line identifiers where they are available. Amount alone is weak evidence, because repeated amounts are ordinary in pharmacy and clinical billing.
Every match should carry a confidence classification and stay reviewable. A forced match is a conclusion somebody reached, not a fact the remittance supplied.
Treat unmatched records as work
An unmatched remittance line and an adjudicated claim with no payment line are different exceptions with different causes. Give them separate queues and separate aging rules.
Preserve the original remittance file next to the parsed result. When a parser is corrected or a payer sends a replacement, you can replay it without losing the first interpretation.
Frequently asked questions
Does a balanced EFT prove every claim was paid correctly?
No. It proves the payment total agrees with its deposit or remittance total. Line-level allocation is a separate control.
Referenced standards and further reading
- CMS: Medicare Claims Processing Manual ↗Centers for Medicare & Medicaid Services
Related articles
Revenue integrity and reconciliation →