The payroll batch is the monthly payroll run: one document that gathers your active employees, calculates each one's pay and statutory contributions, and produces their payslips. It is the engine room of payroll, where a month of salaries, deductions and employer costs is worked out in a single pass.
- How a batch gathers employees and generates payslips
- The shape of the payroll calculation
- How proration handles part-month employees
- What the batch posts to your accounts
Anatomy
A batch is a light header over the payslips it creates: a serial, the period-end date, a description and a status. The substance is in what it generates, one payslip per employee, each fully calculated.
How it behaves
Generation
Running a batch queries your active employees, and for each one builds a payslip: it applies their enrolled pay items, computes the statutory contributions, and prorates a monthly salary by the actual days worked in the period. Employees with nothing active in the period are skipped, and the system expects the previous batch's payslips to be confirmed before a new run, so months do not overlap.
Lifecycle and posting
A batch runs Unconfirmed, Processing, then Complete, with Cancel available. On running, it posts the accrued payroll to your accounts, and raises a payable per statutory scheme (EPF, SOCSO, EIS, PCB and, from 2026, SKBBK), so what you owe each authority is tracked ready for payment.
Worked example
You run June payroll for twenty staff. The batch generates twenty payslips, prorating one new joiner by their part-month days, accrues the salary cost, and raises separate payables for EPF, SOCSO, EIS and PCB to be paid to the authorities.
Edge cases and good practice
- Confirm last month first. A new batch expects the prior run's payslips settled.
- Proration is by actual days, so joiners and leavers are paid for the part-month worked.
- Statutory payables are tracked per scheme, ready to pay each authority.
Related
- How to: Run a payroll batch
- Reference: Payslips
- Reference: Statutory contributions