X12 transaction code
EDI 820 Payment Order/Remittance Advice (X12 820)
EDI 820 is the X12 Payment Order/Remittance Advice transaction set, used when payment instructions or allocation details are ready. The buyer (payer), or the buyer's bank on its behalf, sends the 820 to the supplier (payee). Plan sponsors also use it to send premium payments to health insurance plans.
- Standard
- X12
- Code
- 820
- Partner references
- 35
At a glance
EDI 820 at a glance
What the 820 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 820 Payment Order/Remittance Advice |
|---|---|
| Business record | Payment or remittance record |
| Who sends it to whom | The buyer (payer), or the buyer's bank on its behalf, sends the 820 to the supplier (payee). Plan sponsors also use it to send premium payments to health insurance plans. |
| When it is sent | The buyer's accounts payable run executes a payment against one or more supplier invoices and releases the funds by ACH, wire, or check. |
| Match on | Payment reference, invoice references and amounts applied |
| Partner references | 35 trading partners in this directory |
| Related documents | X12 810 Invoice, X12 812 Credit/Debit Adjustment |
Key segments in an EDI 820
The business segments that appear in at least half of the 60 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| BPR | Beginning Segment for Payment Order/Remittance Advice | To indicate the beginning of a Payment Order/Remittance Advice Transaction Set and total payment amount, or to enable related transfer of funds and/or information from payer to payee to occur. | 60 of 60 |
| ENT | Entity | To designate the entities which are parties to a transaction and specify a reference meaningful to those entities. | 60 of 60 |
| RMR | Remittance Advice Accounts Receivable Open Item Reference | To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail. | 60 of 60 |
| DTM | Date/Time Reference | To specify pertinent dates and times. | 58 of 60 |
| N1 | Party Identification | To identify a party by type of organization, name, and code. | 57 of 60 |
| REF | Reference Information | To specify identifying information. | 56 of 60 |
| TRN | Trace | To uniquely identify a transaction to an application. | 41 of 60 |
| CUR | Currency | To specify the currency (dollars, pounds, francs, etc.) used in a transaction. | 31 of 60 |
Stacksync connects EDI documents such as the X12 820 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 820 mapping and validation
X12 820 Payment Order/Remittance Advice is used when payment instructions or allocation details are ready. Preserve payment reference, invoice references and amounts applied so the payment or remittance record in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | payment or remittance record payment reference, invoice references and amounts applied |
|
| Update the receiving system | Processing the payment or remittance record ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the payment or remittance record Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 810 Invoice
accounts-receivable or accounts-payable invoice: a bill is ready for the buyer to process.
- X12 812 Credit/Debit Adjustment
credit or debit adjustment: a financial difference needs a documented adjustment.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when payment instructions or allocation details are ready. Name the operational owner of the payment or remittance record and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map payment reference, invoice references and amounts applied. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic payment or remittance record data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful payment or remittance record processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 820 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic payment or remittance record data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out payment or remittance record without processing it twice.
Document structure
X12 820 Payment Order/Remittance Advice at the element level
The X12 820 reference contains 27 segment entries and 88 data elements; 45 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 27
- Data elements
- 88
- Mandatory elements
- 45
| Segment | Elements | Mandatory |
|---|---|---|
| BPR | 15 | 4 |
| REF | 3 | 1 |
| DTM | 2 | 1 |
| N1 | 2 | 1 |
| N2 | 1 | 1 |
| N3 | 2 | 1 |
| NM1 | 5 | 2 |
| ADX | 4 | 2 |
- Transaction Handling Code
- Monetary Amount
- Credit/Debit Flag Code
- Payment Method Code
- Reference Identification Qualifier
- Date/Time Qualifier
- Entity Identifier Code
- Name
Find your trading partner for X12 820
35 partners, 60 channels. Choose a channel to inspect its listed document reference and implementation context.
- 7-Eleven
- 7-Eleven (SEDC: Seven Eleven Distribution Company)
- Ace Hardware
- Albertsons (Safeway)
- ALLPRO Corporation
- Amazon
- Ashley Furniture Industries, LLC
- Core-Mark (via SPS Commerce)
- Costco
- Dillard's Department Stores, Inc.
- Do It Best Hardware
- Dollar General Corporation
- Granite City Electric
- JCPenney
- Joann Stores
- John Deere John Deere (Thibodaux -T8) (ISA ID: 008473506)John Deere (AG) (ISA ID: 149825353)John Deere (SP) (ISA ID: 557074379SP)John Deere (Engines) (ISA ID: 021688858)John Deere (ISA ID: 249619198)John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773)John Deere (Kernersville) (ISA ID: 557074379)John Deere (M3) (ISA ID: 812912349)John Deere (Dubuque and Davenport) (ISA ID: 833123370)John Deere (Reman- SE) (ISA ID: 010678766)
- John Deere Mexico
- Loblaw Companies Limited
- Lowe's
- Macy's
- NEXCOM (Navy Exchange Service Command)
- Nordstrom
- Orgill, Inc.
- PetSmart
- PFG Customized Distribution
- PFG PerformanceFoodservice North
- Raley's Supermarkets
- Rehlko
- Rite Aid
- Sobeys Canada
- Target
- The Home Depot
- Walgreens
- Wesco
- Winn Dixie
Catalog breakdown
Where X12 820 Payment Order/Remittance Advice appears in this catalog
The largest groups of classified 820 catalog entries are in retail, grocery & food and building & hardware.
By industry
- retail 16 channels
- grocery & food 13 channels
- building & hardware 10 channels
- agriculture 10 channels
- apparel & footwear 4 channels
- healthcare & pharma 2 channels
By network
- SPS Commerce 5 channels
- Epicor Eclipse 1 channel
- InterTrade 1 channel
- Rithum 1 channel
- Saicits 1 channel
- Ibm Van Old 1 channel
FAQ
EDI 820 questions
What is an EDI 820?
EDI 820 is the X12 Payment Order/Remittance Advice transaction set. Trading partners use it when payment instructions or allocation details are ready. It carries the data for the payment or remittance record, and your system matches it on payment reference, invoice references and amounts applied.
Who sends an EDI 820 and who receives it?
The buyer (payer), or the buyer's bank on its behalf, sends the 820 to the supplier (payee). Plan sponsors also use it to send premium payments to health insurance plans. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 820 sent?
The buyer's accounts payable run executes a payment against one or more supplier invoices and releases the funds by ACH, wire, or check. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 820?
Across 60 partner document references listed here, the business segments that appear most often include BPR (Beginning Segment for Payment Order/Remittance Advice), ENT (Entity), RMR (Remittance Advice Accounts Receivable Open Item Reference), DTM (Date/Time Reference), N1 (Party Identification), REF (Reference Information). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 820 and EDI 810?
The 820 carries the payment or remittance record and is used when payment instructions or allocation details are ready. The 810 carries the accounts-receivable or accounts-payable invoice and is used when a bill is ready for the buyer to process.
What should I map for X12 820?
Start with payment reference, invoice references and amounts applied and the target payment or remittance record. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 820 error handling?
Allocate a partial payment across several invoices and preserve the remaining balances. Keep receipt of remittance information distinct from confirmation that funds settled. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 820?
The directory on this page links 35 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
