Police Pay Rise 2026: Is It In Your Payslip Yet?
Some forces already have the new rate showing this pay cycle. Others are still running on last year's figure, with backpay to follow. Both are completely normal. Here's how to tell which one applies to you, and what to expect either way.
- The 3.5% rise is confirmed, not in doubt. Announced 15 July 2026, effective 1 September 2026
- Your new rate is already public. Because the percentage is fixed, every pay point is a known number. See our Police Pay Scales page for your exact rank and pay point
- Implementation speed varies by force. Some forces move on their own payroll circular within weeks of the July announcement. Others take longer. Both are normal, and neither means anything's gone wrong
- If yours hasn't landed yet, you'll get backpay for every day since 1 September, usually as a lump sum on your first payslip at the new rate
- Overtime rises with it too, and backdated overtime is exactly the kind of thing worth double-checking against your own record
The rate is confirmed. Whether it's landed yet depends on your force.
On 15 July 2026, the Home Secretary confirmed a consolidated 3.5% pay rise for police officers, effective from 1 September 2026. That part is done. It's not a proposal, it's not under negotiation, and because the percentage is fixed, your new pay point is simple arithmetic on last year's confirmed rate. Find yours on our Police Pay Scales page, updated for 2026/27.
Force payroll teams typically don't wait for the full, formal Home Office determination that separately republishes the pay tables under the Police Regulations 2003. That document is a slower legal formality that has historically lagged its own effective date by months, and pay isn't held up waiting for it. Instead, most forces move once they've had the relevant pay circular confirming the specific new figures, which for other 2026 police pay bodies has followed the July announcement by anywhere from a few weeks to a couple of months. Some forces will have that sorted and applied well in time for this pay cycle. Others are still catching up. Both are normal.
Check your basic pay line against last month's. If it's roughly 3.5% higher, your force has already applied it, you're sorted. If it's identical, your force hasn't run the update yet, and you're owed backpay to 1 September once it does. Neither is a mistake, they're just different forces moving at different speeds on the same confirmed rise.
What this looks like on an actual payslip
Using a round £40,000 salary purely to illustrate the mechanics, not a real pay point, just so the maths is easy to follow, here's what each scenario looks like:
| Scenario | What you'll see | What it means |
|---|---|---|
| Your force has already applied it | £3,450/mo, roughly 3.5% above August | You're sorted. Nothing to chase, no backpay owed since it's already in there |
| Your force hasn't yet | £3,333/mo, same as August | Expect a backpay lump sum once it's applied, covering every day since 1 September |
Your actual new figure depends on your specific rank and pay point. Check our Police Pay Scales page, already updated for 2026/27, to find yours exactly.
A backpay lump sum is still just pay, with one quirk
When your force's payroll catches up and runs the backdated amount, it typically appears as a single lump sum alongside your first payslip at the new rate, rather than being spread evenly across future months. Worth knowing: a large one-off amount landing in a single pay period can occasionally push that month's tax calculation higher than normal. HMRC corrects this automatically over the following months through your tax code, so it evens out, but it's a reasonable thing to expect rather than be alarmed by if one payslip looks unusually taxed.
Overtime goes up too, and backdated overtime is worth checking
Every overtime and unsocial-hours rate you're paid is a multiplier of your base hourly rate. When the base rate rises 3.5%, time-and-a-third and time-and-a-half rise with it automatically, including on hours you've already worked since 1 September, which also get backdated.
This is the part actually worth being organised about. A basic-pay correction is one number, easy for payroll to get right. A backdated overtime correction depends on exactly which hours, on which dates, at which rate you worked, and that's the calculation most likely to come out slightly wrong on the other end, simply because payroll is reconstructing weeks of your shifts after the fact instead of you logging them as they happened.
If you've been tracking your own shifts and overtime since 1 September, checking a backdated payslip takes two minutes: pull up your log, compare it to the total, done. If you haven't, this is a good week to start. From here, every hour you log is one you won't have to reconstruct from memory later.
Know exactly what you're owed, whenever your force's payroll catches up
Overtime Live logs every shift and every overtime hour in real time, at whatever rate you set. Free, no account, no subscription. Update to your new rate today, and whenever your backpay lands, the calculation is already sitting there waiting for you.