EDI 820 Transaction Set: Segments, Transmission, and Acknowledgment

The EDI 820 transaction set is the ANSI X12 electronic document a buyer sends to authorize a payment and tell the recipient which invoices that payment covers. It bundles bank routing instructions with line-by-line remittance detail in a single transmission, so the money and the “what it’s for” travel together and feed directly into both sides’ accounting systems.1Federal Reserve Financial Services. Fundamentals of Financial EDI

Where the 820 Sits in the Payment Cycle

The 820 is the last link in a chain of EDI documents. A buyer typically sends an 850 Purchase Order to a seller. The seller ships, then transmits an 810 Invoice back. Once accounts payable approves that invoice, the system generates an 820 that authorizes payment and carries the invoice numbers from the 810 forward as references. In industries where terms attach to the purchase order rather than a separate invoice, the 820 may reference the 850 directly.

The payment itself usually moves through the ACH network as a CTX (Corporate Trade Exchange) entry. A CTX can carry up to 9,999 addenda records of 80 characters each, which is enough room to embed the full 820 remittance detail alongside the banking instructions.1Federal Reserve Financial Services. Fundamentals of Financial EDI That reference chain is what makes automated matching work on the receiving end: incoming dollars tie to specific open receivables without anyone looking up invoices by hand.

The Segments That Make Up the File

An 820 is built from defined segments, each handling a specific piece of the payment. Mapping errors at this level are the most common reason transmissions fail, so it helps to know what each one does.

BPR: The Payment Header

The BPR (Beginning Segment for Payment Order/Remittance Advice) carries the total payment amount, the effective date the funds should clear, and the payment method — ACH, wire, or check — along with the originator’s and receiver’s bank account details.2Defense Finance and Accounting Service. EDI 820 Implementation Guide If the BPR total doesn’t match the sum of the individual line items below it, the entire file is rejected.

TRN: The Trace Number

The TRN segment assigns a unique reference number so both the payer and the bank can track the transaction through the system.2Defense Finance and Accounting Service. EDI 820 Implementation Guide When a payment goes missing, the trace number is the first thing a bank will ask for.

N1: Party Identification

The N1 segment identifies who is paying and who is being paid. It captures legal entity names, addresses, and identification codes for the payer, the payee, and in some cases a paying office or intermediary bank.2Defense Finance and Accounting Service. EDI 820 Implementation Guide Financial regulations require clear identification of every entity involved in a funds transfer, so incomplete N1 data can trigger compliance holds.

ENT: Grouping by Entity

The ENT segment organizes the file into logical groupings when one payment covers multiple departments, subsidiaries, or cost centers.2Defense Finance and Accounting Service. EDI 820 Implementation Guide A parent company settling invoices for three divisions in one consolidated transmission uses ENT segments to keep each division’s line items separate.

RMR and REF: Invoice-Level Detail

The RMR (Remittance Advice Accounts Receivable Open Item Reference) segment is where individual account-level payment data lives. Each RMR loop carries the dollar amount applied to a specific account, and the sum of all RMR amounts must equal the total in the BPR. When they don’t balance, most translation software flags the file before it leaves the sender’s system.

Inside each RMR loop, REF segments carry the reference numbers that tie the payment to specific documents: invoice numbers, cross-references back to the 810, and account identifiers. These references are the entire reason the 820 exists as something more than a bank transfer. Without them, the recipient sees money arrive with no way to know which invoices it clears.

ADX: Payment Adjustments

Payments rarely match invoices to the penny. The ADX segment uses standardized reason codes to explain why a payment is more or less than the invoiced amount, covering things like freight charges, recoupment of overpayments, interest owed, and early-payment discounts.2Defense Finance and Accounting Service. EDI 820 Implementation Guide A buyer taking a two-percent discount for paying within net-10 terms includes an ADX segment with the discount code and the deducted amount. The recipient’s system reads the code and adjusts the open balance automatically.

TXI: Tax Information

The TXI segment handles tax-related data in the remittance: type of tax, jurisdiction, and amount. It matters most in industries where sales tax, use tax, or VAT has to be tracked at the transaction level for audit purposes. Mistakes here surface months later during a review.

What You Need Before You Can Send One

Before generating an 820, you need the recipient’s nine-digit ABA routing number and bank account number.3American Bankers Association. ABA Routing Number These are typically exchanged during the trading partner agreement process, where both sides agree on technical specifications, communication protocols, and the legal obligations governing their electronic transactions. You’ll also need the specific invoice numbers, purchase order numbers, and any credit memo identifiers the payment covers.

Most organizations pull these values directly from their ERP system using EDI translation software rather than keying them by hand. A single wrong digit in a routing number means the payment bounces. The technical specifications for how your internal data maps to EDI segments come from the implementation guide provided by your trading partner or industry clearinghouse. These guides run anywhere from 50 to 200 pages and define exactly which segments are required, which are optional, and how each data element must be formatted.

When the 820 triggers an ACH payment, the file must comply with the Nacha Operating Rules governing the ACH network. ACH files use a fixed-width ASCII format with each line exactly 94 characters, alphanumeric fields left-justified and padded with spaces, numeric fields right-justified and padded with zeros.4Nacha. ACH File Overview Files that don’t meet these formatting requirements get rejected by the originating bank, and rejected entries typically incur return fees.

How the File Gets Transmitted

Once an 820 is assembled and validated, it needs a secure path to the recipient. Three transport methods dominate.

A Value Added Network (VAN) acts as a private electronic mailbox. You drop the file in your outbound folder, the VAN routes it to the recipient’s inbox, and both parties pick up files on their own schedule. VANs handle protocol translation and provide an audit trail, which is why they’ve been the default for decades. Per-document fees typically range from a few cents to about a dollar depending on volume, with monthly costs starting around $50 for low-volume users.

