Cloud-based Accounting Integration
The #1 Integration Platform | 1 800 755 6921
Find us on:

EDI - Connecting your Accounting to a World of Trading Partners
Next Steps
Contact me
Request more information

Request Information
Name:*
Company:
Phone:*
Email:*
Accounting package:
Questions or comments:
Please include me in the eBridge mailing list.

EDI Document Type - 860 Purchase Order Change Request

What is an 860 Purchase Order Change Request?

One of the most common EDI document types is the EDI 860 Purchase Order Change Request.  The 860 document type is an electronic version of a paper Purchase Order Change Request.  Standard EDI formats include X12, ANSI, EDIFACT and its subsets. Click here to read more about supported EDI Standards.


The 860 EDI document type is used provide information required for the established business and industry practices relating to a purchase order change. The transaction can be used by the buyer to request a change to a previous purchase order, or by a buyer to confirm acceptance of a purchase order change sent by the seller or by mutual agreement of both parties.

What makes up the 860 Purchase Order Change Request document?

An 860 EDI Purchase Order Change Request is organized into the following segment and data elements.  A segment can contain at least one data element.  Each data element contains a data field. Data elements could include vendor number, purchase order number, items, quantities, and corrections, like in a paper purchase order change request. There are an infinite number of possibilities available for a company to include data on an 860 Purchase Order Change Request.

How is it used?

The 860 EDI document is used either by the buyer to request a change to an existing purchase order, or by a buyer to confirm acceptance of a purchase order change sent by the seller. After the 860 Purchase Order Change Request is received, a 997 Functional Acknowledgment is sent back from the buyer indicating that the Purchase Order Change Request was successfully received. 

The Process and Standards

An EDI solution is required to process the EDI documents received into a financial system (click here to view all available financial systems eBridge integrates into) or into a readable format for manual entry.  Each trading partner will have an EDI Implementation guide outlining the specific segments, data elements, values accepted, and the applicable business rules to be followed. 

Click here to find your trading partner

Why eBridge Connections?

Integration with Sage MAS 90, MAS 200, MAS 500, PFW, Business Vision, Sage Pro and more
EDI integration with Microsoft Dynamics Navision, Microsoft Dynamics Axapta and more
 
Integration with Epicor Enterprise, Vantage and iScala
 

Click here for information on benefits, pre-configured trading partner connections, EDI document types and more