To start and identify an interchange of zero or more functional groups and interchange-related control segments
NEXCOM (Navy Exchange Service Command) X12 820 Payment Order/Remittance Advice
X12 820 (Payment Order/Remittance Advice) is the EDI transaction exchanged between NEXCOM (Navy Exchange Service Command) (NEXCOM Trans) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 12
- Loops
- 4
- X12 820
- All partners ↗
Transaction context
Where 820 Payment Order/Remittance Advice fits on NEXCOM Trans
- NEXCOM (Navy Exchange Service Command) channels
- 1 of 1
- Trading partners
- 35
- Channels
- 60
1 of NEXCOM (Navy Exchange Service Command)'s 1 channel carries 820
partners across the Stacksync network trade 820
channels network-wide carry 820
Most common alongside 820
The 820 carries payment and remittance information: which invoices are being paid, for how much, and with what adjustments, plus the payment method and banking details. The seller needs this remittance detail to apply cash against open invoices, because the funds themselves often move separately through the ACH network or by wire. The transaction can involve up to four parties: the payer, the payer's bank, the payee, and the payee's bank. Sent by the buyer (payer), or by the buyer's bank on its behalf, to the supplier (payee); it is also used by plan sponsors to send premium payments to health insurance plans.
When it fires: The buyer's accounts payable run executes a payment against one or more supplier invoices and releases the funds by ACH, wire, or check.
Common 820 rejection causes
- Missing or incorrect invoice references in the RMR remittance detail, so the seller cannot match the payment to open invoices and cash application stalls.
- Deduction or adjustment amounts that do not reconcile against the billed amounts, forcing manual research of the discrepancy.
- Errors in the BPR segment's payment amount, method, or banking details, which break the link between the 820 and the actual funds movement.
- Remittance detail arriving decoupled from the ACH payment it describes, leaving the seller to match bank deposits to 820s manually.
Specification summary
X12 820 Payment Order/Remittance Advice at the element level
The X12 820 specification defines 27 segments carrying 88 data elements, 45 of which are mandatory.
- 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 |
Key identifiers in 820
- Transaction Handling Code
- Monetary Amount
- Credit/Debit Flag Code
- Payment Method Code
- Reference Identification Qualifier
- Date/Time Qualifier
- Entity Identifier Code
- Name
Full segment guideline — 12 segments 4 loops · X12 820 Payment Order/Remittance Advice
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
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
To uniquely identify a transaction to an application
To specify identifying information
To specify pertinent dates and times
N1 Loop
To identify a party by type of organization, name, and code
ENT Loop
To designate the entities which are parties to a transaction and specify a reference meaningful to those entities
RMR Loop
To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
ADX Loop
To convey accounts-payable adjustment information for the purpose of cash application, including payer-generated debit/credit memos
Trading partners
10+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
PU Purchase Order PU Purchase Order Acknowledgment PR Product Activity Data IN Invoice RE Request For Routing Instructions RO Routing Instructions SH Ship Notice Manifest IN Inventory Inquiry Advice TR Transportation Carrier Shipment Status Message RE Return Merchandise Authorization And Notification
No trading partner matches your search.
Browse the full directory
NEXCOM (Navy Exchange Service Command) NEXCOM Trans EDI 820 FAQ
Common questions about 820 Payment Order/Remittance Advice on the NEXCOM Trans channel.
What is X12 820 Payment Order/Remittance Advice?
X12 820 (Payment Order/Remittance Advice) is the EDI transaction set used to exchange payment order/remittance advice data. NEXCOM (Navy Exchange Service Command)'s NEXCOM Trans channel requires it from trading partners.
Does NEXCOM (Navy Exchange Service Command) NEXCOM Trans require 820 for trading partners?
Yes, NEXCOM (Navy Exchange Service Command) (NEXCOM Trans) supports X12 820 Payment Order/Remittance Advice. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate NEXCOM (Navy Exchange Service Command) 820 with Stacksync?
Most companies go live with NEXCOM (Navy Exchange Service Command) 820 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 820 on NEXCOM Trans?
On NEXCOM Trans, X12 820 is typically exchanged alongside 850 Purchase Order, 810 Invoice, 856 Ship Notice Manifest, 855 Purchase Order Acknowledgment. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your NEXCOM (Navy Exchange Service Command) EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
