BPT
Beginning segment for product transfer and resale: report type, reference, and date.
EDI 867: Product Transfer and Resale Report
A distributor’s report to a manufacturer of what it sold, to whom, and what it transferred between locations. Distributor or reseller to manufacturer. This page covers what the 867 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 867 Is For
The 867 reports sell-through and transfers. A distributor sends it to the manufacturer whose products it carries to say what was sold, to which end customers, at what price and quantity, and what moved between the distributor’s own locations. Manufacturers use it for channel visibility, rebate and commission calculation, and demand planning.
It underpins ship-and-debit and rebate programs in industries such as electronics and industrial distribution, where the manufacturer credits the distributor for sales made below list to specific customers. Accuracy here is money.
The Segments You Meet First
In document order, the segments that carry the 867's meaning. A partner's implementation guide says which are required and which fields each must hold.
N1
Parties: the reporting distributor and the end customer for each transfer.
PTD
Product transfer and resale detail: the transaction type (sale, return, transfer) and references.
LIN
Item identification.
QTY
The quantity sold or transferred.
AMT
Monetary amounts such as the resale price.
Where It Goes Wrong
End-customer identification. Rebate programs depend on knowing who the distributor sold to, and inconsistent customer names and addresses across reports make claims disputable. Reporting periods that do not align with the manufacturer’s program periods cause the rest.
The Documents It Travels With
The 867 rarely moves alone. These are the documents that precede, answer, or settle it.
852 · Product Activity Data
A retailer’s report of sales and inventory movement by product and location, sent back to the supplier.
See The 852844 · Product Transfer Account Adjustment
Travels with this document in the same exchange.
849 · Response to Product Transfer Account Adjustment
Travels with this document in the same exchange.
997 · Functional Acknowledgment
The receipt that says an EDI transmission arrived and was parsed, with any syntax errors found.
See The 997How The 867 Moves On Files.com
A partner sends the 867 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 867 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 867 that was due never arrives. The full picture is on the EDI software page.
EDI 867 Questions
What teams ask about the 867 and how it moves on Files.com.
An EDI 867 is the X12 Product Transfer and Resale Report. A distributor sends it to a manufacturer to report resales to end customers and transfers between locations, which drives channel visibility, rebates, and commissions.
The 852 is a retailer reporting product activity by store, mainly sales and stock. The 867 is a distributor reporting resales to identified end customers and transfers, mainly for channel and rebate programs.
Yes. Files.com is a standards-compliant RFC 4130 AS2 endpoint, and a 867 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 867 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 867 from your system’s export and drops it in the partner’s outbox for delivery.
Exchange The 867 Without The Legacy Stack
Start the 7-day trial, turn AS2 on, and exchange certificates with your partner. The 867 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