850 Purchase Order (Shrinkwrapped Orders)
Adobe · X12 004010
Adobe’s published 850 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
19 of 19 segments
HEADING
ST
Transaction Set Header ST
pos 010
Optional
max —
BEG
Beginning Segment For Purchase Order BEG
Example: BEG*00*NE*MH80312**20150831
pos 020
Required
max —
CUR
Currency CUR
Currency is MANDATORY and must be sent.
Example: CUR*SE*USD
pos 040
Required
max —
REF
Reference Identification REF
This reference identification is used by Adobe to communicate the buying party's contract number.
Example: REF*CT*123456
pos 050
Required
max —
DTM
Delivery Requestedvariant 1 of 2
Example: DTM*002*20150901
pos 150
Optional
max —
DTM
Requested Shipvariant 2 of 2
Example: DTM*010*20150831
pos 150
Optional
max —
N1 LoopBill-to-Partyvariant 1 of 4required
N1
Name N1
COMPTIA: In this Header position of the Purchase Order document, this segment identifies the destination party. It is encouraged that the trading partners codify all addresses within their systems.
Adobe: ID codes are utilized for location identification. Additions, Enhancements, or Changes to the Bill-To ID will require extra configuration on Adobe’s Part. Please contact your Adobe Business Representative to provide any changes or additions for Bill-To ID.
Example: N1*BT*BILL TO*ZZ*04332571
pos 310
Required
max —
N1 LoopBuying Party (Purchaser)variant 2 of 4required
N1
Name N1
COMPTIA: In this Header position of the Purchase Order document, this segment identifies the destination party. It is encouraged that the trading partners codify all addresses within their systems.
Adobe: ID codes are utilized for location identification. Additions, Enhancements, or Changes to the Sold-To ID will require extra configuration on Adobe’s Part. Please contact your Adobe Business Representative to provide any changes or additions for Sold-To ID.
Example: N1*BY*BUYING PARTY*ZZ*04332571
pos 310
Required
max —
N1 LoopParty to Receive Invoice for Goods or Servicesvariant 3 of 4required
N1
Name N1
COMPTIA: In this Header position of the Purchase Order document, this segment identifies the destination party. It is encouraged that the trading partners codify all addresses within their systems.
Adobe: ID codes are utilized for location identification. Additions, Enhancements, or Changes to the Payer ID will require extra configuration on Adobe’s Part. Please contact your Adobe Business Representative to provide any changes or additions for Payer ID.
Example: N1*PO*PAYER PARTY*ZZ*04332571
pos 310
Required
max —
N1 LoopShip Tovariant 4 of 4required
N1
Name N1
COMPTIA: In this Header position of the Purchase Order document, this segment identifies the destination party. It is encouraged that the trading partners codify all addresses within their systems.
Adobe: ID codes are utilized for location identification. Additions, Enhancements, or Changes to the Ship-To ID will require extra configuration on Adobe’s Part. Please contact your Adobe Business Representative to provide any changes or additions for Ship-To ID.
Example: N1*ST*SHIP TO*ZZ*04332571
pos 310
Required
max —
N2
Additional Name Information N2
COMPTIA: In this Header position of the Purchase Order document, this segment provides additional detail to the N1 segment. It is encouraged that the trading partners codify all addresses within their systems.
Example: N2*M. BUYER
pos 320
Optional
max 2
N3
Address Information N3
Adobe: Adobe accepts up to 3 iterations of the N3. This first iterations contains address lines 1 and 2 and the second iteration contains address line 3. Only the N301 will be used from the second iteration. If an N302 is sent it will not be mapped.
Example: N3*123 MAIN STREET, SE
pos 330
Required
max 2
N4
Geographic Location N4
COMPTIA: In this Header position of the Purchase Order document, this segment identifies the city, state/province, and postal code of the destination party.
Example: N4*CEDAR RAPIDS*IA*524032140
pos 340
Required
max —
PER
Administrative Communications Contact PER
COMPTIA: In this Header position of the Purchase Order document, this segment identifies the parties responsible for originating the Purchase Order.
Example: PER*IC*J SMITH*TE*8015551234*FX*8015554321*EM*john@doe.com
pos 360
Optional
max —
DETAIL
PO1 Looprequired
PO1
Baseline Item Data PO1
Adobe: There is one PO1 segment for each line item. Product/Service ID's must be sent in the order listed.
Example: PO1*1*11*EA*588.00*CA*BP*12345678*MG*65158494
pos 010
Required
max —
DTM
Date Time Reference DTM
Example: DTM*010*20150831
pos 210
Optional
max 10
SUMMARY
CTT Looprequired
CTT
Transaction Totals CTT
Example: CTT*1
pos 010
Required
max —
AMT
Monetary Amount AMT
Adobe: All monetary amounts must be provided in USD. This segment will be used to verify that the total extended values of the line items match this total amount. If there is any discrepancy our translator will reject the 850 document.
Example : AMT*TT*6468
pos 020
Optional
max —
SE
Transaction Set Trailer SE
pos 030
Optional
max —
Validate a 850
Paste or upload a document and check it against Adobe’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on Adobe’s 850 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with Adobe, and keeps the spec current as it changes.