A new tax year in the engine
January was about getting Mintage Payroll ready for the 2025 PAYE rules before they were needed on a live payroll. We added a 2025 PAYE deduction for each pay frequency we support (monthly, bimonthly, fortnightly and weekly) and stored the threshold year with it, so older rules stay intact for past periods.
The rules now look at more than salary. We added a number-of-children field to the PAYE settings for each employee, and the PAYE and net salary calculations now take children and overtime into account. On the payroll grid, a small tag shows which threshold year an employee is on, and a child icon shows how many children are recorded.
Small things payroll staff notice
The salary adjustment dialog gained a way to work backwards from a target net salary. It takes health and life insurance into account and has a switch for employees who are not eligible for NIS because of their age. We also tightened NIS number validation, so numbers in the wrong format are flagged on the payroll screen before anything is filed.
Each employee record now has a payslip delivery setting, so a company can choose email, WhatsApp or both for each person. The employee change history, which used to be a plain list, became a table grouped by record type, with readable dates and a clear "Nil" where a field had no earlier value.
Under the hood
Behind the scenes, PAYE and NIS submission exports moved behind split buttons, fields that the PAYE and NIS logic depends on were locked against accidental edits, and the team added new tests alongside the calculation changes. It was a busy month, with 339 commits across the backend and frontend.
This article was written from Mintage Payroll’s commit history for January 2025. See Mintage Payroll today