Fitting more businesses
November was about flexibility. Real businesses rarely fit one template, so the main work was letting each one shape the payroll to match how it operates.
Locations were the first part. Employees can now be assigned to a location, and the master payroll sheet and other exports can be produced per location. For a business with more than one site, that turns one long report into something each site can check on its own.
The second part was custom pay items. Employers can now add and remove their own non-taxable allowances, and add custom deductions, without a code change. Those allowances also appear on the master and cash sheets, so what is configured is what gets reported.
A fix worth owning
We also found and fixed a real calculation error. Weekly and fortnightly payrolls had been using the monthly overtime formula. We added proper overtime formulas for each pay frequency, corrected the affected calculations and updated weekly and fortnightly payslips to match. It is the kind of bug that is easy to miss when most testing has focused on the monthly cycle, and we would rather say so than hide it.
Safety nets
Because payroll data is hard to recreate, the system now takes a database backup before creating a new payroll, and we added tooling for database snapshots. We also added a module for connecting to a time-tracking service, extended the weekly calendar years ahead, and made sure live environments are not filled with test payrolls by mistake.
This article was written from Mintage Payroll’s commit history for November 2021. See Mintage Payroll today