Purchase Order Acknowledgment: Standard EDI payload – TradeCentric

The X12 855 purchase order acknowledgment (POA) request payload sends a POA from your system, such as your eCommerce platform or ERP system, to the TradeCentric platform so that we can deliver the POA to the buyer's eProcurement system. For standard integrations that send EDI payloads, we accept POAs in our standard EDI format.

This article describes the standard EDI format to use for this payload.

Important: This payload is for POAs associated with POs only. The payload must include the buyer PO identifier from the PO request payload that we sent.

Jump to:

Request payload (to TradeCentric)

Request segment details

Envelope
Heading
Detail
Summary

Request payload (to TradeCentric)

The code block below shows an example POA request payload in our standard EDI format:

X12

855

POA request

ISA*00*          *00*          *ZZ*SUPPLIER_INC   *ZZ*TEST_CORP      *221118*1057*U*00401*000000002*0*P*>~
GS*PR*SUPPLIER_INC*TEST_CORP*20221118*1057*2*X*004010~
ST*855*0001~
BAK*00*AD*PO-123*20221118~
REF*ZZ*93369535150910.10.57.136~
DTM*002*20221225~
N1*BY*TEST_CORP~
N1*SU*SUPPLIER_INC~
N1*ST*Test Corp. - Nashville Branch~
N3*123 Test St.; Suite A~
N4*Nashville*TN*37011*US~
PER*CN*Contact Name*TE*8885559876*EM*contact@buyer.com~
N1*BT*Test Corp. - Nashville Branch~
N3*123 Test St.; Suite A~
N4*Nashville*TN*37011*US~
PER*CN*Contact Name*TE*8885559876*EM*contact@buyer.com~
PER*BD*Contact Name*TE*8885551234*EM*contact@buyer.com~
PO1*101*3*EA*41.15**BP*45L017*VP*CART12-ITEM123~
PID*F****Low Arc Kitchen Faucet: Dominion Faucets, Silver, Chrome Finish, 1.75 gpm Fl~
ACK*IA*3*EA*002*20221225~
CTT*1~
SE*20*0001~
GE*1*2~
IEA*1*000000002~

Request segment details

A standard POA request EDI payload has envelope, heading, detail, and summary sections. The subsections explain the segments and fields in each payload section.

String and number types: ID = standard EDI code, AN = alphanumeric text, N0 = whole number, N2 = decimal number without decimal point, R = decimal number with decimal point

Envelope

Contains the entire payload and provides the general identifying information described in the subsections below

ISA - Interchange control header

Required Max use: 1

Provides identifying information about the payload

Example

ISA*00*          *00*          *ZZ*SUPPLIER_INC   *ZZ*TEST_CORP      *221118*1057*U*00401*000000002*0*P*>~

ISA field breakdown

ISA-01

Authorization information qualifier

RequiredType: String (ID)Length: 2

Specifies the type of authorization information included

Example: 00 = no authorization information is included
ISA-02

Authorization information

RequiredType: String (AN)Length: 10

Provides the authorization value when authorization information is included

Example: blank in this payload
ISA-03

Security information qualifier

RequiredType: String (ID)Length: 2

Specifies whether security information is included

Example: 00 = no security information is included
ISA-04

Security information

RequiredType: String (AN)Length: 10

Provides the security value when security information is included

Example: blank in this payload
ISA-05

Sender qualifier

RequiredType: String (ID)Length: 2

Specifies the type of sender identifier provided

Example: ZZ = mutually defined by buyer and supplier
ISA-06

Sender identifier

RequiredType: String (AN)Length: 15

Provides the sender identifier

Example: SUPPLIER_INC
ISA-07

Receiver qualifier

RequiredType: String (ID)Length: 2

Specifies the type of receiver identifier provided

Example: ZZ = mutually defined by buyer and supplier
ISA-08

Receiver identifier

RequiredType: String (AN)Length: 15

Provides the receiver identifier

Example: TEST_CORP
ISA-09

Interchange date

RequiredFormat: YYMMDD

