Statutory and compliance overview
Manage workspace statutory packs and review rules or non-posting tax previews before preparing official outputs.
Where to do the work3 sections
Managing statutory work involves more than opening Compliance. Paydae stores employer and employee facts, calculates payroll with a signed statutory pack, prepares documents, and tracks PAYE period evidence. The employer reviews the result and completes any required authority submission and payment.
Where to do the work
| Need | Area |
|---|---|
| Employer identifiers and applicability | Organisation statutory profile |
| Employee tax method, identity, NSSA coverage, and supporting facts | Employees |
| Rule release and effective date for new payroll | Workspace Settings → Statutory Packs |
| Rule inspection or a non-posting hypothetical calculation | Compliance → Statutory Rules or Tax Preview |
| Actual earnings, deductions, statutory liabilities, and finalised source evidence | Payroll |
| PAYE periods, coverage, filing evidence, payment reconciliation, and corrections | Calendar → PAYE work |
| Earnings, NSSA, ZIMDEF, and internal report files | Documents → Statutory Filings or Custom Reports & Proof |
Manage a reporting period
- Confirm statutory source facts
Confirm the organisation’s registrations, applicability decisions, and employee statutory data. Resolve readiness warnings in their owning screens.
- Check the applicable pack
For new payroll, review the applicable signed workspace default. Existing runs keep the exact pack they captured.
- Review finalised payroll
Calculate and finalise payroll, then inspect the statutory deductions, employer liabilities, source periods, and exceptions.
- Open the PAYE period
For PAYE, open Calendar → Needs attention and review the employer period and its separate upload, return, and payment actions. Reconcile payroll coverage before preparing monthly files.
- Prepare each output
Generate the required documents using each output’s own month, effective date, or run-extract criteria. Check eligible and skipped rows, totals, warnings, and generated history.
- Retain external evidence
Complete any official submission and payment through the relevant authority channel. Record the external receipt and payment evidence separately from the local generated file.
What local evidence proves
A preview proves only that the app calculated or validated the supplied scope. A generated file proves local preparation. A saved file proves a local copy was written. A locally recorded status, clear attention queue, or proof package does not establish that an authority accepted a filing or allocated a payment.
Check the applicable authority source for the reporting period, deadline, form, rate, and required channel. Use an internal target for planning without treating it as a legal due date.