How to Fix 820 Remittance Mismatches in Finance Reconciliation
You know the feeling. The money hit the bank, the 820 landed in the queue, and the two refuse to agree. Someone in Accounts Receivable is now staring at a spreadsheet at 4:45 on a Friday. Here’s the thing: most 820 mismatches aren’t mysterious. They fall into a handful of repeat patterns. If you sort the problem first, the fix usually gets obvious fast.
This is a working playbook for that. It assumes you already know what an 820 is, so we’re skipping the primer.
Start with the three-way check
Before you blame the trading partner (or your mapping), line up three things:
- The bank deposit or Automated Clearing House detail
- The 820 header (BPR total, plus the TRN trace number)
- The 820 detail (the RMR lines, and any ADX adjustments)
Most teams jump straight to detail-level hunting. Don’t. Figure out which layer is off first. A header-to-bank gap and a header-to-detail gap are completely different problems, and they belong to different people.
The usual suspects
1. Header total doesn’t equal the sum of the detail
Take the RMR paid amounts, subtract the ADX adjustments, and compare to the BPR total. If it doesn’t tie, look at sign handling first. Credit memos and deductions coming through as positives (or the reverse) cause a surprising amount of this. Rounding on multi-currency remittances is the other common one.
Whether the partner’s math or your parse is wrong is worth checking before you send an angry email. Run the raw file through a simple sum. Ten minutes, tops.
2. The 820 and the bank don’t match
Timing is the boring answer, and it’s often the right one. The remittance can land days before or after the funds. Also check for aggregation: some payers roll several remittances into one payment, and some split one remittance across multiple. Use the TRN trace value to tie them together instead of matching on amount alone. Amount-only matching is how you end up applying cash to the wrong customer.
3. Invoice references that don’t match your ledger
The RMR reference comes through as a PO number instead of an invoice number. Or it’s got a prefix you don’t store. Or the leading zeros disappeared somewhere between their ERP and yours. (Honestly, leading zeros cause more grief than almost anything else in EDI.)
Keep a cross-reference table per trading partner for how they format references. It’s dull work, but it pays off every single month.
4. Short-pays with vague adjustment reasons
An ADX line with a reason code that could mean five things is not an explanation. Partners use adjustment reasons inconsistently, and a code that means “pricing” for one retailer means “allowance” for another. Check the partner’s guide, and if it’s still fuzzy, ask them directly. Don’t guess and write it off.
5. Duplicates and resends
Same TRN, same amounts, two files. Somebody resent, or your inbound picked it up twice. If you apply both, you’ve just created an overpayment that will sit in unapplied cash for months. Build a duplicate check on the trace number plus amount before anything posts.
6. Remittance-only files
Not every 820 has money attached. Some are information only, with the funds moving separately. If your process assumes every 820 has a matching deposit, these will look like missing payments when they’re not.
A triage order that saves time
When a mismatch shows up, work through it in this order:
- Confirm the file is complete and not a duplicate
- Check header vs. detail math
- Match TRN to the bank record
- Check invoice references against the ledger
- Review ADX reasons for anything you’d dispute
- Only then escalate to the partner
Steps 1–3 clear a large share of cases without ever contacting anyone. Step 6 should come with evidence attached: file name, TRN, the exact line, and what you expected. Partners respond faster when you make it easy for them.
Fix the process, not just the invoice
Chasing individual mismatches is necessary, but it’s a treadmill. A few habits make the pile smaller over time:
- Log the mismatch type. Even a simple tag (sign error, reference format, timing, unclear adjustment) shows you where the repeat offenders are.
- Keep partner-specific notes. How they format references, how they use ADX, whether they batch. Put it somewhere the whole team can find it.
- Set tolerance rules deliberately. Small rounding differences don’t need a human. But agree on the threshold as a team, and write it down.
- Bring EDI and finance into the same room. Mismatches often sit right on the line between mapping and accounting, and each side assumes it’s the other’s problem. It’s usually both.
One more thing
Some 820s are premium payment files in healthcare, not trade remittances. The reconciliation logic there is different (member-level detail, group-level totals). Don’t reuse a retail playbook on those without checking the implementation guide first. And in general: the partner’s companion guide beats any rule of thumb, including the ones in this post. Version and partner quirks vary.
If your team is spending real hours on this every month, that’s usually a skills-and-process gap rather than a tooling one. It’s exactly the kind of thing we cover in CEDIAP® training at EDI Academy, from reading the raw segments to knowing which questions to ask a partner.