855 Purchase Order Acknowledgment
Veyer · X12 004010
Veyer’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
8 of 8 segments
HEADING
ST
Transaction Set Header ST
pos 010
Optional
max —
BAK
Beginning Segment For Purchase Order Acknowledgment BAK
Veyer’s PO Number must match EXACTLY what was sent on the EDI PO.
Example:
BAK~00~AD~ 15971515-1105~20070501~~~~110777205~20070501}
pos 020
Required
max —
REF
Reference Identification Customer Account Numbervariant 1 of 2
Example: REF~CO~12345678} ODP Business Solutions AOPS Customer Account Number
pos 050
Optional
max —
REF
Reference Identification Document Numbervariant 2 of 2
Example: REF~QC~083431107001} ODP Business Solutions AOPS Order Number
pos 050
Optional
max —
DETAIL
PO1 Loop
PO1
Baseline Item Data PO1
Example: PO1~1~48~EA~3.1~~VA~1111~IN~0173179~UP~051131069060~MG~MFR’s Part Number}
pos 010
Required
max —
ACK Loop
ACK
Line Item Acknowledgment ACK
Example: ACK~IA~48~EA~083~20100501~~ZZ~I1 Invalid Item Cost}
pos 270
Required
max —
SUMMARY
CTT Loop
CTT
Transaction Totals CTT
Example: CTT~1~48}
pos 010
Required
max —
SE
Transaction Set Trailer SE
pos 030
Optional
max —
Validate a 855
Paste or upload a document and check it against Veyer’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on Veyer’s 855 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with Veyer, and keeps the spec current as it changes.