855 Purchase Order Acknowledgment
NEXCOM · X12 003040
NEXCOM’s published 855 specification, rendered as an interactive guide. Expand any segment to see its elements, data types, lengths and accepted codes — then validate your own document against it below.
Specification
9 of 9 segments
HEADING
ST
- TRANSACTION SET HEADER Level: HEADER
pos 010
Required
max —
BAK
- BEGINNING SEGMENT Level: HEADER
pos 020
Required
max —
REF
- REFERENCE NUMBER Level: HEADER
pos 050
Optional
max —
DTM
- Date/Time Reference Level: HEADER
pos 150
Optional
max —
N1 Loop
N1
- NAME * Level: HEADER
pos 300
Optional
max —
DETAIL
PO1 Loop
PO1
- BASELINE ITEM DATA Level: DETAIL
pos 010
Optional
max —
SDQ
- DESTINATION QUANTITY * Level: DETAIL
pos 190
Optional
max —
SUMMARY
CTT
- TRANSACTION TOTALS Level: SUMMARY
pos 010
Required
max —
SE
- TRANSACTION SET TRAILER Level: SUMMARY
pos 030
Required
max —
Validate a 855
Paste or upload a document and check it against NEXCOM’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on NEXCOM’s 855 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with NEXCOM, and keeps the spec current as it changes.