AS2 (Applicability Statement 2) provides a direct, encrypted connection between trading partners over the internet, cutting out the VAN. It uses digital certificates for authentication and sends back a signed receipt called an MDN (Message Disposition Notification), creating a non-repudiation trail. Many large retailers and manufacturers mandate AS2 in their trading partner agreements. Secure FTP (SFTP) is the third option, offering encrypted file transfer without the receipt infrastructure of AS2. Your trading partner agreement dictates which method to use.

Regardless of transport method, the Gramm-Leach-Bliley Act requires financial institutions to maintain an information security program with administrative, technical, and physical safeguards for customer data.5Federal Trade Commission. Gramm-Leach-Bliley Act Because 820 files contain bank account and routing numbers, companies transmitting this data fall within that requirement. If you’re outsourcing EDI to a third-party provider, your agreement with that provider should address how they protect this data in transit and at rest.

Confirming the File Was Accepted

Sending an EDI file and knowing it arrived correctly are two different things, and X12 handles them with two separate acknowledgment documents.

The 997 Functional Acknowledgment fires back almost immediately to tell the sender whether the file met the syntactical requirements of X12: correct segment structure, valid data types, proper envelope formatting. It does not confirm the data makes business sense or that the payment will be processed. The 997 explicitly does not cover the semantic meaning of the transaction.6Defense Logistics Agency. 997 Functional Acknowledgment A file with valid structure but an invalid purchase order number passes the 997 check and fails downstream.

That’s where the 824 Application Advice comes in. The 824 reports the results of the receiving application’s business-level edit checks: duplicate invoices, invalid account numbers, purchase orders that don’t exist in the receiver’s system, amounts that don’t match.7Defense Logistics Agency. 824 Application Advice Not every trading partner sends 824s; many handle business-level rejections through email or portal notifications instead. When available, the 824 closes the gap between “received” and “accepted.”

A 997 rejection means the file never reached the application layer, so you fix the syntax and resend. An 824 rejection means the data was readable but wrong, so you correct the source data in your ERP and regenerate the 820.

Interest, Discounts, and Other Adjustments

When the buyer is a federal agency, late payments trigger mandatory interest penalties under the Prompt Payment Act. The interest rate for January through June 2026 is 4.125%, calculated on a 360-day year from the day after the payment due date through the date the payment is actually made.8Bureau of the Fiscal Service. Prompt Payment9eCFR. 5 CFR 1315.10 – Late Payment Interest Penalties The interest shows up in the ADX segment of the 820 with the appropriate reason code, so the vendor’s system can book the interest income automatically.

In the private sector, late payment penalties are set by contract rather than statute. Terms like “1.5% per month on past-due balances” are common, and when a buyer applies an early-payment discount or a seller charges a late fee, those adjustments flow through the ADX segment the same way. The standardized reason codes replace the phone calls that used to happen when a vendor received a payment that didn’t match the invoice.

Healthcare Premium Payments and the 820 vs. 835

The 820 has a specialized role in healthcare: plan sponsors (employers providing health benefits) use it to transmit premium payment information to insurance carriers, communicating premium amounts, enrollment counts, and adjustments tied to member additions or terminations during the coverage period.

This is distinct from the EDI 835, which flows in the opposite direction. The 835 Healthcare Claim Payment/Advice moves from a health plan to a healthcare provider, explaining how claims were adjudicated and what the plan is paying. The 820 moves from the employer to the health plan. Different parties, different business function. Confusing the two during implementation is common.

Onboarding a New Trading Partner

Getting 820 transactions running with a new partner is not a flip-the-switch exercise. The typical onboarding cycle runs six to ten weeks, and the timeline has less to do with technology than with how quickly both sides align their data.

  • Weeks 1–2: Your EDI team or provider reads the partner’s implementation guide and builds the initial field mapping between your ERP’s data fields and the required 820 segments.
  • Weeks 2–4: Internal testing. You generate sample 820 files, run them through validation, catch mapping errors, and fix them. Expect multiple cycles.
  • Weeks 4–8: Formal certification testing with the partner’s EDI team. They run their own test scenarios against your files, flag issues, and require corrections before signing off.
  • Weeks 8–10: Final certification, production cutover, and the first live transactions. Close monitoring during this phase catches issues that testing missed.

The leading cause of delays is data mapping disagreements. Your system stores an invoice number in one format, the partner’s guide expects another, and reconciling that difference takes longer than anyone estimates. Starting the implementation guide review before the trading partner agreement is finalized shaves time off the overall timeline.

The Shift Toward ISO 20022

The X12 820 has been the dominant format for electronic remittance in the U.S. for decades, but the global financial messaging world is moving toward ISO 20022, an XML-based standard that is more readable and more granular than X12. The Fedwire Funds Service is implementing ISO 20022 interoperability changes on November 16, 2026, including a shift to structured postal address formats and enhanced investigation messages.10Federal Reserve Financial Services. Fedwire Funds Service Upcoming Releases

For businesses currently using the 820, migration isn’t immediate. ACH-based payments using the CTX format will continue to work. One longstanding criticism of the 820 is that implementations vary so widely between trading partners that the “standard” is only loosely standard. ISO 20022’s self-describing XML tags make the data more intuitive (a field labeled “InstructedAmount” needs no implementation guide to interpret), and the format supports richer remittance detail than X12 can practically carry.11Nacha. Introduction to ISO 20022 for US Financial Institutions Companies building new EDI infrastructure should factor in whether their translation software and VAN can handle ISO 20022 alongside X12, because running both in parallel is the most likely near-term reality.