Buckle
/
Purchase Order Acknowledgment
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from Buckle. Contact Buckle for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
Buckle logo

X12 855 Purchase Order Acknowledgment

X12 Release 5010

This X12 Transaction Set contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) 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 a seller's acknowledgment of a buyer's purchase order.
This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI sample
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build free EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    detail
    PO1 Loop
    summary
    CTT Loop
    SE
    0300
    Transaction Set Trailer
    Max use 1
    Required
    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 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
    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 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
    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

    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
    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

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

    08
    UCC EDI Communications ID (Comm ID)
    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
    I65
    Repetition Separator
    Required
    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
    Required

    Code specifying the version number of the interchange control segments

    00501
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
    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 indicating sender's request for an interchange acknowledgment

    0
    No Interchange Acknowledgment Requested
    1
    Interchange Acknowledgment Requested (TA1)
    ISA-15
    I14
    Interchange Usage Indicator
    Required
    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
    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

    PR
    Purchase Order Acknowledgment (855)
    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 where CC represents the first two digits of the calendar year

    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 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

    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

    005010
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003

    Heading

    ST
    0100

    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) 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).
    855
    Purchase Order Acknowledgment
    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

    BAK
    0200

    Beginning Segment for Purchase Order Acknowledgment

    RequiredMax use 1

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

    Example
    BAK-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    BAK-02
    587
    Acknowledgment Type
    Required

    Code specifying the type of acknowledgment

    Usage notes

    BAK02 – We only support AC (Acknowledge with detail and change) and AD (Acknowledge with detail no change. No other codes are supported and both require that the PO1 be returned (with the correct data).

    AC
    Acknowledge - With Detail and Change
    AD
    Acknowledge - With Detail, No Change
    BAK-03
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    BAK-04
    373
    Date
    Required
    CCYYMMDD format

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

    • BAK04 is the date assigned by the purchaser to purchase order.

    Detail

    PO1 Loop
    RequiredMax >1
    PO1
    0100

    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
    PO1-02
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    • PO102 is quantity ordered.
    PO1-03
    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

    EA
    Each
    PO1-04
    212
    Unit Price
    Optional
    Min 1Max 15

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

    PO1-05
    639
    Basis of Unit Price Code
    Optional

    Code identifying the type of unit price for an item

    NT
    Net
    PO1-06
    235
    Product/Service ID Qualifier
    Optional

    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.
    SK
    Stock Keeping Unit (SKU)
    UP
    UCC - 12
    PO1-07
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    CTP
    0400

    Pricing Information

    OptionalMax use >1

    To specify pricing information

    Usage notes

    CTP segment ONLY needs to be returned if there has been a price change.

    Example
    If either Quantity (CTP-04) or Composite Unit of Measure (CTP-05) is present, then the other is required
    CTP-02
    236
    Price Identifier Code
    Optional

    Code identifying pricing specification

    RTL
    Retail
    CTP-03
    212
    Unit Price
    Optional
    Min 1Max 15

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

    • See Figures Appendix for an example detailing the use of CTP03 and CTP04.
    • See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
    CTP-04
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    CTP-05
    C001
    Composite Unit of Measure
    To identify a composite unit of measure (See Figures Appendix for examples of use)
    C001-01
    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

    EA
    Each
    ACK Loop
    RequiredMax >1
    ACK
    2700

    Line Item Acknowledgment

    RequiredMax use 1

    To acknowledge the ordered quantities and specify the ready date for a specific line item

    Example
    If either Quantity (ACK-02) or Unit or Basis for Measurement Code (ACK-03) is present, then the other is required
    If either Product/Service ID Qualifier (ACK-07) or Product/Service ID (ACK-08) is present, then the other is required
    If Date/Time Qualifier (ACK-04) is present, then Date (ACK-05) is required
    ACK-01
    668
    Line Item Status Code
    Required

    Code specifying the action taken by the seller on a line item requested by the buyer

    Usage notes

    A minimum of the ACK01 must be returned with the appropriate code.

    IA
    Item Accepted
    IB
    Item Backordered
    IC
    Item Accepted - Changes Made
    IP
    Item Accepted - Price Changed
    IQ
    Item Accepted - Quantity Changed
    IR
    Item Rejected
    IS
    Item Accepted - Substitution Made
    ACK-02
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    Usage notes

    ACK02 – only needs to be returned if the order quantity is being changed.

    ACK-03
    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

    EA
    Each
    ACK-04
    374
    Date/Time Qualifier
    Optional

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

    Usage notes

    ACK04 and ACK05 only need to be returned if you are changing the ship date

    068
    Current Schedule Ship
    ACK-05
    373
    Date
    Optional
    CCYYMMDD format

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

    Usage notes

    ACK04 and ACK05 only need to be returned if you are changing the ship date

    ACK-07
    235
    Product/Service ID Qualifier
    Optional

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

    Usage notes

    ACK07 and ACK08 only need to be returned if you are substituting an item (and only if you have the buyer’s approval).

    SK
    Stock Keeping Unit (SKU)
    UP
    UCC - 12
    ACK-08
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    ACK07 and ACK08 only need to be returned if you are substituting an item (and only if you have the buyer’s approval).

    DTM
    2800

    Date/Time Reference

    OptionalMax use 1

    To specify pertinent dates and times

    Usage notes

    DTM segment only needs to be returned if you are changing the delivery date.

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    067
    Current Schedule Delivery
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

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

    Summary

    CTT Loop
    OptionalMax >1
    CTT
    0100

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

    Total number of line items in the transaction set

    SE
    0300

    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

    Sample 855

    ST*855*41050001
    BAK*00*AD*0999999*20230323
    PO1**35*EA*53.00**UP*111111111111
    CTP**RTL*118.00*35*EA
    ACK*IA*35*EA
    PO1**35*EA*53.00**UP*111111111112
    CTP**RTL*118.00*35*EA
    ACK*IA*35*EA
    PO1**45*EA*53.00**UP*111111111113
    CTP**RTL*118.00*45*EA
    ACK*IA*45*EA
    PO1**45*EA*53.00**UP*111111111114
    CTP**RTL*118.00*45*EA
    ACK*IA*45*EA
    PO1**45*EA*53.00**UP*111111111115
    CTP**RTL*118.00*45*EA
    ACK*IA*45*EA
    PO1**35*EA*53.00**UP*111111111116
    CTP**RTL*118.00*35*EA
    ACK*IA*35*EA
    CTT*6

    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.