National Minimum Wage Age Bands: What UK Employers Need to Know in 2026

If you employ workers across different age groups, you're juggling up to four different minimum hourly rates at any given time. Get one wrong and you could face fines of up to 200% of the underpayment, plus public naming by HMRC. With rates updated again from 1 April 2026 and the government signalling a move towards a single adult rate, now is the time to make sure your rota and payroll processes are set up correctly. This guide breaks down the current age-band rates, explains what happens when workers cross age thresholds, and shows you how to catch compliance issues before they reach payroll.

Key Takeaways

• The UK's national minimum wage has four age-based pay bands, and rates change every April. The National Living Wage (NLW) of £12.71 per hour now applies from age 21.

• When a worker crosses an age threshold (turning 18 or 21), their pay rate must increase from that exact birthday, not at the next pay period or the next April uplift.

• In Round 22 of the government's naming scheme (October 2025), HMRC publicly named 491 employers for underpaying 41,923 workers, with 28% of those breaches involving incorrect apprentice rates.

• Scheduling software like Deputy can help employers track age-based pay rates, surface potential pay discrepancies during scheduling, and support compliance workflows before payroll is processed.

Table of contents

1. Current national minimum wage rates by age band (2026/27)

2. How age band changes affect your rota and payroll

3. Common mistakes that land employers on the naming list

4. The government's plan to phase out age bands

5. How scheduling software supports NMW compliance across age bands

6. A quick-reference checklist for NMW age band compliance

7. Conclusion

8. FAQs

Current national minimum wage rates by age band (2026/27)

If you employ workers across different age groups, you're dealing with up to four different hourly rates at any given time. Here's what applies from 1 April 2026.

A few things to note about how these bands work:

• The National Living Wage (NLW) is the highest band and now applies from age 21. This changed in April 2024, when the threshold dropped from 23 to 21. If you still think of 23 as the NLW trigger, you need to update your records.

• The apprentice rate applies to apprentices aged under 19, or to those aged 19 and over who are still in their first year of apprenticeship. After that first year (or once they turn 19, whichever comes later), the standard age-band rate applies.

• Rates are set by the Low Pay Commission and reviewed each year, taking effect every April.

For the official rate tables and historical rates, see the gov.uk national minimum wage guidance.

How age band changes affect your rota and payroll

The rates in the table above are straightforward enough. The operational headache starts when your workers cross age thresholds mid-rota or mid-pay period.

When a team member turns 18 or 21, their minimum hourly rate increases on their birthday. You don't wait until the next pay period. You don't wait until the following April. The higher rate kicks in from the exact date they reach the new age band.

This creates a real challenge for rota planning. Picture this: you've published next week's rota and one of your team members turns 21 on Wednesday. Monday and Tuesday's shifts should be costed at the 18-to-20 rate. Wednesday onwards should reflect the NLW rate of £12.71. If your payroll system or rota doesn't account for that mid-week change, you could end up underpaying without realising it.

This isn't a rare scenario. According to Deputy's UK Big Shift Report 2026, Gen Z now represents 44% of UK shift workers, up from 39% in 2024. That means a large and growing share of frontline workers are in the age range where birthday-triggered rate changes are most common.

The April 2024 change that brought the NLW threshold down to age 21 caught many employers off guard. Businesses had to reclassify every 21- and 22-year-old on their books overnight, updating pay rates across rotas and payroll systems in one go.

What to do when a team member crosses an age threshold

Follow these steps each time a worker approaches a birthday that triggers a rate change:

1. Update their pay rate in your system before their next scheduled shift. Don't wait for payroll to catch it. Make the change proactively so any rota published for shifts after their birthday reflects the correct rate.

2. Review any shifts already published for the pay period. If shifts falling after the birthday were built at the old rate, adjust them. This is where rota-stage reviews can help identify potential pay-rate issues before payroll-stage corrections are needed.

3. Communicate the change to the worker. Let them know their rate is increasing and when the change takes effect.

4. Confirm payroll reflects the new rate from the exact birthday date. Run a check before the pay run closes to make sure no shifts are costed at the old rate after the threshold date.

Keeping a calendar of upcoming birthdays that trigger rate changes is one of the simplest compliance steps you can take, and one of the most commonly missed.

Common mistakes that land employers on the naming list

The UK government operates a naming scheme for employers who underpay the national minimum wage. Being named isn't just embarrassing. It comes with financial penalties that can be severe.

In Round 22 (published October 2025), HMRC publicly named 491 employers for underpaying a combined 41,923 workers. Total repayments reached £6.2 million. The most common reason for breaches, accounting for 28% of cases, was failing to pay the correct apprentice rate.

Other common errors include:

• Not updating rates when workers change age bands. This is the exact scenario described above: a worker turns 18 or 21, but their pay stays at the old rate for days, weeks, or even months.

