Use the reason shown in Payroll or the preparation wizard to identify why a run cannot be created, continued or previewed for the selected organisation and period. A failed readiness check is not a calculation result.

What this means

An action may be disabled when no organisation, schedule occurrence, eligible employee set or compatible pack is available, or when backend readiness fails. For a regular run, the statutory effective date comes from the service-period end. Passing the close-by date alone does not make the occurrence unavailable.

Common causes

  • No active organisation is selected. The app shows “No active organisation selected”.
  • The selected schedule has no valid occurrence or employee assignment for the service dates.
  • No compatible signed workspace-default pack covers the service-period end, or the pack does not support calculation for the selected frequency.
  • Employee, compensation, organisation, transaction, exchange-rate, or other calculation blockers are returned by readiness checks.
  • The local runtime or backend readiness response cannot be loaded.

How to fix it

  1. Confirm the organisation

    Return to Payroll and confirm the organisation badge is the intended organisation.

  2. Check the schedule and employees

    Open Payroll → Schedules and confirm the named schedule, occurrence service dates, close-by date and effective-dated assignments. Check candidate eligibility for the selected occurrence; see Choose employees for a pay run.

  3. Check pack coverage

    Open Workspace Settings → Statutory Packs and confirm the default covers the service-period end. If no pack covers it, follow App update or statutory pack update unavailable. Use Compliance for Rules or detached Tax Preview.

  4. Follow readiness actions

    Read the readiness action in My Organisation or the payroll wizard. Follow its named destination, such as Employees, My Organisation, Transactions or Time Off Policies. See Understand payroll and statutory readiness.

  5. Refresh the editable draft

    Return to the wizard, select “Refresh employees”, and select “Save progress” before trying “Continue”.

What to check before continuing

The draft should show the selected occurrence, eligible employee set and calculation readiness. Missing bank routing for an optional export is output-specific. Do not rely on a draft gross estimate until backend preview succeeds. Zimbabwe v3 RC2 can generate semi-monthly occurrences, but its PAYE tables do not certify calculation and finalisation for that frequency.

How to prevent it

Keep the active pack, statutory information, effective compensation, assignments, and transaction versions current for the selected period. Run readiness for each occurrence rather than assuming a previous period’s result carries forward.

Still stuck

Record the readiness code/message, organisation, schedule occurrence, close-by date, statutory effective date, and app version. Share only selected diagnostic evidence with support. Do not bypass a blocker by editing generated results.

Related guidePayroll preparation checklistRelated guidePayroll finalisation blockedRelated guideSupport cannot see my payroll data