Noyo supports round-trip confirmation—our unique ability to sync back data from carriers and confirm that changes submitted via the Noyo API have been successfully completed by a carrier. When there are errors on the carrier side that affect these confirmation checks, it can be difficult for ben-admins to understand what went wrong and how to resolve it.

An Issue represents a specific problem Noyo has detected in the flow of benefits data that needs attention—paired with context and resolution guidance to help teams take action.

With this release, Noyo now creates Issues when we’re unable to successfully confirm an update with a carrier, starting with Guardian. This makes confirmation blockers visible earlier and ties them to clear, actionable guidance, without requiring manual investigation or engineering support.

What’s new

This capability launches with Guardian, based on the most common root causes of confirmation errors we see today. These Issues are created automatically and are visible to all ben-admins with a Guardian connection. We’ll quickly expand to additional carriers as we evaluate patterns in their system.

We now surface Issues with confirmation due to pending Evidence of Insurability (EOI), retroactive changes that fall outside the carrier's policy, terminations that don't align with the carrier's termination policy for that plan, and overages of dependents.

Supported

• Evidence of insurability (EOI) pending

• Invalid carrier configuration (benefit class)

• Retroactive changes and termination rules (based on carrier policies)

• Overage dependents

How it works

• When a carrier confirmation can’t be processed, Noyo creates an Issue tied to the underlying error—we identify the root cause and surface it, either via API and in our app

• If confirmation later succeeds without that error, the Issue is automatically resolved

• Repeated instances caused by the same issue are grouped together, avoiding duplicate Issues for the same problem

The ben-admin experience

Ben-admins with Guardian connections will now see confirmation-related Issues alongside other carrier Issues from API errors and EDI error reports. The overall Issue reconciliation workflow remains the same, but summaries and resolution guidance are tailored to these confirmation errors—making it easier to proactively address problems before they impact members.

Want to learn more? Go deeper on how Noyo is modernizing data reconciliation or reach out for a demo.