The £10 million blind spot: why your payroll system cannot stop a minimum wage breach

In September 2026 the government named 658 UK employers for paying staff below the minimum wage, in the first enforcement round since the Fair Work Agency was established.
The list ran from household retail and hospitality names to nurseries, care providers and NHS trusts, with around £4m returned to workers and roughly £7m in penalties issued. In case after case the employers said the breaches were unintentional: geographical allowances calculated on top of hourly rates, salary sacrifice schemes, London weighting, and apprentices whose handover and changing time had not been counted against contracted hours. Established businesses, with mature payroll functions, caught out by the same handful of calculation edge cases. Which sets up the uncomfortable truth behind every one of these cases.
Every payroll platform on the market can calculate the minimum wage. None of them can guarantee you will not breach it. That sentence should unsettle any CFO, CHRO or General Counsel reading it, because it is not a hypothetical. It is the current state of enterprise payroll, on every major platform, for every employer with an hourly, shift-based or variable-pay workforce.
The problem is not the headline rate
National Minimum Wage compliance sounds simple: pay at or above the statutory floor. In practice it is one of the most common statutory breaches in UK payroll, and it keeps happening not because employers are cutting corners but because a handful of calculation edge cases quietly erode compliance without anyone noticing until it is too late:
- Salary sacrifice schemes that are not tested against the compliance floor before they are applied
- Age-band rate transitions missed on an employee's birthday, mid pay-period
- Overtime premiums wrongly included in the eligible pay test, masking a breach a lower basic rate would otherwise reveal
- Acting-up and substitution pay posted as a flat allowance instead of an hourly rate, hiding an effective shortfall
None of these show up as a wrong number
They show up as a breach, one that is discovered months later, after it has already been paid to hundreds or thousands of employees.
The numbers are public, growing, and coming for every sector. Recent government naming rounds have named organisations across aviation, retail, energy, hospitality, fashion and outsourcing, employers with mature HR functions, established payroll teams and, in many cases, the same SAP or third-party payroll platforms sitting on desks across the industry. Arrears must be repaid in full, and on top of that employers face a penalty of up to 200% of the underpayment per worker. This is board-level financial and reputational exposure, not a payroll-team footnote.
It is about to get harder, not easier
From April 2026 the Fair Work Agency consolidates minimum wage, holiday pay and Statutory Sick Pay enforcement under a single body with materially stronger powers than today's fragmented, HMRC-led system. Enforcement is being built to intensify at exactly the moment most payroll estates have no defence beyond catching problems in the next audit.
Here is the gap that should concern every executive who owns payroll risk. As far as we have found, no SAP-native, Workday-native or third-party payroll product currently offers real-time, preventive minimum wage enforcement. Every existing tool, including the market leaders, detects a breach after the fact, once the payment has already left the building. Detection after payment means the arrears, the penalty exposure and the reputational risk have already crystallised. By the time a report flags it, the only options left are damage control. Smaller-business platforms are starting to move in this direction, proof the demand is real, but nothing built for enterprise payroll stops a non-compliant payment before it posts.
This is where EX3 comes in
We designed the answer to exactly this gap: the Payroll Compliance Cockpit, a preventive minimum wage capability built on three pillars. Prevent: real-time enforcement at the point of calculation, stopping a non-compliant payment before it is ever paid. Detect: a live compliance dashboard with trend KPIs and red-flag alerts, so issues surface during routine monitoring, not months later. Evidence: a full, audit-ready trail built for regulator defensibility and board-level reporting.
What makes this different from a bolt-on report is where it sits and how it connects. It is a lightweight, API-driven layer that plugs into whatever payroll, HR and time system an organisation already runs, from SAP and Workday to ADP, iTrent and Ceridian, without a platform rebuild, a migration or new vendor lock-in. It deploys inside the customer's own infrastructure, so payroll data never leaves the organisation's control. EX3 supplies the software and the compliance logic; the customer's data stays exactly where it already lives.
If your organisation runs an hourly, shift-based or variable-pay workforce, the question is no longer whether your payroll system can calculate the minimum wage. It can. The question is whether anything in your payroll estate can stop a breach before it is paid, evidence every outcome for a regulator, and do it without you having to rebuild or replace the systems you already run. Right now, for the vast majority of employers, the honest answer is no.
Talk to EX3 about payroll compliance
EX3's payroll specialists work with finance and HR leaders to map exactly where minimum wage exposure sits, before the Fair Work Agency finds it first. From compliance health-checks to full deployment of the Payroll Compliance Cockpit, we help you prevent breaches, evidence every outcome and keep your existing systems in place.
Figures on naming-and-shaming rounds and the enforcement penalty regime are drawn from published UK government NMW enforcement cycles. Presented as the evidence base for this article, not as legal advice.


