BCA
Beginning segment for purchase order change acknowledgment: the acknowledgment type, the PO number and date, and the change or acknowledgment date.
EDI 865: Purchase Order Change Acknowledgment / Request (Seller Initiated)
The seller’s answer to a buyer’s change request, or a change the seller proposes on its own. Supplier to buyer. This page covers what the 865 is for, the segments you meet when you open one, the documents it travels with, where it tends to go wrong, and how it moves over AS2 into your systems on Files.com, which receives, parses, validates, and routes it as configuration.
No credit card required · 7-day free trial · Live in minutes
#1 MFT vendor in Gartner Peer Insights
Trusted by 4,000+ companies
Every protocol included
What The 865 Is For
The 865 does two jobs. It acknowledges an 860, telling the buyer which requested changes the seller accepts or rejects, line by line. And it lets the seller initiate a change to an order the buyer placed, proposing a substitution, a different quantity, or a new date, which the buyer then accepts or rejects.
It keeps both sides’ view of a changed order in sync before goods move, which matters most in long-lead or high-volume relationships where the original 850 is rarely what ships.
The Segments You Meet First
In document order, the segments that carry the 865's meaning. A partner's implementation guide says which are required and which fields each must hold.
REF
References including the seller’s order number.
POC
Line item change: the change type, quantities, prices, and identifiers.
ACK
Line item acknowledgment: the status of each changed line and its date.
CTT
Transaction totals.
Where It Goes Wrong
Confusing the two roles. An 865 that acknowledges an 860 and an 865 that proposes a seller change use the same document with different codes in BCA, and a translator that maps them the same way applies changes nobody agreed to.
The Documents It Travels With
The 865 rarely moves alone. These are the documents that precede, answer, or settle it.
860 · Purchase Order Change Request (Buyer Initiated)
A buyer’s change to an order already sent: add, delete, or modify lines, quantities, prices, or dates.
See The 860850 · Purchase Order
A buyer’s order to a supplier: the items, quantities, prices, dates, and ship-to locations.
See The 850855 · Purchase Order Acknowledgment
The supplier’s answer to a purchase order: accepted, rejected, changed, or backordered, line by line.
See The 855997 · Functional Acknowledgment
The receipt that says an EDI transmission arrived and was parsed, with any syntax errors found.
See The 997How The 865 Moves On Files.com
A partner sends the 865 over AS2, SFTP, or FTPS, and it lands in that partner’s inbox folder on Files.com with the transport receipt recorded. From there it is a workflow, not a project: TransformScript parses the X12 natively into the JSON, CSV, or XML your ERP or WMS reads, content validation flags a document whose contents are wrong before anything ingests it, and an automation routes the result to the system and the people who act on it.
Outbound is the mirror image. Your system exports its record, TransformScript builds the 865 the partner’s guide specifies, and the file dropped in the partner’s outbox goes out over AS2 with automatic retries until the MDN confirms delivery. Every transmission in both directions is in the audit log, and delivery monitoring alerts when a 865 that was due never arrives. The full picture is on the EDI software page.
EDI 865 Questions
What teams ask about the 865 and how it moves on Files.com.
An EDI 865 is the X12 Purchase Order Change Acknowledgment/Request, Seller Initiated. The seller uses it to accept or reject a buyer’s 860 change request line by line, or to propose its own change to an existing order.
Yes. Files.com is a standards-compliant RFC 4130 AS2 endpoint, and a 865 sent by a trading partner lands in that partner’s inbox folder with a signed MDN receipt returned to the sender. Partners who exchange over SFTP or FTPS connect to the same platform and the document lands in the same place.
Yes. TransformScript parses the X12 865 natively and writes the JSON, CSV, or XML your systems ingest, as a step in the workflow that fires when the document arrives. Outbound, the same engine builds a 865 from your system’s export and drops it in the partner’s outbox for delivery.
Exchange The 865 Without The Legacy Stack
Start the 7-day trial, turn AS2 on, and exchange certificates with your partner. The 865 lands in their folder, parses into the record your system reads, and every transmission carries a signed receipt.
No credit card required • Free for 7 days • Live in minutes