X12 transaction code
X12 867 Product Transfer And Resale Report
X12 867 Product Transfer And Resale Report: explore its business purpose, mapping identifiers, validation tests and 10 partner references across 11 listed channels.
- Standard
- X12
- Code
- 867
- Partner references
- 10
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
X12 867 questions
What is X12 867 Product Transfer And Resale Report used for?
867 is used when transfers or downstream sales are reported. It carries information for the product transfer and resale record. Match it to your business system using product, transfer or resale reference and reporting period.
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.
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.
How does 867 relate to other EDI messages?
X12 844 Product Transfer Account Adjustment; X12 852 Product Activity Data are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 867 and 844?
867 is used when transfers or downstream sales are reported. 844 is used when a distributor or reseller requests an account adjustment. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
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.
