X12 transaction code
X12 834 Benefit Enrollment And Maintenance
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 834
- Trading partners
- 1
Specification summary
X12 834 Benefit Enrollment And Maintenance at the element level
The X12 834 specification defines 37 segments carrying 166 data elements, 64 of which are mandatory.
- 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
Trading partners that support X12 834
1 partner, 1 channel. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 834 Benefit Enrollment And Maintenance
834 is used most heavily in healthcare & pharma.
The 834 carries health plan enrollment and maintenance data: adding members, changing coverage or dependents, and terminating enrollment. It is the HIPAA-mandated ASC X12N standard for exchanging member eligibility between plan sponsors and payers, so carriers require it to keep member records and eligibility current. Each payer's companion guide adds carrier-specific requirements on top of the base standard. Sent by plan sponsors (employers, unions, government agencies) or their benefits administrators to insurance carriers, HMOs, or third-party administrators. An enrollment event at the plan sponsor: a new hire, an open enrollment election, a qualifying life event such as marriage or childbirth, COBRA initiation, or a termination.
By industry
- healthcare & pharma 1 channel
FAQ
X12 834 questions
What is X12 834 Benefit Enrollment And Maintenance?
X12 834 (Benefit Enrollment And Maintenance) is an EDI transaction set defined by ANSI ASC X12 for exchanging benefit enrollment and maintenance between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 1 Stacksync trading partner supports this code across 1 channel.
Which trading partners use X12 834?
1 Stacksync partner accepts X12 834: Healthcare Leader. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 834 with my ERP?
Stacksync handles the full X12 834 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
