Rota and Payroll Integration: Hours, Wages and Records

By Zynthio. Published 27 September 2026. Editorial policy

General information for UK hospitality operators, not legal advice. If something here is wrong or out of date, the editorial policy explains how to report it.

Rota and payroll integration explained: which hours the law says you pay, the records you must keep, and how to check the export before payroll runs.

Rota and payroll integration means one approved set of hours travels from the rota to the payslip without being retyped. Where pay follows hours, wages are owed for the hours a worker actually worked, not for the hours a manager published days earlier, and the employer is the party who has to prove which is which.

In hospitality the two drift apart every week. Shifts are swapped on the morning, a table sits until close, a deep clean overruns, and somebody keys the difference into a spreadsheet before the payroll cut-off.

Hours worked, not hours rostered, are what gets paid

A rota is a plan. Payroll is a record of what happened. The minimum wage is worked out from pay and hours worked in a pay reference period, so the hours that count are the ones actually put in, including overtime and time that never appeared on the rota.

Government guidance says where those hours should come from: most employers use their payroll records as proof of total pay, including deductions, allowances and tips, and of total hours worked, including absences and overtime. Where hours exist only on a rota, the payroll record is a copy of a plan, not evidence of work.

Pay in the period divided by hours worked in the period has to clear the rate for that worker. Some payments never help that sum: tips, service charges and cover charges are left out of minimum wage calculations, and so is extra pay for working unsocial hours on a shift. A file that folds a late-night premium into basic pay can show an hourly rate the worker never received, and most of the pay traps behind minimum wage compliance work like that.

Failing to pay the National Minimum Wage or National Living Wage is a criminal offence, as is faking payment records. HMRC officers can carry out checks at any time and ask to see payment records, and an employer who finds an underpayment must pay the arrears immediately.

The records the law makes you keep

Three duties sit on the same underlying data, each with its own retention period.

Minimum wage records. It is the employer's responsibility to keep records proving that they are paying the minimum wage, and records created on or after 1 April 2021 must be kept for at least 6 years, counted from the last day of the pay reference period after the one they cover. The form is open, and paper or computer records both count, but employers must be able to produce records for an individual pay reference period in a single document. Three separate systems can still meet that, but only if something can assemble them into one document for one worker and one period on demand.

Itemised payslips.Section 8 of the Employment Rights Act 1996 gives a worker the right to a written itemised pay statement at or before the time wages are paid. Since 6 April 2019 the statement has also had to give, where the amount of wages or salary varies by reference to time worked, the total number of hours worked in respect of that variable amount, either as one aggregate figure or as separate figures for different types of work or different rates of pay.

Working time records.Regulation 9 of the Working Time Regulations 1998 requires records adequate to show compliance with the limits in regulations 4(1), 5A(1) and 6(1) and (7), retained for two years from the date they were made. The headline limit is an average of 48 hours a week over a 17-week reference period, which a worker may opt out of in writing. Rest entitlements sit outside that record-keeping duty but still shape the rota: an uninterrupted break of at least 20 minutes where daily working time is more than 6 hours, and at least 11 consecutive hours of rest between working days. Since 1 January 2024 the records may be kept in whatever manner and format the employer reasonably thinks fit, and an employer need not record each worker's daily working hours if compliance can be demonstrated without doing so.

Section 8 and regulation 9 both extend to England, Wales and Scotland.

Where separate rota, clock-in and payroll go wrong

The failure modes are predictable, and nearly all are transcription failures.

• Late changes. The export comes from a rota version superseded on the day, so cover shifts, swaps and early finishes never reach the file.
• Trailing time. Staff clock out after close, but the timesheet carries rostered finish times. Handover, cashing up and cleaning down are hours worked.
• Rounding. Rounding every clock-in forward and every clock-out back strips paid minutes off both ends of a shift and drags the average hourly rate down across the period.
• Deductions nobody modelled. Things the worker bought for the job and is not refunded for, such as tools, uniform and safety equipment, come off pay for minimum wage purposes.
• Accrual on the wrong hours. Irregular-hours and part-year workers accrue holiday at 12.07 percent of hours worked, for leave years starting on or after 1 April 2024. Feed that calculation rostered hours and every accrual is wrong.
• Tips through the wrong door. Tronc paid as ordinary wages distorts the minimum wage sum and cuts across the tipping rules.