Provides the date when the payload was created

Example: 221118 = November 18, 2022
ISA-10

Interchange time

RequiredFormat: HHMM

Provides the time when the payload was created

Example: 1057 = 10:57
ISA-11

Interchange control standards identifier

RequiredType: String (ID)Length: 1

Specifies the standards organization that defines the format used for the payload

Example: U = U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12

Interchange control version code

RequiredType: String (ID)Length: 5

Specifies the X12 version used for the payload

Example: 00401
ISA-13

Interchange control number

RequiredType: Numeric (N0)Length: 9

Provides a unique control number for the payload

Example: 000000002
ISA-14

Acknowledgment requested

RequiredType: String (ID)Length: 1

Specifies whether your organization requests an acknowledgment that the buyer received this document

Values: 0 = no acknowledgment requested, 1 = acknowledgment requested
ISA-15

Interchange usage indicator code

RequiredType: String (ID)Length: 1

Indicates how the receiver should process the payload

Example: P = production data

Other codes: T = test data, I = informational data
ISA-16

Component element separator

RequiredType: DelimiterLength: 1

Specifies the unique character used to separate multiple values within one field

Example: >

GS - Functional group header

Required Max use: 1

Assigns a functional group to the POA in the payload

Note: We recommend one functional group per payload so that errors in one group don’t affect other groups in the same payload.

Example

GS*PR*SUPPLIER_INC*TEST_CORP*20221118*1057*2*X*004010~

GS field breakdown

GS-01

Functional identifier code

RequiredType: String (ID)Length: 2

Specifies the transaction type for the group

Must be PR
GS-02

Application sender's code

RequiredType: String (AN)Length: 2-15

Provides the sender code for the group

Example: SUPPLIER_INC
GS-03

Application receiver's code

RequiredType: String (AN)Length: 2-15

Provides the receiver code for the group

Example: TEST_CORP
GS-04

Group date

RequiredFormat: YYYYMMDD

Provides the date when the group was created

Example: 20221118 = November 18, 2022
GS-05

Group time

RequiredFormat: HHMM

Provides the time when the group was created

Example: 1057 = 10:57
GS-06

Group control number

RequiredType: Numeric (N0)Length: 1-9

Provides the unique control number that your organization generated for the group

Example: 2
GS-07

Responsible agency code

RequiredType: String (ID)Length: 1

Specifies the standards organization that defines the format used for the group

Must be X
GS-08

Version or release code

RequiredType: String (AN)Length: 1-12

Provides the X12 version used for the group

Example: 004010

Heading

Starts the POA and provides the identifying information, reference information, and contact details described in the subsections below

ST - Transaction set header

Required Max use: 1

Starts the POA document

Note: We recommend one transaction set, meaning one document, per payload so that errors in one document don’t affect other documents in the same payload.

Example

ST*855*0001~

ST field breakdown

ST-01

Transaction set identifier code

RequiredType: String (ID)Length: 3

Specifies the transaction type

Must be 855
ST-02

Transaction set control number

RequiredType: String (AN)Length: 4-9

Provides the control number that your organization generated for the transaction set

Example: 0001

BAK - Beginning segment for POA

Required Max use: 1

Provides identifying information about the POA

Example

BAK*00*AD*PO-123*20221118~

BAK field breakdown

BAK-01

Transaction set purpose code

RequiredType: String (ID)Length: 2

Specifies the purpose of the transaction set

Example: 00 = original

Other common codes: 01 = cancellation, 05 = replacement, 07 = duplicate
BAK-02

Acknowledgment type code

RequiredType: String (ID)Length: 2

Specifies the type of POA, such as accepted or rejected, and whether it includes details or changes

Example: AD = acknowledge with details but no changes

Other common codes: AC = acknowledge with details and changes, AT = accepted, RD = rejected with details
BAK-03

Buyer PO identifier

RequiredType: String (AN)Length: 1-22

Provides the buyer PO identifier from the PO request payload that we sent

Example: PO-123
BAK-04

