Noyo vs Ideon

How to choose the best enrollment data
solution for your business

Overview

Knowing who’s enrolled in what coverage at what time is the source of truth from which everything else can flow: payroll deductions, billing, commissions, claims, and more. That’s why it’s vitally important for enrollment data to be secure, reliable, and frictionless. We’ll explore the key differences of how Noyo and Ideon approach the management of enrollment and eligibility data in this guide.

Noyo was first-to-market with a one-to-many API solution that seamlessly connects benefits software and insurance carriers. Noyo delivers a single, safe platform to structure, clean, and transmit member data at each step of benefits administration. Where other middleware focus on adapting legacy technology, Noyo prioritizes deep integrations across a broad network of carriers so benefits data can be used and understood in new ways.

Ideon, formerly Vericred, recently rebranded and shifted their business to expand digital enrollment solutions. Ideon offers middleware focused on improving connectivity with a mix of file-based systems, APIs, and other traditional methods of data exchange. Describing themselves as “pipes” or “in-between technology”, Ideon prioritizes adapting legacy systems to connect with newer technologies like APIs. 

Product comparison: What’s under the hood

Noyo
Enrollment

Ideon
Enrollment

Direct file-based
connection

How are changes transmitted to carriers?

Majority API, but other standard formats supported in specific cases (EDI, .csv, JSON, LDEx).

Select carriers with API, other standard formats supported (multi-tenant EDI, .csv, JSON, LDEx).

EDI or carrier-specific file format.

How are new groups connected?

API call triggers automatic sync of account and member data from the carrier’s system. Groups are usually connected in 3 days or less.

Group is added to existing multi-tenant file or a new file is built and tested. Where supported, API call results in file with group data sent to carrier.

Benefits software and carrier build and test files for 10-12 weeks.

How does account structure mapping work?

Noyo syncs account structure from carrier and populates the Noyo mapping tool for a simple UI-based experience. Noyo also accepts mapping output via API.

Ideon reaches out to carrier for mapping rules. Benefits software must create mapping and load into Ideon with the right plan and structure IDs.

Benefits software must use spreadsheet libraries to create mapping and pass values in files.

How are ongoing member changes handled?

Benefits software makes API call containing full payload of demographic and enrollment data for each family whenever there is a change. Noyo validates and sends changes to carrier(s).

Benefits software sends changes on weekly files, which are converted to carrier’s format. Where supported, qualifying life event requests are sent via API with full payloads of member demographic and enrollment data.

Flat files are exchanged weekly and contain the entire state of group and employee enrollments.

How are member changes confirmed?

Noyo validates each change against carrier rules and business logic and tracks receipt. Noyo syncs directly with carrier system to confirm changes twice: when received and on effective date.

Carriers confirm receipt of change file. API-based changes are validated against carrier rules and business logic. Carriers periodically generate a report with discrepancies.

Carriers confirm receipt of change file and periodically generate a report with discrepancies.

How is reconciliation handled?

Noyo automatically syncs with carrier system to identify issues. Issues are communicated to benefits software via tooling or reporting.

Reconciliation report is requested from the carrier. Issues are passed to benefits software to fix. Where supported, Ideon operations interprets reconciliation report and makes issues available to retrieve via API call.

Reconciliation report can be requested from the carrier for manual comparison and troubleshooting.

How does open enrollment work?

Benefits software submits new plan info via API and Noyo checks the carrier’s system to confirm when the new plans are installed correctly. All OE elections are then sent via API.

Ideon emails carriers weeks in advance to get new plans installed, and then emails the platform when finished. Benefits software sends OE elections to Ideon via files or API. Ideon coordinates with carrier to ensure completion.

Benefits software emails the carrier weeks in advance to get new plans installed. After plans are complete, timing for sending OE elections must be worked out over phone or email.

Can new and past year elections be sent at the same time?

Yes. Both are accepted over API and Noyo works with carriers to ensure completion.

Yes. Ideon works with carriers to ensure completion.

Sometimes. A special OE file or manual communication is needed.

Ideon

Connections and data

 

Eliminate flat files and other outdated methods

Programmatically clean, validate, and standardize data

Managing members

 

Install new groups with the carrier over API

Manage ongoing member changes over API

Simplify account structure mapping

Automate the tough parts of open enrollment

Confirming changes

 

Access fresh data syncs from the carrier system

Confirm member changes upon sending and on the effective date

Identify errors without waiting on a carrier’s report

Want to learn more?

Reach out to our solutions team for a demo.

Noyo by the numbers

3 days or less

Get groups connected and start enrolling members.

4 days or less

Process and confirm member changes at the carrier.

6x faster

To connect carriers with Noyo Sync than building direct.

What sets Noyo apart

Seamless carrier connections

Unlike other solutions, Noyo has proprietary integrations with carriers that allow direct read/write access to the system of record in near real-time.

This lets us deliver:

Technology-first approach

What sets Noyo apart is how our technology keeps data in sync with connected partners, prioritizing automation over a human-led, service-based approach. 

This lets us deliver:

A proven partnership

From the beginning, Noyo has championed the power of frictionless data in our space, bringing together an innovative network of partners to build this reality together.

This lets us deliver:

What customers are saying

Getting started with Noyo

Noyo is a long standing member of the LIMRA LDEX committee, helping advise the industry toward a more open and connected benefits ecosystem. We work with companies at all stages of digital transformation to help realize their strategies and stay agile in a changing landscape. 

We’d love to talk to you about:

Migrating from Ideon or a different direct solution

trend-up

Currently exchanging files and looking to expand API-powered data exchange

New to benefits data and evaluating options

The Noyo API product guide

Learn more

The Noyo API product guide

See step-by-step how Noyo transforms each step of benefits administration, from group setup, to enrollment, to renewal.

See how Noyo works
How Sana Benefits is scaling carrier connectivity with Noyo.

Learn more

How Sana Benefits is scaling carrier connectivity with Noyo

How Sana Benefits eliminated file-based work and reduced opex by 95%.

See the impact
How Beam Benefits unlocked new growth with a leading enrollment experience

Learn more

How Beam Benefits unlocked new growth with a leading enrollment experience

On top of the Noyo platform, Beam unseated a large competitor while reducing opex 85%.

See the impact
Previous
Next