Use My Organisation to identify the setup field or workflow that is blocking payroll or needs attention before statutory output generation.

What this means

The Setup Action Center groups actions into payroll blockers, statutory-output issues, and profile actions. The status can show Blocked for payroll, Ready for payroll, Statutory output attention required, or Verification unavailable. See Understand payroll and statutory readiness to interpret the separate checks.

Common causes

  • Payroll period or statutory pack is not configured for the intended date.
  • Required organisation identity/contact/profile data is missing.
  • A statutory identifier or applicability decision is missing or invalid; examples include ZIMRA BP, Tax office, or NSSA SSR.
  • Employees or employee statutory details are incomplete.
  • An APWCS classification or SDF applicability/evidence field is missing, or the active statutory pack cannot supply the applicable rate. SDF quarterly due dates come from the pack.

How to fix it

  1. Read the action

    Open My Organisation and read the status and each action’s reason/context.

  2. Open the named setup screen

    Resolve the named owner screen: use Edit Organisation Profile for identity/contact fields, Edit statutory profile for statutory fields, Payroll → Schedules for schedule setup, Employees for employee actions, or Statutory Packs to review pack coverage and workspace defaults.

  3. Save and recheck readiness

    Save the correction and return to My Organisation. Refresh the page/readiness data and confirm the action has changed or disappeared.

  4. Resolve remaining blockers

    Repeat until payroll blockers are resolved. Review any separate statutory-output attention before opening Documents > Statutory Outputs.

What to check

The selected organisation and intended period are correct, the action count has changed after each save, and the resulting status is understood. An employee row may show payroll Ready while statutory blockers remain; resolve the separately named statutory issue.

How to prevent it

Complete profile and statutory setup from authoritative records, check pack coverage against the statutory effective date, maintain departments as assignment aids, and rerun readiness after schedule, assignment, organisation, or employee changes. The close-by date is not a pack-selection date.

Still stuck

Record the action title, context, reason, named field path, selected organisation, and period. Do not bypass a blocker by changing an identifier, disabling an obligation, or treating a warning as approval. Escalate the product error with non-sensitive status text; keep employee and registration data local.