ZIMRA FDS and Non-FDS earnings outputs
Prepare the ZIMRA FDS or Non-FDS employee earnings workbook from a finalised payroll run.
Choose the correct population3 sections
Paydae prepares separate employee earnings XLSX files for FDS and Non-FDS populations. ZIMRA describes separate uploads for those populations and one consolidated employer PAYE return for the period. The files are prepared data; review the current TaRMS template and authority requirements before submission. ZIMRA Non-FDS guidance.
Choose the correct population
An employee’s annual PAYE decision and payroll evidence determine the supported method. Non-FDS can apply when an employee starts, changes, or terminates employment within the tax year, has concurrent employment, receives a pension, or meets another method-specific condition. Review the reason shown by the app; do not change a generated file’s label to move an employee. The old set of four PAYE questions is not part of the current employee form. Use Review and set an annual PAYE decision for the current evidence flow.
FDS forecasting uses actual taxable income to date and expected regular taxable pay for the remaining months. It does not assume future one-off bonuses, overtime, leave payments, or fluctuating commission. Any refund permission is separately controlled at organisation and employee level; enabling permission does not guarantee a refund.
Prepare the reporting month
- Choose the earnings row
Open Documents → Statutory Filings and select the FDS or Non-FDS earnings row.
- Select monthly scope
Choose the Reporting month. The monthly path discovers relevant finalised payroll runs; review the source-run list and coverage. Select Payroll-run extract only when you intentionally need one run’s extract.
- Review validation
Review eligible and skipped employees, population, currency, reconciliation totals, warnings, and blockers in the validation preview.
- Resolve source issues
Resolve source employee, payroll, or pack issues. Wait for the refreshed preview after a change.
- Generate the intended file
Use Generate current monthly export for the monthly file, or Generate payroll-run extract for the explicitly selected extract. Save the generated file locally and retain its original scope.
- Reconcile external filing
Reconcile the two populations and the consolidated PAYE return outside the generated-file status. Record actual portal receipts in Calendar → PAYE work.
What to check
A run extract can omit other runs in the reporting month even when it contains every employee in that run. Generated history preserves the file’s original month or run-extract scope. The PAYE period’s payroll-coverage capture provides a separate local reconciliation of all expected runs.