We’ve expanded our Issue tracking experience to support automatic Issue creation from Guardian API transmissions. This update improves visibility into common validation problems that can prevent enrollment and eligibility changes from being successfully processed.

With this release, Issues from API errors and EDI error reports can now be automatically detected and triaged within a single workflow—with full context, timeline, and resolution guidance for every issue.

Need a refresher on Noyo Issues? Here’s a quick tour of the experience.

What’s new

Issues are now created automatically when Guardian rejects an API transmission for the following conditions:

• State and ZIP code mismatch

• Employee date of birth occurring after hire date

• Coverage effective date occurring before hire date

These scenarios represent frequent causes of failed transmissions and often require data corrections before changes can be processed. We’ll quickly expand this capability to additional scenarios and carriers as we evaluate each carrier's unique patterns.

How it works

Carrier API transmission Issues are created when Noyo is unable to successfully deliver a change to Guardian due to a validation error.

An Issue remains open until a successful transmission is sent that does not produce the same error. If an Issue is already open and a new transmission results in an error for the same reason, our system recognizes this as the same underlying problem rather than creating a new Issue—no duplicates.

This behavior mirrors how Issues generated from EDI error reports are handled, ensuring a consistent reconciliation experience no matter how data is transmitted to carriers behind the scenes.

Impact for customers

Failed carrier transmissions can delay enrollment and eligibility updates, especially when the underlying issue isn’t immediately visible or requires engineers to review.

With automatic Issue creation for Guardian API errors:

• Ben-admin ops teams gain immediate visibility into data conditions blocking carrier processing

• Repeated transmission failures are tracked in a single Issue, reducing noise and confusion—it's easy to understand the root cause

• Teams can resolve issues sooner, minimizing downstream reconciliation work and manual follow-up

• The process of understanding and resolving an Issue is the same for EDI and API connected carriers

This gives ben-admin teams greater visibility and control when problems occur, making it easier to be proactive and prevent escalations. We’ll be expanding API Issue generation to more carriers, stay tuned.

Learn more about Noyo's Issues experience here or reach out for a demo.