X12 850 Purchase Order
This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- PO
- Purchase Order (850)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 850
- Purchase Order
Beginning Segment for Purchase Order
To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of Purchase Order
- BN
- Bill of Materials Order
- DS
- Dropship
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Must be an Integer
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Code (Standard ISO) for country in whose currency the charges are specified
- CAD
- Canadian Dollar
- GBP
- Pound Sterling
- USD
- US Dollar
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- 11
- Account Number
- 12
- Billing Account
Account number under which billing is rendered.
- 80
- Charge Number
A number used by financial systems to identify accounts for costs incurred on a contract.
- BU
- Buyer's Approval Mark
If order was placed on Newegg.com, REF02 = "NE".
If order was placed on NeweggBusiness.com, REF02 = "B2B".
- CN
- Carrier's Reference Number (PRO/Invoice)
- CO
- Customer Order Number
- EU
- End User's Purchase Order Number
- GK
- Third Party Reference Number
REF02 will contain the 3rd-party carrier account number (i.e. UPS Account Number).
- IT
- Internal Customer Number
Used for reference as the Customer # on the Packing List.
- SU
- Special Processing Code
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
"HAL" = FedEx Hold at Location Service
"SR" = Signature Required on package shipment
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- BP
- Paid by Buyer
- CC
- Collect
- DF
- Defined by Buyer and Seller
- PC
- Prepaid but Charged to Customer
- PP
- Prepaid (by Seller)
- PU
- Pickup
- TP
- Third Party Pay
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- DE
- Destination (Shipping)
- OR
- Origin (Shipping Point)
A free-form description to clarify the related data elements and their content
Code identifying the source of the transportation terms
Code identifying the trade terms which apply to the shipment transportation responsibility
Code identifying type of location
- FOB06 is the code specifying the title passage location.
A free-form description to clarify the related data elements and their content
Code specifying where responsibility for risk of loss passes
- FOB08 is the code specifying the point at which the risk of loss transfers.
This may be different than the location specified in FOB02/FOB03 and FOB06/FOB07.
- BY
- Risk of Loss in Transit to Destination is Buyer's
- SE
- Risk of Loss in Transit to Destination is Seller's
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
Code identifying type of payment terms
- If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
- 01
- Basic
- 03
- Fixed Date
- 05
- Discount Not Applicable
- 07
- Extended
- 08
- Basic Discount Offered
- 14
- Previously agreed upon
- ZZ
- Mutually Defined
Code identifying the beginning of the terms period
- 3
- Invoice Date
- 4
- Specified Date
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
Date payment is due if discount is to be earned expressed in format CCYYMMDD
Number of days in the terms discount period by which payment is due if terms discount is earned
Date when total invoice amount becomes due expressed in format CCYYMMDD
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- 2
- Standard Carrier Alpha Code (SCAC)
- ZZ
- Mutually Defined
Code identifying a party or other code
- AIT
- AIT
- FEDEX
- FedEx
- UPS
- UPS
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Shipping Carrier Service
- AIT Front Door Delivery
- AIT Front Door Delivery
- AIT In Home Delivery
- AIT In Home Delivery
- AIT White Glove Service
- AIT White Glove Delivery
- FEDEX EXPRESS SAVER
- FedEx Express Saver
- FEDX 2 DAYS
- FedEx 2 Day
- FEDX STD OVR
- FedEx Standard Overnight
- UPS 2nd Day
- UPS 2nd Day Air
- UPS 3 DAYS
- UPS 3 Day Select
- UPS Ground
- UPS Ground
- UPS Red Next Resi
- UPS Next Day Air Saver
- UPSMI
- UPS Mail Innovations
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- L1
- Letters or Notes
Message Text
To provide a free-form format that allows the transmission of text information
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Message Text
To provide a free-form format that allows the transmission of text information
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
If HAL service is indicated for the shipment when REF01 = "SU", it is whom with this address information will pick up at FedEx receiving location.
- BT
- Bill-to-Party
Code designating the system/method of code structure used for Identification Code (67)
- 54
- Warehouse
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- ZZ
- Mutually Defined
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- CN
- General Contact
- RE
- Receiving Contact
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- FX
- Facsimile
- TE
- Telephone
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 54
- Warehouse
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- ZZ
- Mutually Defined
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- CN
- General Contact
- RE
- Receiving Contact
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- FX
- Facsimile
- TE
- Telephone
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
If HAL service is indicated for the shipment when REF01 = "SU", it is where the FedEx receiving location is specified by package receiver.
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 54
- Warehouse
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- ZZ
- Mutually Defined
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- CN
- General Contact
- RE
- Receiving Contact
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- FX
- Facsimile
- TE
- Telephone
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Additional identifications (e.g. MG – Vendor's Manufacture Part Number, UP - UPC Code, or BP - Buyer Part Number) can be added starting from PO108 to PO115, but please note gap (blank elements) between identifications is not allowed.
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- PE
- Price per Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- MG
- Manufacturer's Part Number
- MN
- Model Number (Stock PO Vendor Optional)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- MG
- Manufacturer's Part Number
- MN
- Model Number (Stock PO Vendor Optional)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- MG
- Manufacturer's Part Number
- MN
- Model Number (Stock PO Vendor Optional)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BP
- Buyer's Part Number
- MG
- Manufacturer's Part Number
- MN
- Model Number (Stock PO Vendor Optional)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
Code identifying the general class of a product or process characteristic
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- SU
- Special Processing Code
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- DV
- Declared Value Required on Package Shipment
- SR
- Signature Required on Package Shipment
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
Total number of line items in the transaction set
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample 1
GS*PO*SENDERGS*RECEIVERGS*20240428*183414*000000001*X*004010~
ST*850*0967~
BEG*00*DS*2093518**20090717~
CUR*BY*USD~
REF*CO*AC-156895~
REF*BU*NE~
REF*SU*HAL*Fedex Hold at Location~
REF*SU*SR*SignatureRequired~
ITD*14*3****20090816*30~
TD5*****UPS Ground~
N9*L1*ADDITIONAL COMMENTS~
MSG*Username: Andrew; Password: asdf~
N9*L1*SPECIAL INSTRUCTIONS~
MSG*GOVT. EDUC. PRICING~
N1*ST*TN Warehouse(06)~
N2*02~
N3*4995 Citation Dr Suite 102,Dock#13-20~
N4*Memphis*TN*38118*US~
PER*RE*Contact Guy*EM*ContactGuy@newegg.com*TE*626-271-1420~
PO1*1*5*EA*163.02*PE*VP*010-00270-02*UP*753759031961*MG*010-00270-02*BP*28-483-001~
PID*F*08***Garmin Rino FRS/GPS Receiver Handhe~
PO1*2*2*EA*117.93*PE*VP*010-00361-00*MG*010-00361-00*UP*753759045302*BP*28-483-002~
PID*F*08***GARMIN 010-00361-00 FORETREX 201~
PO1*3*10*EA*138.74*PE*VP*010-00378-00*MG*010-00378-00*UP*753759047832*BP*28-483-003~
PID*F*08***Garmin GPS 10 Deluxe with Bluetooth~
REF*SU*DV*DeclaredValue~
REF*SU*SR*SignatureRequired~
CTT*3*17~
SE*28*0967~
GE*1*000000001~
IEA*1*000000001~
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.