X12 transaction code
EDI 867 Product Transfer and Resale Report (X12 867)
EDI 867 is the X12 Product Transfer and Resale Report transaction set, used when transfers or downstream sales are reported. A reseller, typically a distributor, wholesaler, or retailer, sends the 867 upstream to the manufacturer or supplier whose product it moved, although the standard allows either party to originate it.
- Standard
- X12
- Code
- 867
- Partner references
- 10
At a glance
EDI 867 at a glance
What the 867 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 867 Product Transfer and Resale Report |
|---|---|
| Business record | Product transfer and resale record |
| Who sends it to whom | A reseller, typically a distributor, wholesaler, or retailer, sends the 867 upstream to the manufacturer or supplier whose product it moved, although the standard allows either party to originate it. |
| When it is sent | A distributor or retailer closes a reporting period and transmits an 867 detailing units sold, transferred between locations, or returned during that period. |
| Match on | Product, transfer or resale reference and reporting period |
| Partner references | 10 trading partners in this directory |
| Related documents | X12 844 Product Transfer Account Adjustment, X12 852 Product Activity Data |
Key segments in an EDI 867
The business segments that appear in at least half of the 10 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| BPT | Beginning Segment for Product Transfer and Resale | To indicate the beginning of the Product Transfer and Resale Report Transaction Set and transmit identifying data. | 10 of 10 |
| DTM | Date/Time Reference | To specify pertinent dates and times. | 10 of 10 |
| N1 | Name | To identify a party by type of organization, name, and code. | 10 of 10 |
| REF | Reference Identification | To specify identifying information. | 10 of 10 |
| PTD | Product Transfer and Resale Detail | To indicate the start of detail information relating to the transfer/resale of a product and provide identifying data. | 10 of 10 |
| N3 | Address Information | To specify the location of the named party. | 10 of 10 |
| N4 | Geographic Location | To specify the geographic place of the named party. | 10 of 10 |
| CTT | Transaction Totals | To transmit a hash total for a specific element in the transaction set. | 10 of 10 |
| QTY | Quantity | To specify quantity information. | 9 of 10 |
| LIN | Item Identification | To specify basic item identification data. | 9 of 10 |
Stacksync connects EDI documents such as the X12 867 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 867 mapping and validation
X12 867 Product Transfer and Resale Report is used when transfers or downstream sales are reported. Preserve product, transfer or resale reference and reporting period so the product transfer and resale record in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | product transfer and resale record product, transfer or resale reference and reporting period |
|
| Update the receiving system | Processing the product transfer and resale record ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the product transfer and resale record Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 844 Product Transfer Account Adjustment
product-transfer adjustment request: a distributor or reseller requests an account adjustment.
- X12 852 Product Activity Data
product activity report: product sales or inventory activity is reported.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when transfers or downstream sales are reported. Name the operational owner of the product transfer and resale record and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map product, transfer or resale reference and reporting period. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic product transfer and resale record data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful product transfer and resale record processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 867 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic product transfer and resale record data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out product transfer and resale record without processing it twice.
Document structure
X12 867 Product Transfer and Resale Report at the element level
The X12 867 reference contains 30 segment entries and 90 data elements; 50 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 30
- Data elements
- 90
- Mandatory elements
- 50
| Segment | Elements | Mandatory |
|---|---|---|
| BPT | 4 | 2 |
| DTM | 2 | 1 |
| REF | 2 | 1 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
| PTD | 3 | 1 |
| N2 | 1 | 1 |
| QTY | 2 | 1 |
| LIN | 11 | 2 |
- Transaction Set Purpose Code
- Date
- Date/Time Qualifier
- Reference Identification Qualifier
- Entity Identifier Code
- Address Information
- Product Transfer Type Code
- Name
Find your trading partner for X12 867
10 partners, 11 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 867 Product Transfer and Resale Report appears in this catalog
The largest groups of classified 867 catalog entries are in healthcare & pharma, building & hardware and electronics & technology.
By industry
- healthcare & pharma 4 channels
- building & hardware 3 channels
- electronics & technology 2 channels
- grocery & food 2 channels
By network
- Epicor Eclipse 2 channels
- iTradeNetwork 1 channel
FAQ
EDI 867 questions
What is an EDI 867?
EDI 867 is the X12 Product Transfer and Resale Report transaction set. Trading partners use it when transfers or downstream sales are reported. It carries the data for the product transfer and resale record, and your system matches it on product, transfer or resale reference and reporting period.
Who sends an EDI 867 and who receives it?
A reseller, typically a distributor, wholesaler, or retailer, sends the 867 upstream to the manufacturer or supplier whose product it moved, although the standard allows either party to originate it. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 867 sent?
A distributor or retailer closes a reporting period and transmits an 867 detailing units sold, transferred between locations, or returned during that period. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 867?
Across 10 partner document references listed here, the business segments that appear most often include BPT (Beginning Segment for Product Transfer and Resale), DTM (Date/Time Reference), N1 (Name), REF (Reference Identification), PTD (Product Transfer and Resale Detail), N3 (Address Information). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 867 and EDI 844?
The 867 carries the product transfer and resale record and is used when transfers or downstream sales are reported. The 844 carries the product-transfer adjustment request and is used when a distributor or reseller requests an account adjustment.
What should I map for X12 867?
Start with product, transfer or resale reference and reporting period and the target product transfer and resale record. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 867 error handling?
Keep a transfer between locations separate from a sale to an end customer. Deduplicate corrected resale reports before calculating rebates or channel demand. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 867?
The directory on this page links 10 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
