Workday errors in plain English.

Submit an Error
errors / peci / picof-payee-must-have-position-payroll-interface-pay-group

PICOF Extract Skips Payee: "Must Have a Position Assigned to at Least One Payroll Interface Pay Group"

✓ Verified PECI / PICOF 3 lookups
The error There is an issue with the Payee [ID] which has prevented it from being included in the payroll extract: Payee must have a Position assigned to at least one Payroll Interface Pay Group

What it means

PICOF only extracts a worker whose current position sits in a pay group the integration is scoped to run for. After a rehire, transfer, or a scheduled run tied to a specific pay group, the worker's active position can land outside that scope, so the connector reports the payee as ineligible instead of silently including them.

Troubleshooting

  1. Open the worker's current position and check which pay group it's assigned to, then compare against the pay group(s) this PICOF integration is configured to process.
  2. If the integration runs on a schedule, check the "Scheduled Future Process" task for what pay group the run was scheduled against. A rehire after the schedule was set can leave the worker attached to a pay group the scheduled run no longer covers.
  3. For a rehire or transfer specifically, confirm the new position's effective date and pay group took effect before the extract's as-of date, since a position change landing mid-cycle can leave the worker in a gap.
  4. Re-run the extract for a single test worker after correcting the pay group scope to confirm the payee is now included, rather than assuming a broader re-run will surface the same detail again.
⚡ Quick fix

Correct the worker's position pay group, or adjust the PICOF run's pay group scope/schedule to include the pay group the worker is actually in, then re-run.

✓ Permanent fix

When rehires or transfers happen close to a payroll cutoff, add a pre-run check that flags workers whose position pay group falls outside the scheduled PICOF run's scope, so these payees don't silently drop out of an extract.

Was this helpful?

Related errors