X12 transaction code
X12 864 Text Message
X12 864 Text Message: explore its business purpose, mapping identifiers, validation tests and 15 partner references across 25 listed channels.
- Standard
- X12
- Code
- 864
- Partner references
- 15
Implementation guide
X12 864 mapping and validation
X12 864 Text Message is used when a trading partner sends information intended for a recipient. Preserve message reference, subject and related business document so the business message 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 | business message message reference, subject and related business document |
|
| Update the receiving system | Processing the business message ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the business message 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 850 Purchase Order
purchase order or sales order: a buyer places an order.
- X12 824 Application Advice
application validation result: a receiving application reports processing results.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a trading partner sends information intended for a recipient. Name the operational owner of the business message and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map message reference, subject and related business document. 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 business message 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 business message processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 864 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic business message 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 business message without processing it twice.
Document structure
X12 864 Text Message at the element level
The X12 864 reference contains 16 segment entries and 52 data elements; 35 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 16
- Data elements
- 52
- Mandatory elements
- 35
| Segment | Elements | Mandatory |
|---|---|---|
| BMG | 3 | 1 |
| N1 | 4 | 1 |
| MIT | 1 | 1 |
| N3 | 2 | 1 |
| REF | 2 | 1 |
| PER | 4 | 1 |
| MSG | 1 | 1 |
- Transaction Set Purpose Code
- Entity Identifier Code
- Reference Identification
- Address Information
- Reference Identification Qualifier
- Contact Function Code
- Free-Form Message Text
Find your trading partner for X12 864
15 partners, 25 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 864 Text Message appears in this catalog
The largest groups of classified 864 catalog entries are in building & hardware, grocery & food and retail.
By industry
- building & hardware 7 channels
- grocery & food 6 channels
- retail 6 channels
- apparel & footwear 6 channels
By network
- ecUtopia 2 channels
- InterTrade 1 channel
FAQ
X12 864 questions
What is X12 864 Text Message used for?
864 is used when a trading partner sends information intended for a recipient. It carries information for the business message. Match it to your business system using message reference, subject and related business document.
Which partners list X12 864?
The directory on this page links 15 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 864?
Start with message reference, subject and related business document and the target business message. 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 864 error handling?
Preserve line breaks and readable content in the receiving work queue. Test an urgent message linked to an order and assign a human owner instead of silently filing it. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 864 relate to other EDI messages?
X12 850 Purchase Order; X12 824 Application Advice 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 864 and 850?
864 is used when a trading partner sends information intended for a recipient. 850 is used when a buyer places an order. 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.
