Say Goodbye to Duplicate Rule Sets! Multi-Period Support is Available

Managing payroll for a diverse workforce can quickly turn into an administrative headache. If you run a business with employees on different pay schedules - such as weekly full-timers and fortnightly casuals - who happen to share the exact same overtime rules, you’ve likely had to make copies of entire rule sets for every different rule set period or period ending date.

We are thrilled to announce that we have released Multi-Period Support for Pay Condition Rule Sets.

What’s new?
You can now add multiple rule set periods, by pinning one or more pay schedules, to a single pay condition rule set, with each period containing its own frequency and end date.

The system will automatically resolve the correct rule set period per employee when interpreting pay conditions for timesheet costing and evaluating pay run earnings.

When you install an award update, you don't have to worry about losing your custom setups. Choosing the option to preserve custom rule set period will keep your multi-period configurations completely intact.

API enhancements
For users utilising our pay condition API, we have updated the infrastructure to support these multi-period capabilities. A new periods array has been introduced to read and write period types, end dates, and payScheduleId pins. Legacy top-level period fields are preserved for backward compatibility; however, if the new periods array is provided in a write request, it takes precedence and legacy fields are ignored.

Learn more about automating payroll rules for multi-period pay condition sets.