One Directional
When you integrate your HRIS with Yuzu, eligibility changes flow one direction: from your HRIS into Yuzu. The Yuzu portal shows you what's enrolled, but it isn't where you edit eligibility anymore.
Your HRIS already owns this data
Hires, terms, life events, dependents…they're entered in your HRIS first. Payroll, ACA reporting, and COBRA all read from there. Making Yuzu read from the same place keeps every system in agreement.
Two editable systems would drift apart
If you could edit eligibility in both places, they'd disagree the moment someone updated one and not the other. The next HRIS file would either overwrite your portal change or quietly conflict with it. There's no clean way to resolve that, so we don't create the problem.
What does it mean for you as an employer?
Eligibility maintenance is an HR or broker responsibility, handled at the source. When Yuzu surfaces an ingestion error, the fix happens upstream in your HRIS. The portal is where you go to see enrollment, not change it.
When something goes wrong
Ingestion failures usually come from demographic mismatches, missing fields, or overlapping coverage. We hold the whole file rather than ingest part of it: clean data in exchange for fixing errors before the next file lands.
For the walkthrough, see HRIS Enrollment Troubleshooting guide.