EDI 820 Remittance Advice for Freight Payments and Cash Application

A carrier's bank statement shows one ACH credit of $48,609.00 from a shipper. The carrier billed that shipper $50,960.00 across 26 freight bills last month, so cash application has $2,351.00 to explain and no idea which PRO numbers were shorted or why. The payment sits in unapplied cash for three weeks while a collector emails the shipper's accounts payable team, and the open freight bills age past 60 days on the receivables report.

The shipper did send the explanation. It arrived as an X12 820 remittance advice that nobody had mapped, with every short pay coded and tied to a PRO. Once a carrier maps the 820 to its receivables ledger, most payments apply themselves, and the short pays land in a dispute queue with a reason code, an amount and the 180-day clock already running.

• What this guide explains: how the 820 travels with or apart from the money, the segments cash application uses, and the adjustment codes freight short pays rely on.
• What it adds: a sample freight 820, a timestamped unapplied-cash incident, India's TDS deduction inside a transporter payment, and worked remittances in dollars and rupees.

How an 820 travels with the money, or separately from it

The 820 Payment Order/Remittance Advice can order a payment, describe one, or do both. The first data segment, BPR, tells the receiver which: element BPR01 carries a transaction handling code, and that code decides whether cash application should expect the detail inside the bank file or as a separate EDI document.

• Code C, payment with remittance: the payment and the remittance detail travel together, typically in an ACH CTX entry.
• Code I, remittance only: the 820 is information; the money moves on its own rail and must be matched by amount and trace number.
• Code D, payment only: a payment order without the open-item detail, which leaves the carrier to ask for it.
• Codes U and X, split: the payer, or the bank at its option, sends payment and remittance by different paths.

BPR04 names the payment method, such as ACH, CHK for a check or FWT for a Federal Reserve wire, and BPR05 names the ACH format, such as CCP for a CCD entry with addenda or CTX for a corporate trade exchange. Nacha's ACH developer guide describes CTX as supporting up to 9,999 addenda records, each with an 80-character payment-related information field, which is room for a complete X12 820.

Carrier cash application matches an X12 820 to the bank credit through BPR02, the payment amount, and TRN02, the trace number; when BPR05 is CTX, Nacha allows up to 9,999 addenda records of 80 characters each, so a remittance covering 500 freight bills can arrive inside the ACH entry itself.

The split cases cause most unapplied cash. When BPR01 is I, the remittance can arrive a day before or after the funds, and the carrier's bank may truncate CTX addenda when it reports the deposit. Store the TRN02 trace number from each 820 and from each bank deposit, and match on that value before trying amount and date.

Reading the segments a carrier's cash application team uses

A freight 820 has a short heading and a repeating detail loop, and cash application only needs about a dozen elements from it. The heading identifies the payment and the parties; the detail lists each freight bill being paid and any adjustment against it.

Freight payers often batch many PROs into one ENT loop for a single payee. When a third-party freight payment provider pays on behalf of several shippers, the ENT loop and its NM1 segments identify each underlying shipper, which matters because the carrier's customer is the shipper, not the provider.

RMR lines that match PRO numbers, bills of lading and invoices

Every paid freight bill should appear as one RMR segment with a reference the carrier can find in its billing file. The reference qualifier in RMR01 decides which number that is, and agreeing it during onboarding prevents most matching failures.

• CN, carrier's reference number: the PRO or carrier invoice number, the best key for an LTL or truckload carrier.
• BM, bill of lading number: useful when the shipper's freight audit keys on its own BOL, but one BOL can span several PROs.
• IV, seller's invoice number: right for a consolidated monthly freight invoice covering many shipments.
• PO, purchase order number: common in retail payers, and a poor key for freight because many loads ship against one PO.

The sample below shows a payment of $48,609.00 by ACH CTX for four of the 26 PROs, with three adjustments. Amounts in ADX01 are signed: a negative value reduces the payment, as the 820 standard notes for that element. The routing and account numbers are placeholders.

