EFT/ERA Reassociation
Payment and explanation arrive separately: the EFT (electronic funds transfer) through the banking system, the 835 remittance through the EDI path, often days apart. When reassociation fails, cash sits unposted.
The Five Ways It Breaks
Reassociation matches payment to remittance by comparing the CCD+ addenda trace number to the 835's TRN02. The bank does not deliver the CCD+ addenda to the depositor, so the trace number never arrives. One EFT covers many 835s, or one 835 spans many payments, breaking one-to-one logic. Trace values drift in format between the banking and EDI paths: leading zeros, prefixes, truncation. Money and remittance arrive days apart and timing-dependent posting logic creates its own backlog. Payer TRN02 practice varies from the operating rule.
None of these are exotic. Together they are why "unposted cash" is a standing line item rather than an exception.
Matching and Enrollment
A Matching Problem
Reassociation compares two identifiers. It does not require retaining the remittance payload or the payment detail. PNT performs the match and returns the result; the receiving organization's system remains the system of record. This matters because the alternative (an intermediary that holds your remittance history to enable posting) is the same concentration decision in a different costume.
Enrollment Is the Gate
EFT and ERA enrollment is governed by the CAQH CORE EFT & ERA Enrollment Data Rule (vPR.2.0), which standardizes what a payer may require. In practice it remains payer-by-payer and form-by-form, and it is the usual reason an organization has electronic remittance from some payers and paper from others years after "going electronic." Any timeline that treats EFT/ERA enrollment as an afterthought will find it on the critical path.
Frequently Asked Questions
What is EFT/ERA reassociation?
Matching an ACH healthcare payment to its corresponding X12 835 remittance by comparing the reassociation trace number in the ACH CCD+ addenda record to the TRN02 element of the 835. A successful match enables automated posting; a failure sends the payment to manual reconciliation.
Why does reassociation fail so often?
Five common causes: the bank does not pass the CCD+ addenda to the depositor; one EFT covers multiple 835s or vice versa; trace value formatting drifts between the banking and EDI paths; payment and remittance arrive days apart; and payer TRN02 practice varies from the operating rule.
Do you have to store remittances to automate posting?
No. Reassociation is a comparison of two identifiers. The payload does not need to be retained for the match to occur, and the receiving organization's system remains the system of record for the remittance itself.
Why do some payers still send paper remittance?
Usually enrollment rather than capability. EFT and ERA enrollment is governed by the CAQH CORE EFT & ERA Enrollment Data Rule but remains payer-by-payer and form-by-form in practice. Incomplete enrollment is the common reason an organization is electronic with some payers and paper with others.
Transactions and Industries
835 ERA Processing
Reassociation is the hard part: matching the money to the explanation.
Providers
Fewer eligibility denials, faster prior authorization and clean claims that get paid sooner.
Revenue Cycle Companies
Multi-client processing with per-client provenance and no PHI retained across your book of business.
Ready to talk through your use case?
Talk to a Post-n-Track specialist about your data challenges. A direct conversation, starting with what you need.