Payroll Outbound Fails: No Value Output for Required Field When the Primary Address Lacks the Expected Usage Type
The error No value output for required field PAYROLL Worker Home Address 1
What does "No value output for required field PAYROLL Worker Home" mean in Workday PECI?
A required field in the outbound payroll file produced nothing for one worker. The worker usually does hold the data, but the connector selects it by usage type and primary flag, and the record it picks is not the one carrying the usage the field expects.
Quick fix
Add the missing usage type to the worker's primary address so the primary record is the one the connector selects, then relaunch for that worker.
Permanent fix
Build a validation report that flags workers whose primary address is missing the usage type the payroll interface filters on, and run it before each payroll extract instead of discovering the gap in the integration log.
Troubleshooting
- Identify the specific worker or workers affected. This message names the field, but the failure is almost always per-record rather than a global mapping fault, which is why most of the population extracts cleanly.
- Read the integration output log and check which address the connector actually returned, and whether it came back flagged as the primary one.
- Compare the affected worker's addresses against a worker who extracts cleanly, looking at both the usage types assigned and which address holds the primary flag for each usage.
- Where a worker has a primary home address and an additional home address, check whether the additional record carries the usage the connector filters on while the primary record does not. That ordering is what makes the connector return nothing.
- Confirm the field is genuinely required in the target file layout before changing worker data, since relaxing the field may be the correct answer for some vendor layouts.
Was this helpful?