To start and identify an interchange of zero or more functional groups and interchange-related control segments
Border States X12 867 Product Transfer and Resale Report
Plan X12 867 Product Transfer and Resale Report for Border States Electric Supply. Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 19
- Loops
- 4
- X12 867
- Partner references ↗
Implementation guide
Border States Electric Supply: 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.
This document is listed for Border States Electric Supply. Confirm the version, required fields and responses that apply to your account.
| 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 |
|
The document reference includes 19 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
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.
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 Border States 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.
Transaction context
Where 867 Product Transfer and Resale Report fits on Border States Electric Supply
- Border States channels
- 1 of 1
1 of Border States's 1 channel list 867
- Trading partners
- 10
partner references list 867
- Channels
- 11
channel entries list 867
Frequently listed alongside 867
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 |
Key identifiers in 867
- Transaction Set Purpose Code
- Date
- Date/Time Qualifier
- Reference Identification Qualifier
- Entity Identifier Code
- Address Information
- Product Transfer Type Code
- Name
Segment reference — 19 segments 4 loops · X12 867 Product Transfer and Resale Report
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of the Product Transfer and Resale Report Transaction Set and transmit identifying data
To specify pertinent dates and times
N1 Loop Repeat: 5
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
PTD Loop Repeat: 5
To indicate the start of detail information relating to the transfer/resale of a product and provide identifying data
CTT Loop Repeat: 1
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To identify a person or office to whom administrative communications should be directed
QTY Loop
To specify quantity information
To specify basic item identification data
To specify item unit data
To indicate the total monetary amount
To describe a product or process in coded or free-form format
To specify identifying information
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Related references
Other transactions in Border States Electric Supply
Other EDI documents listed on this channel.
Product Transfer Account Adjustment X12 844 Response To Product Transfer Account Adjustment X12 849 Purchase Order X12 850 Purchase Order Acknowledgment X12 855 Ship Notice Manifest X12 856 Invoice X12 810
No references match your search.
Showing 6 of 6 references
Browse the full directoryBorder States Electric Supply EDI 867 questions
Common questions about 867 Product Transfer and Resale Report on the Border States Electric Supply channel.
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.
Is 867 required for Border States Electric Supply?
867 is listed for Border States Electric Supply. Confirm the required version and direction for your business unit and account with the partner.
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 is a related document also listed on Border States Electric Supply. 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 Border States 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.