• Deductions that push effective pay below the minimum wage. Uniform costs, till shortage deductions, and even some salary sacrifice arrangements can bring a worker's effective hourly rate below their NMW band (more on this below).

• Unpaid working time. Opening and closing duties, mandatory training sessions, and team briefings that aren't recorded as paid time can all reduce effective hourly pay below the threshold.

The penalty structure is steep. HMRC can charge 200% of the underpayment as a fine, up to a maximum of £20,000 per worker. On top of that, your business name goes on the public list, which is widely covered in the press.

HMRC doesn't distinguish between intentional and accidental underpayment. A payroll error has the same consequences as a deliberate attempt to pay below the minimum wage.

Deductions that can accidentally push pay below the minimum wage

Some of the most common NMW breaches aren't caused by setting the wrong hourly rate. They happen because deductions reduce a worker's effective pay below their applicable band.

Watch for these:

• Uniform costs. If you require workers to buy or pay for branded uniforms and the cost isn't reimbursed, it reduces their effective pay. For workers close to the NMW floor, this alone can trigger a breach.

• Till shortage deductions. Deducting cash register shortfalls from a worker's pay is a common practice in retail and hospitality, but it can push their effective hourly rate below the minimum wage.

• Salary sacrifice schemes. Cycle-to-work schemes, childcare vouchers, and pension contributions above the statutory minimum all reduce gross pay. If the reduction brings the worker's effective hourly rate below NMW, it counts as a breach.

• Accommodation offset. If you provide accommodation to workers, you can offset a set amount against their pay. For 2026/27, the maximum offset is £9.99 per day. Going above this figure, or failing to account for the offset when calculating effective hourly pay, can lead to underpayment.

The lesson here: compliance isn't just about setting the right headline rate. You also need to check that deductions don't erode it.

The government's plan to phase out age bands

In August 2025, the UK government announced plans to move towards ending what it called "discriminatory age bands" in the national minimum wage structure. The Low Pay Commission received a new remit to work towards a single adult rate.

The immediate focus is the gap between the 18-to-20 rate and the NLW. The government's direction of travel is to narrow that gap over time, with the long-term goal of a unified rate for adult workers. The government expects under-18 and apprentice rates to remain separate for now, though future reviews may change this.

What does this mean for you right now? The current age-band structure still applies in full. You still need to manage multiple rates across your workforce, and you'll continue to do so for at least the next few rate-setting cycles. But the trend is clear: younger adult workers will cost more, and the wage gap between a 19-year-old and a 21-year-old will keep shrinking.