ST*820*0001~
BPR*C*48609.00*C*ACH*CTX*01*071000013*DA*1234567890*1362811290**01*021000021*DA*9876543210*20261112~
TRN*1*0007712345*1362811290~
N1*PR*ACME HOME GOODS INC~
N1*PE*NORTHLINE CARRIERS INC~
ENT*1~
RMR*CN*4471029*PI*1840.00*1840.00~
RMR*CN*4471030*PP*1615.00*1790.00~
ADX*-175.00*TI*CN*4471030~
RMR*CN*4471031*PI*0.00*1250.00~
ADX*-1250.00*19*CN*4471031~
RMR*CN*4471032*PP*1028.40*1811.80~
ADX*-783.40*44*CN*4471032~
SE*14*0001~
# Remaining 22 RMR lines and one fuel surcharge adjustment omitted.
# Check: sum(RMR04) for all 26 lines must equal BPR02 = 48609.00

The check in the last line is the most useful single validation a carrier can run on arrival. If the paid amounts in RMR04 do not sum to BPR02, the remittance and the money disagree, and nothing should auto-apply until a person looks. The 820 should also be acknowledged with a 997 or 999; our guide to the EDI 997 functional acknowledgment covers that loop.

Short-pay codes: ADX reason codes behind freight disputes

The adjustment reason code in ADX02 is what turns a short pay into a workable dispute. X12 data element 426 holds more than 600 codes, so carriers should agree a short list with each payer and reject anything outside it during testing.

ASC X9 Technical Report 42, the core adjustment reason code list developed with the Remittance Coalition, picked a subset of element 426 for common use and wrote fuller definitions. Several of its codes fit freight directly, and the list is a sensible starting point for a carrier's own code table.

• TI, transportation issue: covers detention, a missed delivery appointment and volume or weight-break disputes.
• SF, shipping and freight charge: freight charges not otherwise listed, including an incorrect delivery charge.
• Q6, contract price error: pricing discrepancy against a contract, which TR 42 says includes a freight surcharge.
• 19 and 86, duplicates: 19 for a duplicate bill from the vendor, 86 for a duplicate payment the payer is recovering.
• 44, required documents missing: packing slip, bill of lading or proof of delivery not received.
• 03, extension error: an arithmetic error such as rate times weight not equalling the line amount.
• L7, miscellaneous: deductions not covered by another code, which should be rare.

Where ADX sits also matters. An ADX inside an RMR loop applies to the RMR immediately above it, so the deduction belongs to that PRO. An ADX in the ENT-level loop is an adjustment not netted to any RMR, such as recovery of last month's overpayment, and needs its own reference to make sense.

Freight short pays and the 180-day billing dispute clock

For US motor carriage, federal law sets deadlines on both sides of a billing dispute, and the 820 is often the first written record of the shipper's challenge. A carrier that ignores a coded short pay can lose the right to rebill.

Under 49 U.S.C. 13710(a)(3)(A), a carrier must issue any bill for charges beyond those originally billed within 180 days of the receipt of the original bill to keep the right to collect them. Under 13710(a)(3)(B), a shipper must contest the original or a subsequent bill within 180 days of receiving it. A short pay with an ADX reason code is evidence of when and why the shipper contested.

Freight short pays reported in an X12 820 ADX segment should open a carrier dispute record dated from the remittance, because 49 U.S.C. 13710(a)(3) gives shippers 180 days to contest a bill and carriers 180 days to issue additional charges, and 49 CFR 377.203 sets a default 15-day credit period.

The credit rules give context for discount and late-payment lines. Under 49 CFR 377.203, the credit period starts the day after a freight bill is presented, defaults to 15 days including weekends and holidays, and can be set by tariff to no more than 30 calendar days. If an RMR06 discount or a negative ADX for early payment appears, check that the contract actually offers it before accepting.

Incident trace: one unapplied ACH and a duplicate-payment loop

A single wrong qualifier can turn a clean payment into weeks of reconciliation work and a second payment the shipper later claws back. The trace below comes from a mid-size truckload carrier during its first month on a shipper's 820 programme.