Buyer's PO date

RequiredFormat: YYYYMMDD

Provides the PO date from the PO request payload that we sent

Example: 20221118 = November 18, 2022

REF - Reference information

Optional Max use: 12

Provides additional reference information, which may vary depending on the integration's requirements

Example

REF*ZZ*93369535150910.10.57.136~

REF field breakdown

REF-01

Reference identification qualifier

Required if REF is usedType: String (ID)Length: 2-3

Specifies the type of reference value

Example: ZZ = mutually defined by buyer and supplier

Other common codes: DP = department number, IA = buyer's internal vendor number
REF-02

Reference identification

Required if REF is usedType: String (AN)Length: 1-30

Provides the reference value

Example: 93369535150910.10.57.136 = PO payload identifier

DTM - Date and time reference

Optional Max use: 10

Provides a relevant date for the POA

Example

DTM*002*20221225~

DTM field breakdown

DTM-01

Date or time qualifier

RequiredType: String (ID)Length: 3

Specifies the type of date provided

Example: 002 = delivery requested on date

Other common codes: 010 = shipping requested on date, 068 = shipping currently scheduled on date, 106 = required by date
DTM-02

Date

RequiredFormat: YYYYMMDD

Provides the date

Example: 20221225 = December 25, 2022

N1 loop - Parties, addresses, and contacts

Typically required Max use: 200

Provides the organizations, addresses, and contact details for the POA

Note: Repeat this loop for each organization or address involved in the transaction. For example, if the billing address is different from the buyer's address, include a segment for the buyer and a separate segment for billing.

Example

N1*BY*TEST_CORP~
N1*SU*SUPPLIER_INC~
N1*ST*Test Corp. - Nashville Branch~
N3*123 Test St.; Suite A~
N4*Nashville*TN*37011*US~
PER*CN*Contact Name*TE*8885559876*EM*contact@buyer.com~
N1*BT*Test Corp. - Nashville Branch~
N3*123 Test St.; Suite A~
N4*Nashville*TN*37011*US~
PER*CN*Contact Name*TE*8885559876*EM*contact@buyer.com~
PER*BD*Contact Name*TE*8885551234*EM*contact@buyer.com~

N1 loop breakdown

N1
Name

Typically required

Identifies the organization or location and provides its name
- N1-01 Entity identifier code
  
  Required if N1 is usedType: String (ID)Length: 2-3
  
  Specifies the type of organization or location
  
  Example: BY = buyer
  
  Other common codes: SU = supplier, ST = ship to, BT = bill to
- N1-02 Name
  
  Required if N1 is usedType: String (AN)Length: 1-60
  
  Provides the name of the organization or location
  
  Example: TEST_CORP
Example: N1*BY*TEST_CORP~
N3
Address information

Optional

Provides street address details for the organization or location
- N3-01 Address information
  
  Required if N3 is usedType: String (AN)Length: 1-55
  
  Provides the first line of the street address
  
  Example: 123 Test St.; Suite A
- N3-02 Address information
  
  OptionalType: String (AN)Length: 1-55
  
  Provides the second line of the street address
  
  Example: blank in this payload
Example: N3*123 Test St.; Suite A~
N4
Geographic location

Optional

Provides city, region, postal code, and country details
- N4-01 City name
  
  Required if N4 is usedType: String (AN)Length: 2-30
  
  Provides the city for the organization or location
  
  Example: Nashville
- N4-02 State or province code
  
  OptionalType: String (ID)Length: 2
  
  Provides the state, province, or region code
  
  Example: TN
- N4-03 Postal code
  
  OptionalType: String (ID)Length: 3-15
  
  Provides the postal code
  
  Example: 37011
- N4-04 Country code
  
  OptionalType: String (ID)Length: 2-3
  
  Provides the country code
  
  Example: US
Example: N4*Nashville*TN*37011*US~
PER
Administrative communications contact

Typically required

