UNFI
/
Purchase Order
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from UNFI. Contact UNFI for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
UNFI logo

X12 850 Purchase Order

X12 Release 4010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
    View the latest version of this implementation guide as an interactive webpage
    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
    010
    Transaction Set Header
    Max use 1
    Required
    BEG
    020
    Beginning Segment for Purchase Order
    Max use 1
    Required
    REF
    050
    Reference Identification Customer Reference Number
    Max use 1
    Optional
    REF
    050
    Reference Identification Department Number
    Max use 1
    Optional
    REF
    050
    Reference Identification Internal Vendor Number
    Max use 1
    Optional
    FOB
    080
    F.O.B. Related Instructions
    Max use 1
    Optional
    ITD
    130
    Terms of Sale/Deferred Terms of Sale
    Max use 1
    Optional
    DTM
    150
    Date/Time Reference
    Max use 10
    Optional
    N1 Loop Bill To
    detail
    PO1 Loop
    PO1
    010
    Baseline Item Data
    Max use 1
    Required
    PO4
    090
    Item Physical Details
    Max use 1
    Optional
    SAC 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

    Code to identify the type of information in the Authorization Information

    00
    No Authorization Information Present (No Meaningful Information in I02)
    ISA-02
    I02
    Authorization Information
    Required
    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

    Code to identify the type of information in the Security Information

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    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
    Min 2Max 2

    Qualifier to designate 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
    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

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

    01
    Duns (Dun & Bradstreet)
    ISA-08
    I07
    Interchange Receiver ID
    Required
    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
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    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
    ISA-12
    I11
    Interchange Control Version Number
    Required

    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
    ISA-13
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Min 1Max 1

    Code sent by the sender to request an interchange acknowledgment (TA1)

    0
    No Acknowledgment Requested
    1
    Interchange Acknowledgment Requested
    ISA-15
    I14
    Usage Indicator
    Required
    Min 1Max 1

    Code to indicate 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
    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

    Code identifying a group of application related transaction sets

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

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

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

    Code identifying party receiving transmission. Codes agreed to by trading partners

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    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
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Min 1Max 2

    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
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

    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

    ST
    010

    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

    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
    ST-02
    329
    Transaction Set Control Number
    Required
    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
    020

    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

    Code identifying purpose of transaction set

    00
    Original
    BEG-02
    92
    Purchase Order Type Code
    Required

    Code specifying the type of Purchase Order

    SA
    Stand-alone Order
    BEG-03
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    BEG-05
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BEG05 is the date assigned by the purchaser to purchase order.
    BEG-06
    367
    Contract Number
    Optional
    Min 1Max 30

    Contract number

    REF
    050

    Reference Identification Customer Reference Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    If REF01 = CR then REF02 = Chain Code for Natural Orders or Order Source ID for Conventional Orders

    Example
    Variants (all may be used)
    REFReference Identification Department NumberREFReference Identification Internal Vendor Number
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    CR
    Customer Reference Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    REF
    050

    Reference Identification Department Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    If REF01 = DP then REF02 = Department Number

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    DP
    Department Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    REF
    050

    Reference Identification Internal Vendor Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    If REF01 = IA then REF02 = Vendor Number

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    IA
    Internal Vendor Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    FOB
    080

    F.O.B. Related Instructions

    OptionalMax use >1

    To specify transportation instructions relating to shipment

    Example
    FOB-01
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    • FOB01 indicates which party will pay the carrier.
    CC
    Collect
    PP
    Prepaid (by Seller)
    PU
    Pickup
    FOB-02
    309
    Location Qualifier
    Required

    Code identifying type of location

    • FOB02 is the code specifying transportation responsibility location.
    DE
    Destination (Shipping)
    OR
    Origin (Shipping Point)
    ITD
    130

    Terms of Sale/Deferred Terms of Sale

    OptionalMax use >1

    To specify terms of sale

    Example
    ITD-02
    333
    Terms Basis Date Code
    Required

    Code identifying the beginning of the terms period

    3
    Invoice Date
    15
    Receipt of Goods
    ITD-03
    338
    Terms Discount Percent
    Required
    Min 1Max 6

    Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date

    ITD-05
    351
    Terms Discount Days Due
    Required
    Min 1Max 3

    Number of days in the terms discount period by which payment is due if terms discount is earned

    ITD-07
    386
    Terms Net Days
    Required
    Min 1Max 3

    Number of days until total invoice amount is due (discount not applicable)

    DTM
    150

    Date/Time Reference

    OptionalMax use 10

    To specify pertinent dates and times

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    002
    Delivery Requested
    010
    Requested Ship
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    N1 N1 Loop Bill To
    RequiredMax 200
    Variants (all may be used)
    N1N1 Loop Ship To
    N1
    310

    Name

    RequiredMax use 1

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

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    BT
    Bill-to-Party
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

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

    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Required
    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.
    N3
    330

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N4
    340

    Geographic Location

    OptionalMax use >1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Required
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Required
    Min 2Max 2

    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.
    N4-03
    116
    Postal Code
    Required
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    PER
    360

    Administrative Communications Contact

    OptionalMax use >1

    To identify a person or office to whom administrative communications should be directed

    Example
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named

    BD
    Buyer Name or Department
    PER-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Required

    Code identifying the type of communication number

    TE
    Telephone
    PER-04
    364
    Communication Number
    Required
    Min 1Max 80

    Complete communications number including country or area code when applicable

    N1 N1 Loop Ship To
    RequiredMax 200
    Variants (all may be used)
    N1N1 Loop Bill To
    N1
    310

    Name

    RequiredMax use 1

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

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    ST
    Ship To
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

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

    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Required
    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.
    N3
    330

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N4
    340

    Geographic Location

    OptionalMax use >1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Required
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Required
    Min 2Max 2

    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.
    N4-03
    116
    Postal Code
    Required
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    PER
    360

    Administrative Communications Contact

    OptionalMax use >1

    To identify a person or office to whom administrative communications should be directed

    Example
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named

    BD
    Buyer Name or Department
    PER-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Required

    Code identifying the type of communication number

    TE
    Telephone
    PER-04
    364
    Communication Number
    Required
    Min 1Max 80

    Complete communications number including country or area code when applicable

    Detail

    PO1 Loop
    RequiredMax 100000
    PO1
    010

    Baseline Item Data

    RequiredMax use 1

    To specify basic and most frequently used line item data

    • PO102 is required.
    Example
    If either Product/Service ID Qualifier (PO1-10) or Product/Service ID (PO1-11) is present, then the other is required
    PO1-01
    350
    Assigned Identification
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • PO101 is the line item identification.
    PO1-02
    330
    Quantity Ordered
    Required
    Min 1Max 15

    Quantity ordered

    PO1-03
    355
    Unit or Basis for Measurement Code
    Required

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

    CA
    Case
    DZ
    Dozen
    EA
    Each
    GR
    Gram
    LB
    Pound
    PO1-04
    212
    Unit Price
    Required
    Min 1Max 15

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

    PO1-06
    235
    Product/Service ID Qualifier
    Required

    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.
    IN
    Buyer's Item Number
    MF
    Manufacturer
    MU
    Authorized Parts List Number
    UA
    U.P.C./EAN Case Code (2-5-5)
    PO1-07
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    PO1-08
    235
    Product/Service ID Qualifier
    Required

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

    EN
    European Article Number (EAN) (2-5-5-1)
    IN
    Buyer's Item Number
    PI
    Purchaser's Item Code
    UA
    U.P.C./EAN Case Code (2-5-5)
    VN
    Vendor's (Seller's) Item Number
    PO1-09
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    PO1-10
    235
    Product/Service ID Qualifier
    Optional

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

    UK
    U.P.C./EAN Shipping Container Code (1-2-5-5-1)
    PO1-11
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    PID Loop
    RequiredMax 1000
    PID
    050

    Product/Item Description

    RequiredMax use 1

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

    Example
    PID-01
    349
    Item Description Type
    Required

    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
    PID-05
    352
    Description
    Required
    Min 1Max 80

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

    PO4
    090

    Item Physical Details

    OptionalMax use >1

    To specify the physical qualities, packaging, weights, and dimensions relating to the item

    Example
    PO4-01
    356
    Pack
    Required
    Min 1Max 6

    The number of inner containers, or number of eaches if there are no inner containers, per outer container

    PO4-14
    810
    Inner Pack
    Optional
    Min 1Max 6

    The number of eaches per inner container

    SAC Loop
    OptionalMax 25
    SAC
    130

    Service, Promotion, Allowance, or Charge Information

    RequiredMax use 1

    To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

    Example
    If Reference Identification (SAC-13) is present, then at least one of Service, Promotion, Allowance, or Charge Code (SAC-02) or Agency Service, Promotion, Allowance, or Charge Code (SAC-04) is required
    SAC-01
    248
    Allowance or Charge Indicator
    Required

    Code which indicates an allowance or charge for the service specified

    • If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
    A
    Allowance
    SAC-02
    1300
    Service, Promotion, Allowance, or Charge Code
    Required

    Code identifying the service, promotion, allowance, or charge

    F800
    Promotional Allowance
    SAC-03
    559
    Agency Qualifier Code
    Required

    Code identifying the agency assigning the code values

    13
    Arkansas
    SAC-04
    1301
    Agency Service, Promotion, Allowance, or Charge Code
    Required
    Min 1Max 10

    Agency maintained code identifying the service, promotion, allowance, or charge

    • SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction to further the code in SAC02.
    SAC-05
    610
    Amount
    Required
    Min 1Max 15

    Monetary amount

    • SAC05 is the total amount for the service, promotion, allowance, or charge.
    • If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
    SAC-08
    118
    Rate
    Required
    Min 1Max 9

    Rate expressed in the standard monetary denomination for the currency specified

    • SAC08 is the allowance or charge rate per unit.
    SAC-09
    355
    Unit or Basis for Measurement Code
    Required

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

    CA
    Case
    DZ
    Dozen
    EA
    Each
    GS
    Gross
    LB
    Pound
    SAC-10
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    • SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.
    • SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge.
    • In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.
    SAC-12
    331
    Allowance or Charge Method of Handling Code
    Required

    Code indicating method of handling for an allowance or charge

    02
    Off Invoice
    SAC-13
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    • SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.
    SAC-15
    352
    Description
    Required
    Min 1Max 80

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

    Summary

    CTT Loop
    RequiredMax 1
    CTT
    010

    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
    If either Weight (CTT-03) or Unit or Basis for Measurement Code (CTT-04) is present, then the other is required
    If either Volume (CTT-05) or Unit or Basis for Measurement Code (CTT-06) is present, then the other is required
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    CTT-03
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    CTT-04
    355
    Unit or Basis for Measurement Code
    Optional

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

    LB
    Pound
    CTT-05
    183
    Volume
    Optional
    Min 1Max 8

    Value of volumetric measure

    CTT-06
    355
    Unit or Basis for Measurement Code
    Optional

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

    CF
    Cubic Feet
    AMT
    020

    Monetary Amount

    OptionalMax use 1

    To indicate the total monetary amount

    • If AMT is used in the summary area, then AMT01 will = TT and AMT02 will indicate total transaction amount as calculated by the sender.
    Example
    AMT-01
    522
    Amount Qualifier Code
    Required

    Code to qualify amount

    TT
    Total Transaction Amount
    AMT-02
    782
    Monetary Amount
    Required
    Min 1Max 15

    Monetary amount

    SE
    030

    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
    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
    Min 4Max 9

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

    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
    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
    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
    Min 1Max 5

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

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    CustomerGeneric_850

    ISA*00* *00* *01*123456789 *01*943556183 *140120*0841*U*00401*005887255*0*P*>
    GS*PO*123456789*943556183*20140120*0841*005887255*X*004010
    ST*850*005887255
    BEG*00*SA*5887255**20140120
    REF*CR*ABC
    N1*BT*Customer Bill To Name*92*11111
    N1*ST*Customer Ship To Name*92*22222
    N3*Address
    N4*Short Hills*NJ*07052
    PO1*1*4*EA*11.10**UA*001579402481*VN*064558
    PID*F****Description 1
    PO1*2*3*EA*2**UA*001579402685*VN*068752
    PID*F****Description 2
    PO1*3*4*EA*3.3**UA*001579402474*VN*067355
    PID*F****Description 3
    CTT*3
    SE*9*005887255
    GE*1*005887255
    IEA*1*005887255

    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.