X12 transaction code
EDI 834 Benefit Enrollment and Maintenance (X12 834)
EDI 834 is the X12 Benefit Enrollment and Maintenance transaction set, used when enrollment or membership maintenance is submitted. Plan sponsors (employers, unions, government agencies) or their benefits administrators send the 834 to insurance carriers, HMOs, or third-party administrators.
- Standard
- X12
- Code
- 834
- Partner references
- 1
At a glance
EDI 834 at a glance
What the 834 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 834 Benefit Enrollment and Maintenance |
|---|---|
| Business record | Benefit enrollment record |
| Who sends it to whom | Plan sponsors (employers, unions, government agencies) or their benefits administrators send the 834 to insurance carriers, HMOs, or third-party administrators. |
| When it is sent | The plan sponsor records an enrollment event: a new hire, an open enrollment election, a qualifying life event such as marriage or childbirth, COBRA initiation, or a termination. |
| Match on | Member reference, plan and coverage period |
| Partner references | 1 trading partner in this directory |
Key segments in an EDI 834
The business segments in the one partner document reference listed below. 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 |
|---|---|---|---|
| BGN | Beginning Segment | To indicate the beginning of a transaction set. | 1 of 1 |
| REF | Reference Information | To specify identifying information. | 1 of 1 |
| DTP | Date or Time or Period | To specify any or all of a date, a time, or a time period. | 1 of 1 |
| N1 | Party Identification | To identify a party by type of organization, name, and code. | 1 of 1 |
| N3 | Party Location | To specify the location of the named party. | 1 of 1 |
| N4 | Geographic Location | To specify the geographic place of the named party. | 1 of 1 |
| INS | Insured Benefit | To provide benefit information on insured entities. | 1 of 1 |
| NM1 | Individual or Organizational Name | To supply the full name of an individual or organizational entity. | 1 of 1 |
| PER | Administrative Communications Contact | To identify a person or office to whom administrative communications should be directed. | 1 of 1 |
| DMG | Demographic Information | To supply demographic information. | 1 of 1 |
Stacksync connects EDI documents such as the X12 834 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 834 mapping and validation
X12 834 Benefit Enrollment and Maintenance is used when enrollment or membership maintenance is submitted. Preserve member reference, plan and coverage period so the benefit enrollment 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 | benefit enrollment record member reference, plan and coverage period |
|
| Update the receiving system | Processing the benefit enrollment record ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the benefit enrollment record Original document reference and matching response |
|
Implementation steps
-
Choose the starting event and owner
Decide which application acts when enrollment or membership maintenance is submitted. Name the operational owner of the benefit enrollment record and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map member reference, plan and coverage 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 benefit enrollment 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 benefit enrollment record processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 834 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic benefit enrollment 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 benefit enrollment record without processing it twice.
Document structure
X12 834 Benefit Enrollment and Maintenance at the element level
The X12 834 reference contains 37 segment entries and 166 data elements; 64 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 37
- Data elements
- 166
- Mandatory elements
- 64
| Segment | Elements | Mandatory |
|---|---|---|
| BGN | 9 | 3 |
| REF | 3 | 1 |
| DTP | 3 | 3 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
| INS | 16 | 2 |
| NM1 | 11 | 2 |
| PER | 8 | 1 |
| ICM | 6 | 2 |
- Transaction Set Purpose Code
- Reference Identification
- Date
- Reference Identification Qualifier
- Date/Time Qualifier
- Date Time Period Format Qualifier
- Date Time Period
- Entity Identifier Code
Find your trading partner for X12 834
1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 834 Benefit Enrollment and Maintenance appears in this catalog
The largest groups of classified 834 catalog entries are in healthcare & pharma.
By industry
- healthcare & pharma 1 channel
FAQ
EDI 834 questions
What is an EDI 834?
EDI 834 is the X12 Benefit Enrollment and Maintenance transaction set. Trading partners use it when enrollment or membership maintenance is submitted. It carries the data for the benefit enrollment record, and your system matches it on member reference, plan and coverage period.
Who sends an EDI 834 and who receives it?
Plan sponsors (employers, unions, government agencies) or their benefits administrators send the 834 to insurance carriers, HMOs, or third-party administrators. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 834 sent?
The plan sponsor records an enrollment event: a new hire, an open enrollment election, a qualifying life event such as marriage or childbirth, COBRA initiation, or a termination. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 834?
The one partner document reference listed here includes BGN (Beginning Segment), REF (Reference Information), DTP (Date or Time or Period), N1 (Party Identification), N3 (Party Location), N4 (Geographic Location). Each partner guide sets which segments and elements your account must send.
What should I map for X12 834?
Start with member reference, plan and coverage period and the target benefit enrollment 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 834 error handling?
Test retroactive termination against an already active coverage period. Keep dependent relationships linked to the correct subscriber during an update. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 834?
The directory on this page links 1 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
How does 834 relate to other EDI messages?
Keep 834 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the benefit enrollment record workflow; confirm any required companion messages with your partner.
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.
