From the time clock to the payslip: a payroll cycle nobody argues about
How to connect attendance to shifts, leave and overtime so pay becomes the result of data rather than a debate — and what remains your accountant’s responsibility.
In restaurants, the last two days of the month have a particular flavour: arguments about attendance, a dispute over two hours of overtime, an employee saying “I was here” and a manager saying “you were not”.
This is not a problem of intent. It is a problem of having no single source of truth.
What the usual arrangement looks like
Attendance in a notebook by the door, shifts in a WhatsApp group, leave agreed verbally, and payroll in a spreadsheet the accountant retypes every month. Four sources, no two of which agree.
The inevitable result: pay becomes the outcome of an argument instead of the outcome of data.
The correct arrangement: one chain
shift schedule → attendance capture → variances (late / absent / overtime)
→ approved leave → draft payroll → approval → payment
Every step feeds the next. No manual re-entry in the middle.
1. Start with policy, not with software
Any system will ask you questions you should already have answered in writing:
- Grace period: how many minutes of lateness are forgiven? Five? Ten? And after that — deducted by the minute or by the hour?
- Overtime: what threshold starts it? What multiplier on a normal day, a weekend, a public holiday, a night shift?
- Absence: authorised or unauthorised? What does each one mean?
- Leave: annual entitlement, carry-forward, approval path.
- Warnings: do they carry a financial consequence, and what is it?
A written, published policy ends 90% of disputes before they start. A policy explained verbally after a deduction produces a fresh dispute every month.
2. Attendance is captured as it happens
A book filled in at the end of the day from memory is not an attendance record. Capture it at the door or on the device already in the branch, and make sure each record carries time, branch and user.
Then watch for patterns rather than incidents: someone late every Tuesday, or one shift where punctuality collapses. A pattern can be fixed; a single incident is usually noise.
3. Schedule shifts from sales
Scheduling by feel is the most expensive line you can reduce without touching quality.
Use the sales-by-hour report: how many people do you actually need from 4 to 6 pm compared with 8 to 10 pm? Most restaurants discover they are paying full coverage during two hours that produce less than 5% of sales.
4. Draft, approve, pay
Three states, not two:
| State | Meaning |
|---|---|
| Draft | Calculated, editable, reviewable |
| Approved | Signed off, changed only with a recorded trace |
| Paid | Disbursed and posted to the books |
Separating approval from payment is what makes errors findable before the money leaves.
5. What stays with your accountant
I want to be precise here, because this part is sometimes sold with wider promises than it should be.
A system calculates accurately what rests on your operational data: base pay, overtime with its multipliers, deductions for absence, lateness and unpaid leave, and the effect of warnings — all of which derive from attendance and shifts recorded in the same system.
Statutory deductions — social insurance, income tax and what attaches to them — are a legal obligation governed by rules that change with legislation, and they are determined and reviewed with your accountant or the firm responsible for your business. Do not rely on any software to decide what must legally be withheld; rely on it to give your accountant correct data to work from.
The working rule: the system owns the operational facts, the accountant owns the legal treatment.
6. The payslip
It must be readable by someone who has never studied accounting:
- Base pay and days worked
- Overtime hours and multiplier
- Every deduction on its own line, with its reason
- Net pay
- Period and date
A payslip that explains itself ends half the questions before they are asked.
In one system
In GoSufra, attendance, shifts, leave, overtime and payroll sit inside the same platform the branches already run on, so numbers move from one step to the next without re-entry, payslips follow a draft → approved → paid path, and payment posts to the books automatically.
Before your next payroll run
- Write the lateness, overtime and leave policy on one page and put it on the wall.
- Retire the paper book and capture attendance in the system.
- Review the shift schedule against sales by hour.
- Run one draft payroll and review it with branch managers before approving.
- Sit down with your accountant and settle the legal treatment of deductions.
Run all of this from one system
POS, kitchen, inventory, recipe costing, staff and accounting — connected, and free to start.
Create your free account