X12
Inbound

7 X12 820 Payment Order/Remittance Advice

7-Eleven (Hawaii)
The EDI 820 provides payment remittance details from 7 to suppliers. It includes invoice references, payment amounts, deductions for chargebacks or promotions, and settlement details for accounts receivable reconciliation.
13segments
3loops
5mandatory

Schema Reference

13 segments · X12 820 Payment Order/Remittance Advice

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Interchange Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
BPR Beginning Segment for Payment Order/Remittance Advice
Mandatory Max: 1
BPR01 Transaction Handling Code
M ID 1-2
BPR02 Monetary Amount
M R 1-18
BPR03 Credit/Debit Flag Code
M ID 1-1
BPR04 Payment Method Code
M ID 3-3
TRN Trace
Optional Max: 1
TRN01 Trace Type Code
M ID 1-2
TRN02 Reference Identification
M AN 1-50
REF Reference Information
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-50
DTM Date/Time Reference
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
DTM03 Time
C TM 4-8
DTM04 Time Code
O ID 2-2
N1 Loop
N1 Party Identification
Optional Max: 1
N101 Entity Identifier Code
M ID 2-3
N103 Identification Code Qualifier
C ID 1-2
N104 Identification Code
C AN 2-80
ENT Loop
ENT Entity
Optional Max: 1
ENT01 Assigned Number
O N0 1-6
RMR Loop
RMR Remittance Advice Accounts Receivable Open Item Reference
Optional Max: 1
RMR01 Reference Identification Qualifier
C ID 2-3
RMR02 Reference Identification
C AN 1-50
RMR04 Monetary Amount
O R 1-18
RMR05 Monetary Amount
O R 1-18
REF Reference Information
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-50
DTM Date/Time Reference
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
DTM03 Time
C TM 4-8
DTM04 Time Code
O ID 2-2
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating 7 EDI 820

Stacksync validates, transforms, and delivers your 820 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync syncs incoming 820 Payment Remittances to your accounting system automatically. Payment amounts, deduction breakdowns, and invoice references are mapped to your AR records — making reconciliation fast and accurate.

Business unit variations

7-Eleven
Stacksync syncs incoming 820 Payment Remittances to your accounting system automatically. Payment amounts, deduction breakdowns, and invoice references are mapped to your AR records — making reconciliation fast and accurate.
7-Eleven (Legacy ISA ID: 007347602SLND)
Stacksync syncs incoming 820 Payment Remittances to your accounting system automatically. Payment amounts, deduction breakdowns, and invoice references are mapped to your AR records — making reconciliation fast and accurate.

7 EDI 820 FAQ

Common questions about 820 Payment Order/Remittance Advice transactions with 7.

How long does it take to set up 7 EDI with Stacksync?

Most suppliers are fully connected and processing live 7 EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with 7?

No. Stacksync handles the entire EDI transport layer. We connect directly to 7's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with 7 compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for 7?

Stacksync supports all EDI document types required by 7 — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect 7 EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between 7's EDI network and your system in real time.

What happens when 7 updates their EDI specifications?

Stacksync monitors 7's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.