UK Hospitality: Casual Staff Payroll Threshold (£184/Week Trap)
- The PAYE Threshold Trap
- AskBiz Casual Payroll Monitoring
- LEL vs Secondary Threshold: What £184/Week Actually Triggers
- The August Bank Holiday That Blew Through the Threshold
- What Actually Happens When You Miss the Registration
- Why Variable Shifts Make This Uniquely Hard to Track by Hand
- Letting Your Rota Data Do the Threshold Checking
Pub hire casual bartender at £50/shift, 3 shifts/week = £150/week (below threshold). Then add 1 extra shift = £200/week. Now PAYE required. If not registered, £500+ penalty. AskBiz alerts when casual staff hour accumulation triggers PAYE requirement.
- The PAYE Threshold Trap
- AskBiz Casual Payroll Monitoring
- LEL vs Secondary Threshold: What £184/Week Actually Triggers
- The August Bank Holiday That Blew Through the Threshold
- What Actually Happens When You Miss the Registration
The PAYE Threshold Trap#
Casual workers earning <£184/week don't require PAYE. Once they exceed it, PAYE is mandatory. Most pubs don't track cumulative hours carefully. A casual worker gradually picking up shifts hits threshold and employer doesn't realize. No PAYE filed = penalty.
AskBiz Casual Payroll Monitoring#
Tracks each casual worker's weekly earnings. When approaching £184 threshold, alerts: "Casual bartender John approaching PAYE threshold (current £175/week). Next shift brings to £225/week. Register for PAYE this week."
LEL vs Secondary Threshold: What £184/Week Actually Triggers#
The £184-a-week figure that trips up so many hospitality employers is not one single rule — it is the point where several separate PAYE and National Insurance mechanics start to bite at once, and understanding the difference matters because each threshold does something different. The Lower Earnings Limit is the point below which an employee's earnings do not count towards their National Insurance record at all — pay someone less than this consistently and, technically, that work is not building towards their state pension or contributory benefits, even though no tax or NI is actually due. Above the Lower Earnings Limit but below the Primary Threshold, the employee's earnings do count towards their NI record, but they still do not pay any employee NI out of their pay packet — it is recorded, not deducted. Only once earnings cross the Primary Threshold does the employee start actually paying NI, and separately, once earnings cross the Secondary Threshold, the employer starts owing employer NI contributions on top. Income tax follows yet another threshold tied to the personal allowance, spread across the tax year rather than assessed week by week. The practical consequence for a hospitality employer is that £184 a week is not a single trapdoor — it is the point at which HMRC requires the worker to be on the payroll and reported through Real Time Information, because from that point their earnings are provably relevant to their tax and NI position, even if the actual NI or tax deducted that particular week is nil. Treat any casual worker regularly clearing this figure as needing a proper payroll record from day one of that pattern, not from the week the total finally tips over.
The August Bank Holiday That Blew Through the Threshold#
A pub group running three sites across Bristol relied heavily on a pool of about twenty casual staff — students, part-timers, people picking up the odd shift around other jobs — most of whom worked six to ten hours a week and sat comfortably under the PAYE threshold most weeks. Over the August bank holiday weekend, footfall across all three sites roughly tripled, and the manager did what any sensible manager does: called round the casual pool and offered extra shifts to cover it. Several casual staff who normally worked one evening shift picked up three or four shifts that week to cover the holiday rush, pushing their earnings well past £184 for that single week — in a couple of cases, more than double it. Because these workers were set up in the payroll system as "casual, below threshold," nobody flagged the change, and the payroll run that week processed them exactly as it had every other week, with no PAYE registration triggered and no RTI submission reflecting their new position. It was only when the pub group's accountant reviewed quarterly figures two months later and cross-checked hours against pay that the gap surfaced. The mistake was not malicious and not even really an oversight of process — it was a mismatch between a system built for typical weeks and a business that, by its nature, has wildly atypical weeks around bank holidays, festivals, and local events. Hospitality is disproportionately exposed to exactly this kind of threshold breach because demand genuinely does swing that hard, and a payroll process that only checks thresholds at month-end will always be a step behind a shift pattern that changes week to week.
What Actually Happens When You Miss the Registration#
Missing a PAYE registration trigger is not a paperwork technicality — it has real financial and administrative consequences that compound the longer it goes unnoticed. HMRC expects PAYE to be operated and reported through Real Time Information at or before the point a worker becomes liable, and when a business discovers months later that a worker crossed the threshold and was never brought onto proper payroll reporting, the correction has to be backdated. That means recalculating what should have been deducted and reported for every affected week, filing corrected RTI submissions covering the whole period, and in cases where employer National Insurance was due and unpaid, settling that liability retrospectively along with any interest HMRC applies for late payment. Beyond the direct financial cost, a backdated correction invites more scrutiny — a business that has to go back and fix multiple weeks of payroll records for several workers is more likely to attract a wider compliance check into how casual staff are managed generally, which can surface other issues that had nothing to do with the original threshold breach. There is also a quieter cost in staff trust: a casual worker who discovers months later that a week of higher earnings was never properly recorded may reasonably wonder whether their NI record is accurate, and correcting that perception takes more than a payroll fix — it takes a conversation. None of this requires deliberate wrongdoing on the employer's part. It is simply what happens when a threshold-based system is monitored manually against a workforce whose hours genuinely vary week to week, which is precisely the situation most hospitality businesses are in.
Why Variable Shifts Make This Uniquely Hard to Track by Hand#
A retail job with fixed weekly hours makes threshold monitoring almost trivial — if someone is contracted for twelve hours a week at a known rate, you can tell at a glance, once, whether they sit above or below £184, and that answer barely changes from month to month. Hospitality does not work like that. The same worker might do eight hours one week, eighteen the next because a colleague called in sick, four the week after because trade was quiet, and twenty-two during a festival weekend. Multiply that variability across a casual pool of fifteen or twenty people across multiple sites, each paid at slightly different rates depending on role — bar staff, kitchen porters, event staff on a premium rate for a one-off function — and manually checking each person's rolling weekly total against a fixed threshold becomes a task nobody consistently has time for, particularly for a manager whose actual job that week is running a busy floor, not auditing a spreadsheet. The problem is structural, not a failure of any individual manager's diligence: the threshold check needs to happen every single week, for every single casual worker, and the input data — actual hours worked — is scattered across till clock-ins, paper rotas, and verbal shift swaps that never quite make it back to whoever runs payroll. The businesses that get caught out are rarely careless ones; they are ordinarily well-run venues where the volume and unpredictability of casual shift patterns simply outpaces a manual monitoring process built around monthly or even weekly review cycles rather than continuous, per-shift tracking.
Letting Your Rota Data Do the Threshold Checking#
The fix is not asking managers to be more vigilant — it is removing the need for anyone to manually watch a threshold at all. Because AskBiz's POS and rota system already captures every clock-in and clock-out for shift-based staff as a normal part of running the till and managing the floor, that same data can be rolled up automatically into a running weekly total for each casual worker, updated in real time as shifts are worked rather than reconstructed after the fact from paper timesheets. When a worker's rolling total for the week approaches the threshold — say, once they cross a configurable warning level below £184 — the system can flag it to whoever manages payroll, giving them the chance to confirm the worker's PAYE status before the payslip is run rather than discovering the breach weeks later during a reconciliation. Because the underlying shift and pay data already lives in one system rather than being split across a paper rota, a separate till, and a spreadsheet, there is no manual re-entry step where a threshold breach can quietly get missed. For hospitality businesses that also run payroll through Xero, that same shift and earnings data can flow through consistently, so the PAYE registration and reporting that HMRC expects lines up with what was actually worked and paid, without someone having to reconcile two separate systems by hand at month-end. The bank holiday spike that catches so many pubs and restaurants off guard stops being a threat once the threshold check happens automatically, every week, for every casual worker, rather than depending on a manager noticing during a weekend that is already the busiest of the year.
People also ask
What if a casual worker crosses threshold mid-week?
You need to register for PAYE before the week they exceed threshold. File retroactively if missed, plus penalties.
Our team combines expertise in data analytics, SME strategy, and AI tools to produce practical guides that help founders and operators make better business decisions.
Stay Compliant With Casual Payroll Thresholds
AskBiz monitors casual worker earnings. Alerts when PAYE threshold looms. Avoid penalties. Register on time. Try free.
Connects to Shopify, Xero, Amazon, QuickBooks, Stripe & more in minutes