Statutory output missing
Diagnose an unavailable, blocked, pending, or not-yet-generated statutory document.
Identify the scope3 sections
Use this guide when a row is unavailable, validation is blocked, or no generated file is shown in Documents → Statutory Filings.
Identify the scope
Each output asks for its own criteria. Registration needs selected employees and an effective date. FDS and Non-FDS earnings need a reporting month, with an optional single-run extract. NSSA P4 needs a contribution month. ZIMDEF needs a declaration month and any reviewed adjustments. There is no global payroll-run selector for every output.
How to fix it
- Confirm the output and scope
Confirm the active organisation and select the correct authority row. Read its availability and required criteria.
- Read validation
Enter the criteria and wait for the validation preview. Review source runs, eligible and skipped employees, blockers, warnings, and totals.
- Check monthly source coverage
If monthly source coverage is incomplete or ambiguous, review all relevant finalised regular and off-cycle runs for that month. A single-run extract does not establish complete monthly coverage.
- Resolve source issues
Resolve employer identifiers, employee statutory data, applicability, currency, or pack issues in their owning screens. A run retains its captured pack even if the workspace default has changed.
- Generate and inspect history
Refresh the validation preview. Generate only when the output permits it, then inspect history and use Save generated file locally or Save historical file.
- Record unsupported status
If the row is unavailable because its renderer or mapping is unsupported, retain the displayed reason. Do not relabel another report as an official output.
Still stuck
Record the output name, month or effective date, selected employees or extract run, source-run list, validation issues, and generated-history status. A missing generated file does not prove an authority rejected a filing.