Time off, from the ground up
Leave and payroll are tightly linked: unpaid leave reduces pay and paid leave has to be tracked against an allowance. In July we laid the data foundations for time off in Mintage. That means policy types and policies, request types and statuses, enrolments that tie an employee to a policy, and the time-off requests themselves, with seed data for common leave types so a new company does not start from a blank page.
This month was about structure rather than screens. The rules for working out balances came the following month.
A richer employee record
The employee profile kept growing. Employees can now have addresses, custom fields that each company defines for itself, an employment status, compensation details with an effective date and a reason for change, and recorded payment methods. Locations gained street and city details and a main office flag.
With so many new parts, the employee controller had become unwieldy, so we split it into small, focused pieces, one for each area such as notes, addresses or documents.
Calculations
Three new pay formulas arrived: a salary deduction by percentage, an allowance calculated as a share of basic salary, and pay reduced by NIS days, which now also shows on the payslip. We updated the framework and dependencies along the way. July came to 262 commits.
This article was written from Mintage Payroll’s commit history for July 2023. See Mintage Payroll today