EIB Change Benefits Load Fails With Too Few Dependents Selected For Coverage Level
What it means
Loading a Change Benefits EIB onto a shared coverage level, such as employee plus spouse or employee plus child, fails because Workday expects a matching dependent record for that coverage tier, and the load file only carried the base coverage election without any dependent data behind it.
Troubleshooting
- Check whether the target coverage level has a minimum dependent count configured in Benefits Setup for that plan; employee-only tiers don't need dependent rows, but combination tiers do.
- Confirm the EIB actually includes a dependent row, or a reference to an existing dependent, for every employee being loaded onto a multi-person coverage level, not just the coverage election itself.
- If dependent data genuinely isn't available yet, check whether the plan's rate structure allows the coverage level to be selected without full dependent detail, or whether dependents must be loaded in a separate prior step.
Add the required dependent rows, or dependent ID references, to the load file for every employee moving onto a coverage level above employee-only, matching that plan's minimum dependent requirement.
Sequence dependent-data loads ahead of coverage-level EIBs in the integration plan so dependent records always exist before a multi-person coverage election is attempted, and document the minimum-dependent rule per coverage level in the EIB build spec.