The true cost of poor rota management is mostly rework of this kind, and geofenced clock-in exists because the gap between rostered and worked runs in both directions.

What rota and payroll integration should pass between systems

An integration earns its place only if it carries the fields that change a payslip.

Two design rules matter more than the field list. Approval, not publication, is the trigger: a timesheet becomes payable when a named manager signs it off, and that sign-off is what makes the record defensible later. And the flow runs one way, with corrections made upstream and re-approved rather than typed into the payroll file, because a correction made only in payroll leaves the working time record and the payslip disagreeing about the same shift.

Tips, tronc and why they travel separately

The Employment (Allocation of Tips) Act 2023 applies to tips, service charges and gratuities that employers have control or significant influence over. Employers must pass those tips on without deductions other than the usual tax and National Insurance, share them fairly and transparently following the statutory Code of Practice, and hold a written policy with records to match. Payment is due no later than the end of the month after the month the tips were received. More is coming: Acas says employers will need to consult before creating or reviewing a tipping policy, and that those changes will come into effect by the end of 2026.

A tronc is a system used to bring together tips and share them between workers, run by a troncmaster who may be a worker, an accountant or an independent company. Using one does not hand the duty away: with an independent tronc the employer must still make sure the system was set up fairly and follow the Code, which sets the minimum procedure an employer must follow.

Three rules follow for an integration. Tronc points or hours come out of the rota, not gross pay. Tronc payments stay outside the minimum wage calculation. And the tips record keeps its own policy and retention rather than living inside the payroll file. The detail sits in what the Allocation of Tips Act requires of a venue running a tronc.

Checking the export before payroll runs

An integration removes the retyping, not the check. Work the same list every period before the file goes over.

1. Reconcile three totals per site: rostered, clocked, approved. Where clocked and approved differ, record the reason against the timesheet rather than making a silent edit.
2. Look for open shifts. A shift with no clock-out, or a clock-in with no matching shift, is the commonest underpayment and the easiest to lose inside a total.
3. Divide each worker's gross pay by hours worked in the period, take off anything that does not count, and confirm the result clears the rate for their age.
4. Check that variable hours will print on the payslip, and that split rates arrive as separate figures rather than one blended number.
5. Confirm holiday and absence moved with the hours, and that irregular-hours accrual used worked hours.
6. Confirm the tronc file is separate, allocated on the published policy, and due inside the statutory deadline.

Keep the reconciliation. It is the document showing that a manager looked, which is what separates an error from a pattern.

The record an inspector will ask for

An HMRC officer asking about a pay reference period does not want a rota. They want hours worked, pay, deductions and the arithmetic, for one worker and one period, in a single document, for any period in the past six years.

Zynthio's rota and HR module runs rota to approved timesheet in one system. It costs the week live including employer NI and pension against a labour budget, showing availability and booked holiday, and clocks staff in inside a per-site geofence radius, with a per-site choice of block or flag. It generates timesheets per period, approved in bulk, with a reopenable sign-off and a payroll export. It accrues holiday at 12.07% of hours worked for irregular-hours and part-year staff, while fixed-hours staff are held on an annual 5.6-week entitlement instead, and it distributes tronc by points per position.

What it is not is a payroll bureau, and it does not file with HMRC. The accounting side exports a payroll journal with gross pay including overtime, employer NI and pension, to a wages-payable control account, in Xero's own import layouts, as CSV export only while the live Xero connection is not yet enabled. The bureau still runs the payroll. The integration decides what the payroll runs on. The rota, clocking and timesheet module is where that record gets built.

See how Zynthio handles this