Provides the contact details for the organization or location
- PER-01 Contact function code
  
  Required if PER is usedType: String (ID)Length: 2
  
  Specifies the role of the contact
  
  Example: CN = general contact
  
  Other common codes: BD = buyer contact, DC = delivery contact
- PER-02 Name
  
  OptionalType: String (AN)Length: 1-60
  
  Provides the contact name
  
  Example: Contact Name
- PER-03 / PER-04 Communication number
  
  Optional
  
  Provides a communication method for the contact
  - PER-03 Communication number qualifier
    
    Required if PER-04 is usedType: String (ID)Length: 2
    
    Specifies the type of communication method provided
    
    Example: TE = telephone number
    
    Other common codes: EM = email, FX = fax
  - PER-04 Communication number
    
    Required if PER-03 is usedType: String (AN)Length: 1-256
    
    Provides the value for the communication method
    
    Example: 8885559876
- PER-05 / PER-06 Additional communication number
  
  Optional
  
  Provides an additional communication method for the contact
  - PER-05 Communication number qualifier
    
    Required if PER-06 is usedType: String (ID)Length: 2
    
    Specifies the type of communication method provided
    
    Example: EM = email
    
    Other common codes: TE = telephone number, FX = fax
  - PER-06 Communication number
    
    Required if PER-05 is usedType: String (AN)Length: 1-256
    
    Provides the value for the communication method
    
    Example: contact@buyer.com
Example: PER*CN*Contact Name*TE*8885559876*EM*contact@buyer.com~

Detail

Provides the POA item details, which are described in the subsections below

Note: Repeat these segments for each line item, starting with PO1.

PO1 - Baseline item data

Required Max use: 100000

Provides the main details about each line item

Example

PO1*101*3*EA*41.15**BP*45L017*VP*CART12-ITEM123~

PO1 field breakdown

PO1-01

Assigned identification

OptionalType: String (AN)Length: 1-20

Provides the line item identifier, which is often the line number

Example: 101
PO1-02

Quantity

RequiredType: Decimal number (R)

Provides the acknowledged item quantity

Example: 3
PO1-03

Unit of measure

RequiredType: String (ID)Length: 2

Specifies the unit of measure for the quantity

Example: EA = each
PO1-04

Unit price

OptionalType: Decimal number (R)

Provides the price of one unit

Example: 41.15
PO1-06 / PO1-07
Product or service identifier

Optional

Provides an item identifier, such as a part number or Stock Keeping Unit (SKU)
- PO1-06 Identifier qualifier
  
  Required if PO1-07 is usedType: String (ID)Length: 2
  
  Specifies the type of item identifier provided
  
  Example: BP = buyer's part number
- PO1-07 Identifier
  
  Required if PO1-06 is usedType: String (AN)Length: 1-80
  
  Provides the identifier value
  
  Example: 45L017
Example: BP*45L017
PO1-08 / PO1-09
Additional product or service identifier

Optional

Provides an additional item identifier, such as to indicate a specific color or packaging option
- PO1-08 Identifier qualifier
  
  Required if PO1-09 is usedType: String (ID)Length: 2
  
  Specifies the type of additional item identifier provided
  
  Example: VP = vendor's part number
- PO1-09 Identifier
  
  Required if PO1-08 is usedType: String (AN)Length: 1-80
  
  Provides the identifier value
  
  Example: CART12-ITEM123
Example: VP*CART12-ITEM123

PID - Product or item description

Optional Max use: 1000

Provides a description for each line item

Example

PID*F****Low Arc Kitchen Faucet: Dominion Faucets, Silver, Chrome Finish, 1.75 gpm Fl~

PID field breakdown

PID-01

Item description type

RequiredType: String (ID)Length: 1

Specifies the description format

Example: F = free-form text
PID-05

Description

Required if PID-01 is F or XType: String (AN)Length: 1-80

Provides the item description text

Example: Low Arc Kitchen Faucet: Dominion Faucets, Silver, Chrome Finish, 1.75 gpm Fl

ACK - Line item acknowledgment

Required Max use: 104

Provides status details for each line item

Example

ACK*IA*3*EA*002*20221225~