For employers who rely heavily on younger workers (and with Gen Z making up 44% of UK shift workers, that's a large number of businesses), this means planning ahead for rising labour costs. It also means the compliance complexity of managing multiple age-band rates may eventually reduce, though not yet.

The Low Pay Commission Report 2025 details the evidence behind the 2026/27 rate recommendations and the direction of travel for future changes.

Under current guidance, the best approach is to treat this as a gradual transition. Keep your systems set up for multi-rate management, review each April uplift closely, and factor rising youth wage costs into your labour budgets.

How scheduling software supports NMW compliance across age bands

Managing multiple pay rates across age bands is doable on a spreadsheet when you have a handful of staff. Once your team grows, or if you operate across multiple sites, the risk of manual errors increases fast.

This is where scheduling software earns its place. A platform like Deputy's staff rota software can help you manage rota costs across age bands by connecting employee records (including dates of birth) to pay rate configurations. Here's what that looks like in practice:

• Age-linked pay rate tracking. Employers can configure employee profiles and pay rates within Deputy. The platform can help managers review labour costs and identify potential pay-rate discrepancies during scheduling.

• Birthday threshold alerts. If configured appropriately, Deputy can help managers identify workers approaching age thresholds that may require a pay-rate review.

• Real-time labour costing. As you build your rota, Deputy shows you the cost of each shift based on the applicable pay rate. This means you can see the wage impact of different age-band rates across your team before you publish.

• Audit-ready records. Deputy maintains time-stamped scheduling and attendance records that can help support internal recordkeeping and audit preparation.

Wasib Awan, Box Office Manager at Winter Wonderland Hyde Park, says: "On Deputy you can cap people's work to 40 hours a week and make sure everybody gets at least some sort of a break during the week. But with the previous process it was all manual [and] time consuming."

For a deeper look at how this works in the hospitality sector specifically, see Deputy's NMW compliance guide for hospitality managers.

The shift from manual to system-supported compliance isn't just about convenience. It's about reducing the risk of errors that could land you on the naming list.

Why catching NMW issues at the rota stage matters more than at payroll

There's a critical difference between spotting a pay rate error when you're building the rota and spotting it after payroll has already run.

At the rota stage, fixing a rate costs you nothing. You adjust the rate, republish the rota, and move on. After payroll has processed, you're looking at back-pay calculations, payroll corrections, and potential HMRC scrutiny. The financial and administrative cost of a post-payroll fix is significantly higher.

This matters especially for businesses with a young workforce. With Gen Z representing 44% of UK shift workers, a significant portion of your team is likely in the age range where birthday-triggered rate changes happen regularly. The more workers you have crossing thresholds, the more opportunities there are for an error to slip through if you're only checking at the payroll stage.

Deputy's real-time labour costing can help managers identify potential pay-rate discrepancies while building the rota, enabling earlier review and correction where needed.

A quick-reference checklist for NMW age band compliance

Use this checklist to make sure your business stays on top of national minimum wage requirements across age bands:

• Audit employee records. Confirm that your system records every team member's date of birth accurately. Missing or incorrect dates are the root cause of many age-band errors.

• Set up birthday alerts. Flag workers approaching 18 and 21 so you can update their pay rate before, not after, the threshold date.

• Review pay rates every April. When new NMW and NLW rates take effect, update your system and check that every worker is on the correct band for their age.

• Check your deductions. Make sure no deduction (uniforms, till shortages, salary sacrifice, accommodation offset) pushes any worker's effective hourly pay below their applicable NMW rate.

• Train your managers. Front-line managers who build rotas need to understand how age-band rates work and why getting them right matters. Don't assume payroll will catch it. The Acas minimum wage guidance is a good starting point to share with your team.

• Keep records. HMRC audits require clear documentation of hours worked, rates paid, and when rate changes were applied. Make sure your timekeeping system captures this data accurately. For more on getting this right, see these time and attendance best practices.

Deputy's configurable pay rules, scheduling tools, and reporting capabilities can help support the processes outlined in this checklist and streamline compliance workflows.

Conclusion

National minimum wage age bands add a layer of complexity to rota planning and payroll that many employers underestimate. The consequences of getting it wrong are real: financial penalties of up to 200% of the underpayment per worker, public naming by HMRC, and damage to your reputation as an employer.

Here are the key actions to take away:

• Know your rates. The 2026/27 NMW and NLW rates took effect on 1 April 2026. Make sure every worker is on the correct band for their age.

• Watch for birthday thresholds. When a worker turns 18 or 21, their rate must increase from that exact date. Build this into your rota and payroll processes.

• Audit your deductions. Uniform costs, till shortages, salary sacrifice, and accommodation offsets can all push effective pay below the minimum wage.

• Catch errors early. Checking pay rates at the rota stage is simpler and cheaper than correcting them after payroll runs.

• Prepare for change. The government is working towards a single adult rate. Current age bands still apply, but plan for rising costs for younger workers.

Compliance remains the employer's responsibility. Deputy helps teams track age-based pay rates, manage scheduling workflows, maintain records, and support compliance processes across their operations.

Try Deputy for free

FAQs

Does Deputy automatically update national minimum wage rates when they change each April?

Deputy provides configurable pay rules that you can update when new NMW and NLW rates take effect each April. You'll need to review and confirm the new rates in your system, but the platform makes it straightforward to apply changes across your workforce.

What happens if I accidentally pay a worker the wrong age-band rate?

HMRC can impose a penalty of up to 200% of the underpayment (capped at £20,000 per worker) and publicly name your business. The penalty applies whether the error was intentional or accidental, so catching mistakes early is critical. Deputy's real-time labour costing helps you spot rate discrepancies at the rota stage, before they become payroll errors.

Can Deputy help identify potential pay-rate discrepancies before a rota is published?

Deputy's labour costing and scheduling tools can help managers review pay rates and labour costs during rota creation. Employers remain responsible for configuring pay rates correctly and reviewing schedules before payroll is processed.

How do I handle a worker who turns 21 in the middle of a pay period?

Update their pay rate in your system on or before their birthday. Under current NMW rules, shifts from the birthday onwards should be paid at the NLW rate (£12.71 in 2026/27). Review any shifts already published for that pay period and adjust the rate for post-birthday shifts. Deputy's birthday threshold alerts help you catch these transitions before they become payroll corrections.

Will the government remove all national minimum wage age bands?

The government announced in August 2025 that it's working towards a single adult rate by giving the Low Pay Commission a new remit. The 18-to-20 band is the immediate focus. Under-18 and apprentice rates are expected to remain for now. The timeline is gradual, and current age bands still apply in full. Deputy's configurable pay rules can be updated as bands change, helping you adapt without rebuilding your rota setup from scratch.

Do apprentice rates apply to all apprentices regardless of age?

No. The apprentice rate (£8.00 in 2026/27) applies only to apprentices aged under 19, or those aged 19 and over who are still in their first year of apprenticeship. After that, the standard age-band rate for their age applies. Deputy's age-linked pay rate tracking helps you manage this transition so apprentices move to the correct rate at the right time.