From clock-in to payslip: how attendance, rosters and payroll connect

Payroll disputes are almost never about money. They are about two people remembering the same month differently. The fix is not a better argument — it is one record that both of them can read.

The chain, end to end

Six things happen between someone arriving for a shift and being paid for it:

1. The roster says who was supposed to work, from a shift template with its own start, end and breaks.
2. The clock-in records who actually arrived, and when, with late and absent flags.
3. Changes — a swap request approved by a manager, or an override that makes a day off.
4. Leave is deducted from a balance that was accrued, not invented.
5. Overtime beyond the scheduled hours is recorded with a type and a multiplier.
6. Payroll turns all of the above into a payslip, which is approved and then paid.

Break that chain anywhere and the last step becomes a negotiation. Keep it intact and the payslip is arithmetic that anyone can check.

Templates and rosters, not a photo of a whiteboard

A shift template is the shape of a shift: a start, an end, and the breaks inside it marked paid or unpaid. A schedule attaches an employee to a template on specific weekdays, with an effective-from date so a change does not rewrite history.

Two features do most of the practical work here:

• Overrides. One person, one date, a different shift — or no shift at all. This is how you handle real life without editing the recurring pattern.
• Swap requests. Two employees agree, a manager approves, and the roster changes. The important part is the approval: an unapproved swap is why nobody turned up on Saturday.

Leave has to be defined before it is requested

A leave policy is a set of decisions made once: how many days of each type, whether half days are allowed, how much carries forward into next year, whether unused days can be paid out, and at what rate.

Types matter more than people expect. Annual, sick, personal, unpaid, emergency, maternity, paternity, bereavement, study and compensatory are not interchangeable. Once each has a balance, a request checks against the right one and the answer stops being a mood.

Overtime is a policy, not a case-by-case favour

Overtime carries a type and a multiplier, and the types are genuinely different:

Set the multipliers once, in policy, and every case afterwards is applied rather than debated. Overtime can also be compensated as time off instead of pay, which is often what a tired kitchen would rather have — but only if the system records it, otherwise it evaporates.

What ends up on the payslip

The payslip is not just base salary plus overtime. It carries working days, absent days, late days and total hours, plus bonuses, deductions, leave deductions and any warning deductions — and then the statutory lines: employee social security, health insurance, pension, income tax computed from your configured brackets, the employer’s own contributions, and an end-of-service provision.

One warning worth acting on: those statutory lines are computed from the payroll policy attached to the branch. If a branch has no policy configured, they come out as zero and nothing complains. Configure a policy per branch before your first real payroll run, not after someone asks why a payslip has no deductions on it.

Once approved, the payslip posts itself into the ledger: wage expense on one side, net pay and each deduction on the other. Nobody re-types it into the accounts.

The four habits that end payroll disputes

1. One clock-in method, used by everyone. Mixed methods produce mixed evidence.
2. Approve swaps and overtime the same week, not at month end. Memory is the problem you are solving.
3. Publish the roster far enough ahead that a swap is a request, not a crisis.
4. Show the employee their own hours before you close the period. Ten minutes of checking beats an hour of arguing.

None of this makes staff cost less. It makes staff cost knowable — and a labour percentage you can trust is the difference between rostering and guessing.