One employee, entered once
Many companies keep their HR records in one place and their payroll in another, and the same person ends up being typed in twice. With Mintage Workforce and Mintage Payroll now used side by side, April's main job was to close that gap.
When someone is added in Workforce, it now notifies Payroll, which pulls the employee in and places them in a staging area for a payroll officer to review before they join a pay run. Workforce records do not always carry everything payroll needs, so we added sensible fallbacks: a default department, designation and location, a default start date and address, and clearly marked placeholders for TIN and NIS numbers that still need to be collected. The aim is that a sync never fails silently because one field is blank. Payroll can also serve a single employee's profile back to Workforce.
Cleaning up the details
Child allowance records sometimes ended up duplicated, so we added a screen to merge duplicate children, including records under the 2026 rules. The year-to-date update was made repeatable, so running it twice no longer changes the result, and exports now label the periods they cover. We also lifted the Form 7B child allowance ceiling in the report, and settings now protect against switching off the last active NIS or PAYE version.
Also in April
We built a dedicated pay module for a client whose crews rotate between offshore and onshore roles, with role-based day counts, net pay and its own payroll screens. Bank export settings were extended, an NIS fix landed for employees aged 60 and over, and our release versions now carry a date-based number. At 102 commits, it was the lightest month of the year so far.
This article was written from Mintage Payroll’s commit history for April 2026. See Mintage Payroll today