ACK field breakdown

ACK-01

Line item status code

RequiredType: String (ID)Length: 2

Specifies the action taken for the line item

Example: IA = item accepted

Other common codes: IB = item backordered, IC = item accepted with changes, IR = item rejected
ACK-02

Quantity

Required if ACK-03 is usedType: Decimal number (R)

Provides the acknowledged quantity for the line item

Example: 3
ACK-03

Unit of measure

Required if ACK-02 is usedType: String (ID)Length: 2

Specifies the unit of measure for the acknowledged quantity

Example: EA = each
ACK-04

Date or time qualifier

OptionalType: String (ID)Length: 3

Specifies the type of date provided

Example: 002 = delivery requested on date
ACK-05

Date

Required if ACK-04 is usedFormat: YYYYMMDD

Provides the qualifier date for the line item

Example: 20221225 = December 25, 2022

Summary

Ends the POA and the payload using the summary details described in the subsections below

CTT - Transaction totals

Optional Max use: 1

Provides the line item total for the POA

Example

CTT*1~

CTT field breakdown

CTT-01

Number of line items

Required if CTT is usedType: Numeric (N0)Length: 1-6

Provides the total number of PO1 segments in the transaction set

Example: 1

SE - Transaction set trailer

Required Max use: 1

Ends the POA

Example

SE*20*0001~

SE field breakdown

SE-01

Number of included segments

RequiredType: Numeric (N0)Min value: 1

Provides the total number of segments from ST through SE

Example: 20
SE-02

Transaction set control number

RequiredType: String (AN)Length: 4-9

Provides the same control number as ST-02

Example: 0001

GE - Functional group trailer

Required Max use: 1

Ends the functional group that contains the POA

Example

GE*1*2~

GE field breakdown

GE-01

Number of transaction sets included

RequiredType: Numeric (N0)

Provides the number of POAs in the group

Recommended value: 1
GE-02

Group control number

RequiredType: Numeric (N0)Length: 1-9

Provides the same control number as GS-06

Example: 2

IEA - Interchange control trailer

Required Max use: 1

Ends the payload

Example

IEA*1*000000002~

IEA field breakdown

IEA-01

Number of included functional groups

RequiredType: Numeric (N0)

Provides the number of functional groups in the payload

Recommended value: 1
IEA-02

Interchange control number

RequiredType: Numeric (N0)Length: 9

Provides the same control number as ISA-13

Example: 000000002

Request payload (to TradeCentric)

Request segment details

Envelope

ISA - Interchange control header

Authorization information qualifier

Authorization information

Security information qualifier

Security information

Sender qualifier

Sender identifier

Receiver qualifier

Receiver identifier

Interchange date

Interchange time

Interchange control standards identifier

Interchange control version code

Interchange control number

Acknowledgment requested

Interchange usage indicator code

Component element separator

GS - Functional group header

Functional identifier code

Application sender's code

Application receiver's code

Group date

Group time

Group control number

Responsible agency code

Version or release code

Heading

ST - Transaction set header

Transaction set identifier code

Transaction set control number

BAK - Beginning segment for POA

Transaction set purpose code

Acknowledgment type code

Buyer PO identifier

Buyer's PO date

REF - Reference information

Reference identification qualifier

Reference identification

DTM - Date and time reference

Date or time qualifier

Date

N1 loop - Parties, addresses, and contacts

Name

Address information

Geographic location

Administrative communications contact

Detail

PO1 - Baseline item data

Assigned identification

Quantity

Unit of measure

Unit price

Product or service identifier

Additional product or service identifier

PID - Product or item description

Item description type

Description

ACK - Line item acknowledgment

Line item status code

Quantity

Unit of measure

Date or time qualifier

Date

Summary

CTT - Transaction totals

Number of line items

SE - Transaction set trailer

Number of included segments

Transaction set control number

GE - Functional group trailer

Number of transaction sets included

Group control number

IEA - Interchange control trailer

Number of included functional groups

Interchange control number

Related articles