NEXCOM (Navy Exchange Service Command) EDI 820 Payment Remittance

Schema Reference

14 segments · X12 820 Payment Order/Remittance Advice

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 Interchange Control Standards Identifier

M ID 1-1

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 Usage Indicator

M ID 1-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

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

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

BPR05 Payment Format Code

O ID 1-10

BPR06 (DFI) ID Number Qualifier

C ID 2-2

BPR07 (DFI) Identification Number

C AN 3-12

BPR08 Account Number Qualifier

O ID 1-3

BPR09 Account Number

C AN 1-35

BPR10 Originating Company Identifier

O AN 10-10

BPR12 (DFI) ID Number Qualifier

C ID 2-2

BPR13 (DFI) Identification Number

C AN 3-12

BPR14 Account Number Qualifier

O ID 1-3

BPR15 Account Number

C AN 1-35

BPR16 Date

O DT 8-8

TRN01 Trace Type Code

M ID 1-2

TRN02 Reference Identification

M AN 1-30

REF01 Reference Identification Qualifier

M ID 2-3

REF02 Reference Identification

C AN 1-30

REF03 Description

C AN 1-80

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

N1 Loop

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

ENT Loop

ENT01 Assigned Number

O N0 1-6

RMR Loop

RMR01 Reference Identification Qualifier

C ID 2-3

RMR02 Reference Identification

C AN 1-30

RMR04 Monetary Amount

O R 1-18

RMR05 Monetary Amount

O R 1-18

RMR06 Monetary Amount

O R 1-18

REF01 Reference Identification Qualifier

M ID 2-3

REF02 Reference Identification

C AN 1-30

REF03 Description

C AN 1-80

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

ADX Loop

ADX01 Monetary Amount

M R 1-18

ADX02 Adjustment Reason Code

M ID 2-2

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

How It Works

Automating NEXCOM (Navy Exchange Service Command) 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

NEXCOM Test (via SPS Commerce)

NEXCOM (Navy Exchange Service Command) EDI 820 FAQ

Common questions about 820 Payment Order/Remittance Advice transactions with NEXCOM (Navy Exchange Service Command).

How long does it take to set up NEXCOM (Navy Exchange Service Command) EDI with Stacksync?

Most suppliers are fully connected and processing live NEXCOM (Navy Exchange Service Command) 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 NEXCOM (Navy Exchange Service Command)?

No. Stacksync handles the entire EDI transport layer. We connect directly to NEXCOM (Navy Exchange Service Command)'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 NEXCOM (Navy Exchange Service Command) 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 NEXCOM (Navy Exchange Service Command)?

Stacksync supports all EDI document types required by NEXCOM (Navy Exchange Service Command) — 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 NEXCOM (Navy Exchange Service Command) 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 NEXCOM (Navy Exchange Service Command)'s EDI network and your system in real time.

What happens when NEXCOM (Navy Exchange Service Command) updates their EDI specifications?

Stacksync monitors NEXCOM (Navy Exchange Service Command)'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.