1. 12 Nov, 06:40: Bank file shows ACH CTX credit of $48,609.00, trace 0007712345; the carrier's bank strips addenda beyond the first 20 records, so the receivables system sees only 4 of 26 RMR lines.
2. 12 Nov, 09:15: Auto-match fails because RMR04 for the visible lines totals $4,483.40, not $48,609.00; the full payment posts to unapplied cash under customer ACME01.
3. 13 Nov, 14:30: The shipper's freight audit, seeing PRO 4471031 still open on the carrier's statement, does not recognise its own code 19 rejection and pays the $1,250.00 bill again in the next run.
4. 3 Dec, 11:05: The carrier receives the full 820 by its EDI mailbox after asking for a resend, applies all 26 lines, and finds PRO 4471031 paid once at $1,250.00 against a code 19 duplicate-billing rejection.
5. 10 Dec, 08:00: The next 820 carries ADX*-1250.00*86 at the ENT level to recover the duplicate payment; the carrier now matches remittances from the EDI mailbox on TRN02 and treats bank addenda as a backup only.

The root cause was the assumption that the bank file would carry the whole remittance. The fix took one mapping change and one bank instruction, but the 21 days of unapplied cash had already gone into the month-end receivables ageing reported to the lender.

Withheld tax in the remittance: Indian TDS and US backup withholding

Tax withheld by the payer is a short pay that the carrier must not dispute, so cash application needs to recognise it and book it as tax credit rather than a customer deduction. India and the US handle this very differently, and the X12 core code list has no withholding code, so the trading partner guide must say how it is shown.

In India, a business paying a road transporter deducts tax at source under section 194C of the Income-tax Act, 1961 for amounts credited or paid up to 31 March 2026, and under section 393 of the Income-tax Act, 2025 from 1 April 2026. The rate is 1% for an individual or HUF transporter and 2% for others, with a waiver for transporters who own ten or fewer goods carriages and give a declaration with PAN. Our guide to TDS on transporter payments covers thresholds and the declaration.

Indian transporter remittances should show the tax deducted at source as a separate line, because section 194C, now section 393(1) Table Sl. No. 6(i) of the Income-tax Act, 2025, takes 2% from a company transporter, and CBDT Circular 23/2017 excludes separately stated GST from that base.

Two GST points change the arithmetic. When GST is shown separately on the transporter's invoice, CBDT Circular 23/2017 says TDS is computed on the amount excluding GST. When the shipper pays GST under reverse charge, that tax goes to the government, never appears in the payment to the transporter, and should not be read as a short pay. Our article on GST on goods transport agency services under reverse charge explains which side pays.

In the US, freight payments between businesses usually carry no withholding. The exception is backup withholding: the IRS sets it at 24% of reportable payments where the payee has not given a correct taxpayer identification number. An owner-operator paid without a valid W-9 on file may therefore see a 24% deduction, which also belongs in a tax account, not the dispute queue.

Worked remittance: a US freight payment and an Indian transporter run

The two examples below follow one payment from billed amount to cash posted, with illustrative figures. They show the separate treatment of contestable deductions, which go to a dispute queue, and withheld tax, which goes to a receivable from the tax authority.

The US net is $48,609.00 and the posted entries reconcile: $48,609.00 cash, $1,101.00 in disputed deductions, and $1,250.00 cancelled as a genuine duplicate. The Indian net is ₹4,57,020, with ₹18,400 disputed and ₹9,580 held as a tax credit until it appears in the transporter's annual statement against the shipper's TAN.

Who owns each 820 field, and which matches a machine should make

An 820 crosses at least four teams on each side: shipper accounts payable, the freight audit team, the carrier's billing team and its cash application team. Naming one owner for each field and each decision keeps short pays from bouncing between them.

Most of the matching is arithmetic and should be automatic. Judgement is needed where documents must be read or a commercial decision made, and those tasks benefit from software that prepares the case without closing it.

Onboarding checklist for a new 820 trading partner

Most 820 problems are settled, or created, during the first two weeks with a new payer. A short written agreement on references, codes and delivery path, followed by a parallel test against real deposits, avoids the unapplied-cash month described above.

For the envelope checks, our article on ISA and GS control numbers explains duplicate detection. The freight audit checklist covers the shipper's earlier decision of whether a charge is valid; this article picks up after that decision, when the result reaches the carrier as money and codes. Both sit in the logistics and supply chain library.

If you are planning to automate cash application for freight receivables, or to send 820s to your carriers, we can help scope the mapping, code tables and test plan. Send your current remittance formats and volumes through our request for proposal form.