Use an effective-dated rule version when a named schedule’s frequency, cadence, time zone or close-by rule changes. Existing version history remains available in View schedule details. A version starts at an occurrence boundary and cannot rewrite an occurrence that has already been materialised.

Before you begin

Confirm the organisation, the schedule and the first occurrence that should use the new rule. Review open drafts and existing periods before choosing the effective date. Use Set up pay periods to create a new named schedule instead.

Add the version

  1. Open the schedule action

    Open Payroll → Schedules. On the intended schedule, choose the row action Add effective-dated rule version. A retired schedule cannot receive a new version.

  2. Enter the new rule and effective date

    Set Version effective from, frequency, cadence anchor or scheduled weekdays, time zone, and close-by rule as applicable. Choose an occurrence boundary; follow any validation that rejects an existing materialised period.

  3. Preview the occurrences

    Select Preview occurrences. Check the service start, service end and close-by dates, especially around short months and non-working days. Resolve warnings or errors before saving. If you edit the rule after preview, preview it again.

  4. Save and review history

    Select Save new version, then open View schedule details. Confirm the new effective date and version in Rule version history. Review upcoming occurrences and any draft that may need an explicit refresh and recalculation.

Important boundaries

The close-by date is an operational deadline, not an employee payment date. A rule change does not silently alter an existing draft or finalised payroll evidence. Check Understand schedule changes and payroll drafts before preparing affected periods.

The Zimbabwe v3 RC2 pack can generate semi-monthly occurrences, but its PAYE tables do not certify semi-monthly calculation and finalisation. Confirm pack readiness before using that frequency for a pay run.