Core Connector Empower Retirement Savings Inbound: Worker Not Eligible for 457B
The error SOAP-ENV:Client.validationError / Validation error occurred. <Worker> is not eligible for 457B - Empower / Element 6$29774 Restricted by 103$10324 / Xpath: /wd:Enroll_in_Retirement_Savings_Plans_Request[1]/wd:Enroll_in_Retirement_Savings_Plans_Data[1]/wd:Retirement_Savings_Election
What does "Core Connector Empower Retirement Savings Inbound: Worker Not Eligible for 457B" mean in Workday Core Connector?
The Empower Retirement Savings (Inbound) benefits connector is trying to enroll a worker in a 457B deferral plan, but Workday's benefit eligibility rules say that worker is not eligible for a 457B plan. The connector rejects the whole record with a validation fault instead of skipping just that election.
Quick fix
Remove or suppress the ineligible worker's record from the inbound file for this run so the rest of the enrollment batch processes, then investigate that worker separately.
Permanent fix
Align the vendor's eligibility file scope with Workday's actual 457B eligibility rule (for example via a vendor-side eligibility feed or filter) so the connector only receives records for workers who are truly eligible, preventing recurring rejections.
Troubleshooting
- Identify the specific worker or workers named in the failing record from the inbound file.
- In Workday, check that worker's benefit eligibility (via Benefits Administration or the eligibility rule referenced by the 457B plan) to confirm whether they are genuinely ineligible (wrong worker type, job classification, or benefit group) or whether the eligibility rule or plan enrollment configuration is out of date.
- Check whether the vendor file (Empower) contains records for workers who were recently terminated, transferred, or reclassified, since eligibility can lag a status change.
- If eligibility looks correct on the Workday side, work with the vendor to confirm they are not sending deferral records for out-of-scope populations.
Was this helpful?