Skip to main content

EDI 855 - Purchase Order Acknowledgement

What is the EDI 855 - Purchase Order Acknowledgement? EDI 855 - Purchase Order Acknowledgment

The EDI 855 Purchase Order Acknowledgement is used by sellers to confirm receipt and acceptance, rejection, or modification of an EDI 850 Purchase Order eliminating the need to call or fax a confirmation.  

The Purchase Order Acknowledgement (855) contains all information normally associated with a purchase order and like other acknowledgement transactions, closes the loop on communication by ensuring both buyer and seller are aligned on product, quantity, price, and delivery terms.  

The 855 can indicate that the order was accepted, rejected or accepted with changes and may even suggest changes to orders, establishing it as a critical transaction in the order-to-cash cycle.
 

How does PartnerLinQ use the EDI 855 - Purchase Order Acknowledgement? 

PartnerLinQ leverages the 855 to streamline supplier responses to buyer orders. It supports full, partial, or modified acceptance of purchase orders, automatically updating ERP and OMS systems. PartnerLinQ also provides visibility into rejections and reasons, ensuring buyers can quickly adjust forecasts and replenishment plans. This integration helps minimize delays and disputes in procurement cycles. 
 

What responses to the EDI 855 - Purchase Order Acknowledgement are expected/sent? 

The EDI 855 functions as the formal response to an EDI 850 Purchase Order. Common responses include: 

  • AC: Acknowledge – With Detail and Change
  • AK: Acknowledge – No Detail or Change
  • RJ: Reject – No Detail
  • RD: Reject with Detail – requires rejection details 

Subsequent adjustment details may be communicated by the buyer to the seller through “change by refresh”, the 860 (Purchase Order Change) or by the seller with shipment details in the 856 (Advance Ship Notice). 
 

What does the EDI 855 - Purchase Order Acknowledgement support? 

The 855 supports synchronized procurement by ensuring both trading partners agree to the terms of an order before fulfillment. It provides a legal and audit trail, demonstrates compliance with buyer mandates, and reduces costly errors by clarifying accepted quantities, pricing, and ship dates. 
 

What are the Key Features of the EDI 855 - Purchase Order Acknowledgement? 

  • Confirms, Application Programming Interfacerejects, or modifies purchase orders
  • Provides line-item level acceptance/rejection
  • Communicates dates, pricing, and delivery terms
  • Integrates with ERP and supply chain planning tools
  • Enhances visibility into supplier commitments 
     

What is the Purpose of the EDI 855 - Purchase Order Acknowledgement? 

The purpose of the EDI 855 is to allow sellers to electronically confirm acceptance, rejection, or proposed changes to purchase orders, thereby reducing manual interventions, accelerating order cycles, and ensuring compliance. 
 

What Information is Included in the EDI 855 - Purchase Order Acknowledgement? 

Typical information carried in the 855 includes: 

  • PO number and reference identifiers
  • Acknowledgement type (BAK02)
  • Item details and quantities (PO1)
  • Rejection or modification reasons
  • Delivery and scheduling details (DTM, TD5)
  • Allowances, charges, and terms (SAC, ITD) 
     

What are the Essential Components of the EDI 855 - Purchase Order Acknowledgement? 

SegmentDescription
STTransaction Set Header
BAKBeginning Segment for Purchase Order Acknowledgement
REFReference Identification
N1-N4Name and Address segments
PO1Baseline Item Data
PIDProduct/Item Description
SACAllowances/Charges
TD5Carrier Details
MSGMessage Text

 

What are the Common Segments Included in the EDI 855 - Purchase Order Acknowledgement? 

SegmentDescription
BAKAcknowledgement information
REFPO and reference identifiers
N1Buyer, Seller, Ship-to parties
PO1Line items
SACAllowances/Charges
PRFPurchase Order references
PIDItem descriptions

 

What Status Codes are used with the EDI 855 - Purchase Order Acknowledgement? 

Key Acknowledgement codes (BAK02): 

  • AC = Acknowledge, order accepted
  • RJ = Reject, order not accepted
  • RD = Reject with Detail, partial acceptance/rejection at line level 
     

What Reason Codes are used with the EDI 855 - Purchase Order Acknowledgement? 

Reason codes may appear in: 

  • SAC04 to explain allowance or charge reasons 
  • N9/MSG to provide rejection or modification explanations 

    Examples: damaged goods, incorrect pricing, discontinued item. 
     

What Use Cases does the EDI 855 - Purchase Order Acknowledgement? 

  • Retail AS2replenishment cycle (confirming POs)
  • Manufacturing supplier responses
  • Distribution and wholesale compliance with buyer mandates
  • Exception management through rejections or partial acceptance 
     

