855 Purchase Order Acknowledgment
O.C. Tanner · X12 004010
O.C. Tanner’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
16 of 16 segments
HEADING
ST
Transaction Set Header
pos 010
Required
max —
BAK
Beginning Segment for Purchase Order Acknowledgment
pos 020
Required
max —
REF
Reference Identification
pos 050
Optional
max —
PER
Administrative Communications Contact
pos 060
Optional
max 3
N9 Looprepeats 1000
N9
Reference Identification
pos 280
Optional
max —
MSG
Message Text
pos 290
Optional
max 1000
N1 LoopShip Fromvariant 1 of 2repeats 200
N1
Ship From
pos 300
Optional
max —
N2
Additional Name Information
pos 310
Optional
max 2
N3
Address Information
pos 320
Optional
max 2
N4
Geographic Location
pos 330
Optional
max —
N1 LoopShip Tovariant 2 of 2repeats 200
N1
Ship To
pos 300
Optional
max —
DETAIL
PO1 Looprepeats 100000
PO1
Baseline Item Data
pos 010
Optional
max —
PID Looprepeats 1000
PID
Product/Item Description
pos 050
Optional
max —
ACK Looprepeats 104
ACK
Line Item Acknowledgment
pos 270
Optional
max —
SUMMARY
CTT Looprepeats 1
CTT
Transaction Totals
pos 010
Optional
max —
SE
Transaction Set Trailer
pos 030
Required
max —
Validate a 855
Paste or upload a document and check it against O.C. Tanner’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on O.C. Tanner’s 855 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with O.C. Tanner, and keeps the spec current as it changes.