EDI 865 - Purchase Order Change Acknowledgement / Request - Seller Initiated

Read the guide below to learn about the EDI 865.

If you need to send or receive EDI 865s, contact our team of EDI experts today.

Speak with an EDI Expert
EDI Transaction Header

What is an EDI 865?

The EDI 865, commonly referred to as a Purchase Order Change Acknowledgement/Request, is a type of electronic data interchange transaction initiated by the seller. Its used to communicate with trading partners to accept or reject any previous purchase order change submitted by the buyer. Additionally, the document is also used to relay any changes to a purchase order by the seller (such as a manufacturer) to a previously submitted purchase order, typically an EDI 860 Purchase Order Change Request initiated by the buyer (such as a retailer).


These EDI 865 documents adhere to the x12 format established by the American National Standards Institute (ANSI), a non-profit organization responsible for regulating EDI formats in the United States.


How to use an EDI 865?

In general, Sellers can acknowledge buyer purchase order change requests with either an 855 Acknowledge or an 865 Acknowledgment. The choice between the two is usually specified in the buyer's EDI Guidelines. In the case of requiring the EDI 865, here are the exchanges of the process:


1. Buyers' Purchase Order Submission (EDI 850):
Buyers submit 850 Purchase Order transactions to sellers to order products.

2. Seller's Purchase Order Acknowledgment (EDI 855):
Sellers respond with an EDI 855 Purchase Order Acknowledgment, confirming the receipt and acceptance of the purchase order.

3. Buyer's Purchase Order Change Request (EDI 860):
If a buyer wishes to make changes to the original purchase order, they communicate these changes through an 860 Purchase Order Change Request transaction.

4. Seller's Acknowledgment of Changes (EDI 865):
The seller responds to the buyer's changes by either accepting or rejecting them, using an 865 Acknowledgment. Sellers can also initiate changes by submitting an 865 Request.

5. Functional Acknowledgment (EDI 997):
Once the buyer receives the EDI 865, a confirmation is sent back to the seller in the form of an EDI 997 (Functional Acknowledgment) to indicate the successful reception of the EDI 865 transaction.


The EDI 865 transaction contains much of the same information as the original purchase order (850 transaction set), such as product descriptions, quantities, shipping details, terms, and costs. Additionally, it includes specific references to changes from the original purchase order and a code indicating whether the document is a Request or an Acknowledgment.


In complying with a trading partner's EDI requirements, Cleo facilitates a quick and easy transition to meet those standards. Contact EDI experts at Cleo to learn more.

What Makes Up an EDI 865?

The EDI 865 is used to confirm or reject changes to an original order, and it typically includes similar information as the EDI 860, such as product details, quantities, buyer and seller info, and shipping details. The key focus of the EDI 865 is confirming changes to the original order, which can involve adjustments like:

Quantity or product type changes
Adding new items
Deleting items
Changing prices

The seller can also specify whether a proposed change was rejected, accepted, or accepted with additional adjustments. For instance, a supplier might agree to add more items but adjust the quantity based on product availability.

EDI 855 document components in CIC
EDI transaction automation

Automate EDI / API Transactions

Eliminate manual integration flows by automating and orchestrating EDI and API-based transactions in an intuitive self-service, low-code development environment. 

Not ready for self-service? Leverage Cleo’s Managed Services team to get you up and running.

Keep a list of all X12 EDI transaction sets at hand.

Access a free EDI Transaction Set Guide

More EDI Resources

Explore additional EDI resources to deepen your understanding and enhance your proficiency in Electronic Data Interchange.

  • EDI compliance
    3 Ways to Become EDI Compliant & Eliminate EDI Chargebacks

    Many major companies have requirements for EDI trading partner setup and maintenance, both of which are important in keeping compliant...

    Read the Blog
  • EDI visibility
    EDI Visibility & Business Insights

    23% of companies say visibility is one of their biggest integration challenges. Let's analyze this issue and unleash a powerful solution...

    Read More
  • Cleo Integration Cloud EDI integration video resource
    EDI Integration in Action

    Explore a curated list of videos to help you understand the unprecedented value of EDI integration...

    Start Watching