X12 transaction code
X12 820 Payment Order Remittance Advice
X12 820 Payment Order Remittance Advice: explore its business purpose, mapping identifiers, validation tests and 35 partner references across 60 listed channels.
- Standard
- X12
- Code
- 820
- Partner references
- 35
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
X12 820 questions
What is X12 820 Payment Order Remittance Advice used for?
820 is used when payment instructions or allocation details are ready. It carries information for the payment or remittance record. Match it to your business system using payment reference, invoice references and amounts applied.
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.
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.
How does 820 relate to other EDI messages?
X12 810 Invoice; X12 812 Credit Debit Adjustment are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 820 and 810?
820 is used when payment instructions or allocation details are ready. 810 is used when a bill is ready for the buyer to process. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
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.
