Employee Navigator 834 EDI: license tier, fees and setup
Summarise the blog with AI
Last verified: 2026-10-30
Key takeaways
- Employee Navigator (EN) does not include 834 feeds on Enhanced, so the minimum tier is Enhanced Plus.
- EN's pricing page lists $0.45 PEPM (per enrolled employee per month) on Enhanced Plus and Elite, and $0 PEPM on Platinum, with the row marked "Additional fees apply".
- On EN's stated basis, the highest eligible feed per group, a group with 100 enrolled employees on its largest feed costs $45 a month and $540 a year on Enhanced Plus or Elite.
- EN charges a small one-time fee to set up a carrier that is not on its preconfigured list.
- EN names Guardian, Unum, Principal and Mutual of Omaha as Data Exchange carriers, a path EN says implements in 1 to 2 weeks at no additional cost to brokers.
- EN's 834 engine sends no HSA enrollments or change-only files, and EN publishes no 834 turnaround figure.
Employee Navigator's 834 fee looks like it stacks for every carrier feed a group runs. It doesn't. One charge per group, set by its largest feed.
The tier decides whether you can turn feeds on at all. The group's largest feed decides what you pay each month, and the carrier decides whether you pay anything up front. According to EN's pricing page, the "834 EDI Feeds" row reads "-" on Enhanced, $0.45 PEPM on Enhanced Plus and Elite, and Free on Platinum. EN's Marketplace EDI page adds a small one-time fee to set up a carrier that is not yet on its preconfigured list.
How the $0.45 is calculated
EN's integrations guide states the fee as $0.45 per enrolled employee per month, "based on the highest eligible feed per group." Read plainly, that is one charge per group, keyed to the feed with the most enrolled employees. A group whose largest feed has 100 enrolled employees is billed on those 100, even if it also runs dental and vision feeds.
Here is that group on each tier:
EN's pricing page marks the 834 row "Additional fees apply", so confirm the full invoice, including any carrier setup fee, before you quote a client. Get three points confirmed by EN in writing before you budget: the license price, which EN lists as "Contact Sales" on all four tiers; whether Platinum's $0 PEPM extends to the carrier setup fee; and how "highest eligible feed" treats a group spread across several carriers.
Budget from the tier row above. Older EN pages that predate the tiers show different figures, and the tier row is the current one.
Which path fits each carrier: 834 or Data Exchange?
EN sends full 834 files only for medical, dental, vision and Rx plans, with exceptions for Guardian and Anthem Life. Data Exchange, EN's other carrier path, supports a broader range of products and carriers. Outside X12, LIMRA's LDEx standards have covered enrollment for all employee benefit plans since LIMRA's 2022 enhancement, which gives ancillary carriers a standard of their own outside the 834.
EN's 834 engine also does not send HSA enrollments or change-only files, two things carriers commonly ask for. If a carrier needs either, settle it before you choose the 834 path.
Use the table as a first filter. A medical, dental, vision or Rx line is a candidate for the 834 path, and an ancillary or worksite line is a reason to check EN's Data Exchange list first. A candidate becomes a feed once the carrier confirms it will take that group on EDI. Group size is a separate question: EN's 100+ guidance describes when a feed fits, and it does not decide whether you may turn one on. On price the comparison is short: EN lists Data Exchange at no additional cost to brokers.
For every other route out of EN, including payroll integrations and reports, see our Employee Navigator data export guide.
Does your group qualify, and can a carrier refuse an 834?
The 100+ figure is a recommendation, not a gate. EN's integrations guide recommends the 834 feed for groups with 100+ members or significant turnover, which is EN's view of when the feed pays off. Separately, EN's Marketplace EDI page states that some carriers require at least 100 employees to use their EDI services. That minimum belongs to the carrier, so ask each one.
EN's own page goes further and says such minimums aren't permitted under HIPAA. The regulation's text doesn't mention group size, so treat EN's view as EN's.
The federal rule speaks to health plans. Under 45 CFR §162.925(a), if an entity asks a health plan to conduct a transaction as a standard transaction, the plan must do so. It may not delay or reject the transaction because it is a standard transaction, and it may not reject one because it contains data elements the plan does not need. Whether that bears on a particular carrier's group-size minimum is a question for counsel.
How 834 setup works, step by step
EN describes 834 setup as self-service. Run it in this order:
- Confirm the tier. Your agency needs Enhanced Plus, Elite or Platinum before 834 feeds are available.
- Check the carrier list. See whether the carrier is already on EN's preconfigured list, since the small one-time setup fee applies only if it is not.
- Get the companion guide. Carriers publish an 834 companion guide that describes their implementation requirements.
- Reconcile enrollment data. Correct the group's enrollment records in EN before any file is built.
- Configure the group's file. You set up each company's file individually in EN.
- Test with the carrier. Every 834 file is tested before transmission, so keep testing until the carrier clears it for production.
- Schedule and monitor. Set the transmission schedule and watch it, because users manage and monitor transmissions themselves.
Steps 5 through 7 are yours, which is why 834 consumes staff time after the fee is paid.
On timing, EN says 834 setup takes longer than its other integrations because each file is set up and tested individually, and it publishes no turnaround figure. Put the carrier's test cycle on the calendar before you promise a client a go-live date.
When a platform your clients use needs the same data
If a benefits platform your clients use needs EN enrollment data inside its own product, the 834 feed is the wrong route: it goes to a carrier. Bindbee reads Employee Navigator through an SFTP feed the employer or broker sets up, and normalizes it into four benefits models: the plan catalog, each enrollment, dependent coverage, and per-person insured amounts. The same feed also carries the employee census, employment, compensation and dependents.
Bindbee publishes a Model Availability Matrix that marks each model Available, Beta or not available per integration, and Bindbee's Employee Navigator integration page covers that system directly. Bindbee is SOC 2 Type II, GDPR and ISO 27001 compliant, and HIPAA compliant with BAAs signed as standard, which matters when enrollment data passes through another vendor. More than 100 companies build on Bindbee, including benefits platforms such as Newfront and Healthee.
If all you need is EN's own feed for a group, nothing here changes the fee math above. If a platform you or your clients use needs benefits data from Employee Navigator and other systems, book a demo.
FAQ
How much does an Employee Navigator license cost?
EN lists all four tiers as "Contact Sales" and publishes no subscription price. Using the 834 engine incurs a PEPM fee on top of the license, per EN's pricing page and its support page on additional fees.
What is 834 EDI?
834 EDI is the HIPAA-adopted standard for transmitting enrollment and disenrollment information from a coverage sponsor to a health plan, ASC X12N 834 version 005010X220 (August 2006). Under 45 CFR §162.1502, that transaction establishes or terminates coverage, and HHS adopted this standard for it. For file layout and segment detail, see Bindbee's 834 guide.
Who pays the Employee Navigator 834 fee?
EN charges the 834 fee to agencies, per its integrations guide. EN also states that its payroll integrations cost brokers nothing extra, though the payroll provider may charge setup fees.
Does Employee Navigator send change-only 834 files?
No. EN's Marketplace EDI page says its EDI engine does not transmit change-only files or HSA enrollments, so each transmission carries the full file.
