Use this guide when an employee row in Documents → Payslips says Generation Failed or Not generated, or an expected employee is absent. Generating payslips does not recalculate or finalise payroll.

What to check first

The Payroll run selector can show All Payruns for browsing. Generation requires a specific finalised run. Search for the employee and confirm the active organisation, run, and payroll period. Local save status concerns saved copies; Not saved locally does not mean generation failed.

Common causes

  • The wrong organisation or run is selected.
  • The run is not finalised, or Generate payslips has not been used for it.
  • Source employee or payroll data failed validation.
  • Generation or local document storage failed, or the action is unavailable to the current user.

How to fix it

  1. Select the run and employee

    Choose the intended finalised run in Payroll run, search for the employee, and refresh the page.

  2. Read the row status

    Open Details if available. Identify whether the issue belongs to the employee, payroll run, or document generation.

  3. Resolve the source issue

    Fix the issue in its owning workflow. Review employee statutory readiness if the message names missing employee data.

  4. Generate again

    Select Generate payslips when available, then refresh and inspect the employee row.

  5. Preview the ready document

    When the row says Document Ready, use Preview to confirm period, gross pay, and net pay. Save a PDF only if needed.

Still stuck

Record the organisation, selected run, employee code, row status, and exact displayed error. Avoid sharing a payroll file unless your approved support process requires it.

Related guideGenerate payslipsRelated guideDocuments overviewRelated guideGenerated document hash missing