Guides - sample 850
/
Purchase Order
  • Specification
  • EDI Inspector
Import guide into your account
Guides - sample 850 logo

X12 850 Purchase Order

X12 Release 8010

This X12 Transaction Set 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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/guides-sample-850/purchase-order/01GB65QHM8T24DR7G20C481HHN
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
0100
Transaction Set Header
Max use 1
Required
BEG
0200
Beginning Segment for Purchase Order
Max use 1
Required
CUR
0400
Currency
Max use 1
Optional
DTM
1500
Date/Time Reference
Max use 10
Optional
TD5
2400
Carrier Details (Routing Sequence/Transit Time)
Max use 1
Optional
N9 Loop
detail
PO1 Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code identifying the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code identifying the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I65
Repetition Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

^
Repetition Separator
ISA-12
I11
Interchange Control Version Number Code
Required
Identifier (ID)

Code specifying the version number of the interchange control segments, the version of the data elements within the control segments, and the code values within those data elements.

00801
00801 Standards Approved for Publication by ASC X12 Procedures Review Board through December 2019
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested Code
Required
Identifier (ID)
Min 1Max 1

Code indicating sender's request for an interchange acknowledgment

0
No Interchange Acknowledgment Requested
1
Interchange Acknowledgment Requested (TA1)
2
Interchange Acknowledgment Requested only when Interchange is "Rejected Because Of Errors"
3
Interchange Acknowledgment Requested only when Interchange is "Rejected Because Of Errors" or "Accepted but Errors are Noted"
ISA-15
I14
Interchange Usage Indicator Code
Required
Identifier (ID)
Min 1Max 1

Code indicating whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

PO
Purchase Order (850)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission; codes agreed to by trading partners

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

GS-05
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

008010
008010 Standards Approved for Publication by ASC X12 Procedures Review Board through December 2019

Heading

ST
0100
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code identifying a Transaction Set

  • The transaction set identifier (ST01) is 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
ST-02
329
Transaction Set Control Number
Required
String (AN)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BEG
0200
Heading > BEG

Beginning Segment for Purchase Order

RequiredMax use 1

To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates

Example
BEG-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
BEG-02
92
Purchase Order Type Code
Required
Identifier (ID)

Code specifying the type of Purchase Order

NE
New Order
BEG-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

BEG-05
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

  • BEG05 is the date assigned by the purchaser to purchase order.
CUR
0400
Heading > CUR

Currency

OptionalMax use 1

To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Example
CUR-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

BY
Buying Party (Purchaser)
CUR-02
100
Currency Code
Required
Identifier (ID)

Code specifying the Standard ISO code for country in whose currency the charges are specified

USD
US Dollar
DTM
1500
Heading > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

002
Delivery Requested
038
Ship No Later
DTM-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

DTM-03
337
Time
Optional
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

TD5
2400
Heading > TD5

Carrier Details (Routing Sequence/Transit Time)

OptionalMax use >1

To specify the carrier and sequence of routing and provide transit time information

Example
If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required
TD5-01
133
Routing Sequence Code
Optional
Identifier (ID)
Min 1Max 2

Code specifying the relationship of a carrier to a specific shipment movement

TD5-02
66
Identification Code Qualifier
Optional
Identifier (ID)

Code specifying 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.
0
Petroleum Industry Exchange (PETROEX) Number
TD5-03
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

TD5-04
91
Transportation Method/Type Code
Optional
Identifier (ID)

Code specifying the method or type of transportation for the shipment

A
Air
M
Motor (Common Carrier)
R
Rail
S
Ocean
N9 Loop
OptionalMax >1
N9
2950
Heading > N9 Loop > N9

Extended Reference Information

RequiredMax use 1

To transmit identifying information as specified by the Reference Identification Qualifier

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code identifying the Reference Identification

ZZ
Mutually Defined
N9-02
127
Reference Identification
Optional
String (AN)
Min 1Max 80

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

N9 Loop end
N1 Loop
OptionalMax >1
N1
3100
Heading > N1 Loop > N1

Party Identification

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

BT
Bill-to-Party
ST
Ship To
VN
Vendor
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code specifying the system/method of code structure used for Identification Code (67)

1
D-U-N-S Number, Dun & Bradstreet
9
D-U-N-S+4, D-U-N-S Number with Four Character Suffix
US
Unique Supplier Identification Number (USIN)
ZZ
Mutually Defined
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

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.
N1 Loop end
Heading end

Detail

PO1 Loop
RequiredMax >1
PO1
0100
Detail > PO1 Loop > PO1

Baseline Item Data

RequiredMax use 1

To specify basic and most frequently used line item data

  • PO102 is required.
Example
If Unit or Basis for Measurement Code (PO1-03) is present, then Quantity (PO1-02) is required
If Basis of Unit Price Code (PO1-05) is present, then Unit Price (PO1-04) is required
If either Product/Service ID Qualifier (PO1-06) or Product/Service ID (PO1-07) is present, then the other is required
If either Product/Service ID Qualifier (PO1-08) or Product/Service ID (PO1-09) is present, then the other is required
PO1-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • PO101 is the line item identification.
PO1-02
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

  • PO102 is quantity ordered.
PO1-03
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

EA
Each
PO1-04
212
Unit Price
Optional
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

PO1-05
639
Basis of Unit Price Code
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type of unit price for an item

PO1-06
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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., ISBN No., Model No., or SKU.
BP
Buyer's Part Number
PO1-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 80

Identifying number for a product or service

PO1-08
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

VP
Vendor's (Seller's) Part Number
PO1-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 80

Identifying number for a product or service

PID Loop
OptionalMax >1
PID
0500
Detail > PO1 Loop > PID Loop > PID

Product/Item Description

RequiredMax use 1

To describe a product or process in coded or free-form format

Example
If Product Description Code (PID-04) is present, then Agency Qualifier Code (PID-03) is required
PID-01
349
Item Description Type Code
Required
Identifier (ID)

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
S
Structured (From Industry Code List)
X
Semi-structured (Code and Text)
PID-02
750
Product/Process Characteristic Code
Optional
Identifier (ID)
Min 2Max 3

Code identifying the general class of a product or process characteristic

PID-03
559
Agency Qualifier Code
Optional
Identifier (ID)
Min 2Max 2

Code identifying the agency assigning the code values

  • Use PID03 to indicate the organization that publishes the code list being referred to.
PID-04
751
Product Description Code
Optional
String (AN)
Min 1Max 12

A code from an industry code list which provides specific data about a product characteristic

  • PID04 should be used for industry-specific product description codes.
PID-05
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

PID Loop end
PO1 Loop end
Detail end

Summary

CTT Loop
OptionalMax >1
CTT
0100
Summary > CTT Loop > CTT

Transaction Totals

RequiredMax use 1

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.
Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

CTT-02
347
Hash Total
Optional
Decimal number (R)
Min 1Max 10

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.

## Example:
-.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.
18E2 Fifth occurrence of value being hashed.

1873 Hash Total

CTT Loop end
SE
0300
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
String (AN)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

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.