Paydae prepares statutory files and local evidence. Submit through the relevant authority channel and retain the authority’s response. A generated file, preview, local save, or proof package does not by itself establish filing, payment, or acceptance.

Before an external action

Confirm the active organisation, authority registration, reporting period, population, currency, source payroll coverage, pack reference, validation result, and generated file. Review current authority instructions for the form, channel, and applicable deadline. Keep the file and the person authorised to submit under your organisation’s controls.

PAYE through TaRMS

ZIMRA describes separate FDS and Non-FDS employee uploads and a single consolidated PAYE return for the tax period. Return submission and payment are separate actions. Check the applicable ZIMRA notice and employer account for current dates and any special extension. ZIMRA’s PAYE employee-management guidance explains the population split.

In Paydae, use Calendar → PAYE work to record the relevant external filing receipt, actual date, payment transfer, and allocation evidence. Importing a source file alone does not mark an action complete. An internal P2 working report can support reconciliation without being described as the submitted TaRMS return.

NSSA and ZIMDEF

NSSA directs employers to its self-service portal for monthly P4 filing and describes P4A, employee registration or cessation, and APWCS records separately. ZIMDEF’s declaration and levy follow its own employer process. Check each authority’s current requirements before relying on a generated Paydae output. See NSSA contributions and ZIMDEF FAQs.

After submission or payment

Retain the actual portal acknowledgement, rejection, reference, date, and relevant payment proof. Compare these with the generated file and employer period. If a recipient rejects the file, preserve its response and follow the appropriate correction process; changing a local generated status does not amend an authority record.