Makes salary slips for a whole payroll period in one go, for every employee in scope. Each slip uses the person's salary structure and any adjustments recorded against them.
When to use it
Once per payroll period, after attendance for the period is settled and before you approve and pay.
Before you start
Each employee who should be paid needs an active salary assignment dated to cover the period. Anyone without one appears in the result as an error line instead of a slip. That is intended, and it is how you spot a missing assignment.
Then work through the checks below. Several of them are things the run does not do for you.
Where to find it
Open the HR area from the main menu, then Payroll, then Bulk Salary Slip Run.
The fields on this screen
How it works
Running the batch produces one salary slip per employee in scope. Slips stay drafts until they are approved and posted. Posting is what writes the salary journal.
What you must check yourself
The run will not stop you at any of these points, so make checking them a habit.
Leavers are not excluded automatically. The run picks up every employee in your organization. Marking someone inactive, or filling in a termination date on their record, does not take them out of a payroll run. The only thing that stops payment is ending their salary assignment. When somebody leaves, end the assignment as part of the leaving process, and check the run's employee list before you approve.
A compensation adjustment repeats until you close it by hand. An adjustment still marked pending is picked up by every run from its date onwards, not only the first one. After a one-off bonus or deduction has been paid, go back to Compensation Adjustment and close it, or it will be paid again next period. Compare this period's adjustment lines with last period's before approving.
Attendance marked in the mobile app does not reach this run. Phone punches are stored separately, and payroll does not read them. If your staff mark attendance on their phones, the days behind these slips come from elsewhere, so check the days on a sample of slips instead of assuming.
Holidays do not change overtime here. The run does not apply the holiday list, so an overtime rate meant to rise on a public holiday will not rise. Where that matters, handle it as an adjustment.
A salary component with an unexpected calculation type pays nothing. Components calculate on one of three bases. A component set to anything else produces a zero line and gives no warning. If somebody is paid less than expected, check their components first.
Tips and common mistakes
- Run it once and read the error lines first. They are the cheap signal that something is set up wrong, and they cost nothing to fix before slips exist.
- Approve in batches small enough that you would notice a wrong figure.
- For the first few periods, keep last period's run open beside this one. Most of the mistakes above show up as a difference between periods, not as a wrong number on its own.
Related guides
- Employee Salary Assignment: the record that decides whether somebody is paid at all
- Compensation Adjustment: one-off additions and deductions
- Salary Slip: the individual result, and where you approve
- Payroll Period: the period this run belongs to