Here is the conclusion up front: when the 810 invoice and the bank deposit do not match, do not call the customer's accounts payable team first. Read the EDI 820 payment remittance advice first. I have seen this pitfall three times. Three times, the reconciliation team skipped the 820, tried to force-match invoices against bank statements for an entire afternoon, and got nowhere — only to discover the customer had already written the deduction reason clearly in the 820. Nobody had looked.

The EDI 820 is the payment remittance advice, and it travels with the 810 invoice. The 810 is the bill you send. The 820 is the customer telling you, after paying, which invoices this payment covers, how much was paid against each one, and what was deducted and why. Without the 820, you know money arrived, but you do not know which invoices it settles.

What an EDI 820 Payment Remittance Advice Actually Contains

Learn the key fields and reading an 820 stops being intimidating.

The first group is identity: payer, payee, payment date, payment method, and payment reference number — a check number or an ACH trace number. This group ties the 820 to the bank deposit.

The second group is invoice-level detail: for each 810 invoice, the invoice number, the PO number, the invoiced amount, and the amount actually paid. One 820 often settles three or four invoices in a single payment. Check line by line: is the invoice number in your receivables, and does the PO number match the order in your system?

The third group is deductions, and it is the group most people skip: deduction amount, adjustment reason code, and a short explanation. The reason code is a standard code — short shipment, pricing discrepancy, freight dispute, return deduction. This group explains why the payment is smaller than the invoice. The common habit is to look only at the total and declare a problem. The reason code usually already has the answer written down.

The fourth group is the summary: total invoiced, total deducted, total paid. The equation is simple — invoiced minus deducted equals paid. Verify it first. If it does not balance, the transmission has a problem.

The 810-820-Bank Reconciliation Chain

The chain is three lines forming one closed loop. Miss one and the reconciliation is not done.

Step one, the 810 goes out. Your WMS or billing system generates the invoice from the contracted rate card. One common landmine sits right here: if the charge lines do not map exactly to the rate card the customer agreed to, the 820 will come back full of deductions. Check the rate card against the customer's PO terms before invoicing.

Step two, the 820 comes back. After paying, the customer sends the 820 explaining which invoices the payment settles and what was deducted. Post every line to receivables: invoice number, amount paid, deduction reason code. Ideally your system matches invoice numbers automatically when the 820 arrives, and anything unmatched goes into a separate exception queue.

Step three, the bank deposit. The amount and reference number on the bank statement must match the summary fields in the 820. Many 3PLs stop at step two and assume they are done, then discover the bank actually received less than the 820 stated. Cross-bank fees and intermediary bank charges can shrink the real deposit.

All three must agree before a payment is closed. Any mismatch and the aging clock keeps running.

Use this table when something does not match. Work it in order:

Check What to verify Common finding
1. Verify the 820 summary Invoiced minus deducted equals paid Totals wrong; ask for a resend
2. Match invoice numbers Every invoice on the 820 exists in receivables Transposed digits, someone else's invoice
3. Read the deduction codes Code and note for every deduction Customer already stated the reason
4. Match the bank statement Actual deposit and reference vs. the 820 Bank fees, intermediary charges, cross-month arrival
5. Check the original 810 Charge lines and rate card for the deducted invoice Wrong rate, wrong quantity, duplicate billing

The Five Most Common Mismatches, in Check Order

Short payment comes first. The customer paid less than invoiced, and the 820 carries no deduction reason code, or a vague one. Check first whether it is a partial payment — the customer may have paid only the invoices that fell due, leaving the rest for next month. Next, check for a percentage holdback, such as paying 90 percent and retaining 10 percent as a quality holdback. Only then suspect the customer miscalculated.

Duplicate deductions rank second. The same deduction appears twice in the 820, or a deduction from last month shows up again this month. Compare this month's deduction lines against last month's records item by item. The same invoice number plus the same reason code twice is almost always a duplicate.

Freight deductions rank third. The customer disputes a freight line — freight charged on an order that was supposed to ship prepaid, or a mismatch between the carrier's bill and the freight you invoiced. Pull the source documents before arguing: the carrier invoice, the quote, and the freight terms in the contract.

Tax differences rank fourth. On cross-state or cross-border orders, one wrong digit in the tax rate throws the whole invoice off. Go back to the original 810, check the tax rate and the taxable base, and then either reissue the invoice or accept the deduction.

Cross-period payment ranks fifth. The customer paid on March 31, the money arrived April 2. Reconciling by payment date leaves March looking short and April looking over. Fix it by booking on the actual bank arrival date and noting the 820 payment date in the memo field.

A 3PL Reconciliation Checklist for Collecting on a Client's Behalf

A 3PL's situation is one layer more complicated than a self-operated warehouse: you run the warehouse for the client, you invoice for the client, and sometimes you collect money for the client. Once money passes through your hands, the boundary of reconciliation responsibility has to be written down.

The go-live night checklist should include these items. First, the contract states who owns reconciliation — the 3PL or the client — and who argues deduction disputes. Second, confirm how the 820 arrives: direct EDI into the system, or an email attachment that someone keys in by hand. Third, every charge line on an 810 must trace back to an original activity record — pick, pack, ship, line by line with evidence — so that when a client questions a charge, you can pull the source document within three minutes. Fourth, put a time limit on deduction disputes, for example five business days from receiving the 820 to finish verification and reply.

Two scenarios make this concrete. The first is a 3PL warehouse in California in the fall of 2023 (illustrative scenario; figures are hypothetical worked examples): one payment settled twelve 810 invoices, and the total came in about 8 percent below the invoiced amount. Reading the 820 line by line revealed three invoices each hit with the same reason code — the customer's system could not match the PO numbers to receiving records. A PO number had been keyed with one wrong digit, the 810 went out against the wrong PO, and the customer's system deducted automatically. Fix the PO number, reissue three invoices, and the next payment arrived in full.

The second scenario is cross-month arrival (illustrative scenario; figures are hypothetical worked examples): a 3PL doing e-commerce fulfillment had a client who paid on the 25th of each month, but the bank deposit usually landed on the 1st or 2nd of the following month. Finance booked by payment date, so at every month-end a payment hung in mid-air, the aging report showed it as overdue, and collection emails went out. Switching to booking by actual bank arrival date ended the false alarms. The suspended amount each month ran to roughly 4 to 5 percent of monthly billings — not large, but it happened every single month.

Here is the counterintuitive judgment: when the 810 and the 820 do not match, most of the time do not suspect the customer first. Check your own 810. In my experience, more than seven in ten discrepancies start on our side — a rate card that was never updated, a copied quantity, a mistyped PO number, a wrong tax rate. Your invoice often gave the customer the reason to deduct in the first place. Get the 810 right and the 820 reconciliation workload drops by half.

One thing you can do tomorrow: pull every 820 received in the last three months, run them through the table above, and count how often each of the five mismatch types appears and which reason codes repeat. Once you have the counts, you will know whether to fix the invoicing process, the receiving entry, or the deduction conversation with the client. An 820 is not just a payment notice. It is a health report on the quality of your invoicing.

By Lin Xiao, WMS Implementation Consultant