What are the Benefits of the EDI 855 - Purchase Order Acknowledgement? 

  • Ensures alignment on order details before shipment
  • Reduces disputes and costly returns
  • Improves forecasting and planning accuracy
  • Provides electronic audit trail for compliance 
     

How efficient is the EDI 855 - Purchase Order Acknowledgement? 

The EDI 855 - Purchase Order Acknowledgement reduces cycle times by automating supplier order responses and eliminating the need to call or fax a confirmation.  
 

How Compliant is the EDI 855 - Purchase Order Acknowledgement? 

The EDI 855 - Purchase Order Acknowledgement supports buyer/supplier compliance programs, trade agreements and mandates. 
 

What is the Format of the EDI 855 - Purchase Order Acknowledgement? 

The EDI 855 - Purchase Order Acknowledgement follows ASC X12 formatting rules for Purchase Order Acknowledgement. 
 

How Accurate is the EDI 855 - Purchase Order Acknowledgement? 

The EDI 855 - Purchase Order Acknowledgement improves the accuracy of procurement to pay cycles by clarifying accepted and rejected order and items, standardizing data exchange protocols for consistency and enhancing performance. 
 

What are the Limitations of the EDI 855 - Purchase Order Acknowledgement? 

The EDI 855 requires careful mapping between buying and selling systems and personas particularly when it comes to the more complex scenarios (e.g., partial acceptance with substitutions), and scenarios which require detection, alerting, notifications, or custom workflows and configuration. 
 

Are Guidelines & Sample Files for the EDI 855 - Purchase Order Acknowledgement available? 

Yes. PartnerLinQ provides sample EDI 855 - Purchase Order Acknowledgement Transaction and implementation guides through its Support and Guideline Management Team
Sample EDI 855 implementation guides illustrate both inbound and outbound flows, segment layouts, and valid data examples and support testing and partner onboarding. Customized specification documents for use in on boarding and technical development are available upon request.  

PartnerLinQ provides: 

  • EDI 855 - Purchase Order Acknowledgement transaction implementation guide
  • Sample payloads
  • Qualification and testing maps
  • Error handling and best-practice notes 

Contact our experts.
 

Sample

 

What are the Basic Questions for EDI Integration with the EDI 855 - Purchase Order Acknowledgement? 

  1. Are there Samples and Specs available?
  2. What Acknowledgement Type codes must be supported?
  3. How are acceptance codes managed?
  4. How are rejection codes managed?
  5. How will rejections and modifications be communicated?
  • Are line-item rejections supported?
  • Are partial acceptances allowed?
  1. How should ERP systems handle amended orders
  2. Is there any scenario related to price or carrier information change in 855?
  3. What is the trigger for Order confirmation?
  4. How are cancellation scenarios managed?
  5. Are we canceling the complete Order?
  6. Are we canceling individual lines?
  7. Which SAC allowance/charge codes must be included? 
    How should ERP/OMS handle partial acknowledgements?
  8. Is customization specific to the Customer?
  9. Are there any rejection reason codes that require transformation?
  10. Are there SLAs for the 855?
  11. Is there any Scenario where the EDI Order is modified after the confirmation? 
     

What Business Level Workflow does the EDI 855 - Purchase Order Acknowledgement support?  

  1. Buyer issues an EDI 850 Purchase Order.
  2. Seller reviews and responds with an EDI 855.
  3. Seller either accepts, rejects, or modifies the PO.
  4. Buyer reviews the acknowledgement.
  5. Adjustments are finalized through an 860 or shipment proceeds with an 856.
  6. Invoice (810) closes the cycle. 
     
EDI 855 - Purchase Order Acknowledgment

 

What are the Best Practices for using the EDI 855 - Purchase Order Acknowledgement?

  • Respond promptly with 855 acknowledgements.
  • Use correct BAK02 status codes (AC, RJ, RD).
  • Provide clear rejection reasons in N9/MSG segments.
  • Align SAC allowances/charges with contracts.
  • Maintain consistency with buyer compliance guides. 
     

What Transactions are associated with the EDI 855 - Purchase Order Acknowledgement? 

TransactionANSI X12 – Role/Description
850850 Purchase Order
855855 Purchase Order Acknowledgement
860860 Purchase Order Change
856856 Advance Ship Notice
810810 Invoice
997997 Functional Acknowledgement

Explore Our Integration Solutions

Integration Solutions

PartnerLinQ Integration Solutions

Connect Everything. Integrate Intelligently.

Future-Proof Your Business with Composable, AI Powered Connectivity.

×