Payment batches: splitting a pay run your way

Not everyone is paid the same way

A single pay period rarely means a single payment run. Some staff are paid on one day and others on another, different groups go through different approval steps, and some payments need to go out separately. Until now, Mintage Payroll treated a period as one block.

Payment batches change that. Each pay period can be divided into named batches, and anyone not placed in a batch falls into an automatic remainder, so nobody is left out. Exports and payslip delivery can be scoped to a batch, batches carry over to the next period, and permissions control who can manage them. Batches are managed inline in the payroll grid, each with its own colour, and the grid can be filtered by batch.

Checking the work

We also built a separate audit feed that gives automated checks a structured view of a company's payroll: PAYE year evidence, NIS inputs, child allowance activity and PAYE auto-adjust balances, across weekly, bimonthly, fortnightly and monthly payrolls. Where personal details are not needed, the data is anonymised. Related work added an optional new way of spreading PAYE across fortnights in a month, switched on through a one-time cutover at payroll close.

Also in August

Employees can now split their pay across bank accounts by percentage, and a bank recipient export was aligned to its required file format. Exchange transfers now keep custom fields and run a compatibility check before anything moves. The backend moved to Laravel 13, AI desktop assistants can now connect to the Agent Gateway through a standard sign-in flow, and in-app support now runs through our shared support portal. August came to 255 commits.