How it’s supposed to work
The 835’s TRN segment carries a trace number. The same number rides the ACH payment’s addenda record. The 835’s BPR10 carries the payer’s originating company ID, matching the ACH entry. The CAQH CORE rules adopted under the ACA require payers to support this linkage (45 C.F.R. § 162.1602; CAQH CORE).Why it breaks anyway
- Your bank hides the addenda. Many banks don’t surface ACH addenda at all, or only as a treasury upsell. The trace number exists but you can’t see it.
- Timing skew. The 835 arrives days before or after the money.
- One-to-many. Payers batch or split payments across remittances.
- Paper. A check plus EOB has no TRN. Matching falls back to amounts, dates, and check numbers. See Lockboxes.
- Vendors in the middle. With aggregators (Zelis, ECHO, Optum), the bank descriptor is the vendor’s name, not the payer’s. “ECHO Health” in your feed can be any of a dozen payers.
What unreconciled reassociation costs
Three failures go undetected: missing money (an 835 posted as paid whose EFT went elsewhere, the classic post-bank-switch injury), unexplained deposits (unapplied cash distorting the books), and silent shortfalls (PLB recoupments and card fees absorbed without a decision).What good looks like
Every payer deposit matched to its remittance and vice versa, weekly or continuously, with a short exception list someone owns. This is rule-based matching that should not be a human’s job.Lemma aside: Lemma is the bank account, so it sees the ACH addenda, parses the remittances, and matches them automatically. Only true exceptions surface (docs).