What Your Tax Code Actually Means (And Why It's Probably Wrong)
HMRC issues millions of tax codes a year on estimates, not facts. If yours was never corrected after a job change, you've likely been overpaying without knowing it.
By Firoz Khan|29 May 2026|Updated 20 September 2026|9 min read
Your tax code is not administrative wallpaper on your payslip. It is the single instruction that tells your employer how much of your income to hand to HMRC before you ever see it, and HMRC builds that instruction from old information, guesswork and assumptions that often stop being true the moment your circumstances change. Nobody checks it for you. Millions of people are sitting on the wrong code right now, usually because they changed jobs, picked up a second income, or started a pension, and the system never caught up. Here's how the code actually works, which codes are red flags, and how to get your money back if HMRC has been taking too much.
How the code is actually built
A tax code has two parts, and both mean something specific. The number is your tax-free personal allowance divided by 10. So 1257 means £12,570, the standard personal allowance for 2026/27, the amount you can earn before any income tax applies at all. The letter describes your situation: L for the standard allowance, M or N for Marriage Allowance transfers, T for cases HMRC wants to review manually. The whole code exists so your employer's payroll software can calculate tax deductions automatically, without HMRC having to touch every payslip in the country.
1257L: the default most people should have
1257L is the standard code for anyone with one job, no untaxed income, and the full personal allowance. If you have a single PAYE job and nothing complicated going on, this is what you want to see on your payslip. It means you're taxed at 0% on the first £12,570 you earn in the tax year, then 20% on income up to £50,270, then 40% above that. If your code says something else and you can't explain why, that's the first sign something in HMRC's records doesn't match your actual situation.
BR, emergency codes and other warning signs
BR means Basic Rate, and it taxes every pound you earn at 20% with no tax-free allowance at all. It's commonly applied to a second job or a new job where HMRC hasn't yet received your details, on the assumption you're already using your allowance elsewhere. Emergency codes, usually written as 1257L W1, 1257L M1 or 1257L X, are temporary placeholders applied when you start a new job without a P45. They calculate tax on that single pay period in isolation rather than across the whole year, which frequently overtaxes you in the short term until HMRC issues a correct, cumulative code.
Newsletter
Get the best of our crypto and money content every week
Straight to your inbox, once a week.
By subscribing you agree to receive our weekly newsletter and to our Privacy Policy. No spam, unsubscribe anytime.
K codes: when the taxman thinks you owe, not that you're owed
A K code is the opposite of a normal allowance. Instead of reducing your taxable income, it adds to it, and it appears when you have income HMRC can't collect any other way, commonly company benefits like a car, or when you're repaying tax owed from a previous year through your current salary. A code like K475 effectively adds £4,750 to your taxable pay before tax is worked out. K codes are legal and sometimes correct, but they're also where errors compound fastest, because they're built from estimates of benefit values that change year to year.
Why HMRC's estimate breaks after a job change
HMRC updates your code using information from your employer, your pension provider and your previous year's return, and all of that arrives with a lag. Change jobs mid-year and HMRC may still be expecting income from your old employer, or applying an emergency code until the new employer's data settles in. Pick up a second income, a side business, or rental income, and the system often doesn't adjust your main job's code to account for it, which can leave you underpaying tax that gets clawed back later, or overpaying because two employers both think you're entitled to the full allowance.
Checking your code through the Personal Tax Account
You can check your current code for free at gov.uk through your Personal Tax Account, which shows the code HMRC has on file, the reasoning behind it, and any adjustments feeding into it, such as benefits in kind or previous underpayments. Compare that against your latest payslip. If the two don't match, or the code shown doesn't reflect your actual circumstances, for example you left a second job six months ago and it's still being factored in, that mismatch is worth querying directly rather than assuming payroll will sort it out on its own.
Claiming back what you overpaid
If you've been on the wrong code, HMRC will usually correct it going forward once notified, but that doesn't automatically refund what you've already overpaid. You can claim a tax refund for the current year and the previous four tax years by contacting HMRC directly or through your Personal Tax Account, and for straightforward cases the refund is often processed within a few weeks. You don't need a paid agent for this. The claim itself is free, and HMRC does not proactively tell you that you're owed money, even when its own systems generated the error.
What a year on the wrong code actually costs you
Take someone earning £45,000 who starts a second, lower-paid job and gets put on a BR code for it while their main job's code isn't adjusted. If the second job pays £6,000 a year, taxing all of it at 20% costs £1,200, when in reality some of that income should have used unused allowance elsewhere or been taxed at the correct blended rate. Multiply a smaller error, say £50 a month from an outdated K code, across 12 months and it's £600 gone quietly, every single year, until someone checks. The mistake compounds silently because payslips look official and correct even when they aren't.
A reminder
The FCA risk warning still applies to higher-risk crypto content. Always assess how much risk you are willing to take before buying.
Related reading