Wrong Tax Code Notice From HMRC: What It Means

HMRC just sent you a letter about your tax code, and now you are not sure whether to ignore it, panic, or call in sick. Before you do any of those things: that notice almost certainly means your employer has been taxing you at the wrong rate, and the fix is simpler than HMRC's formatting suggests.

Why HMRC Sent You a Tax Code Notice at All

HMRC does not send a coding notice because it suspects you of anything. It sends one whenever its systems recalculate your tax position, which happens more often than most people realise. Common triggers include:

• Starting a new job or changing employer
• HMRC receiving information about an untaxed source of income (rental income, freelance work, savings interest above the Personal Savings Allowance)
• A benefit in kind being added or removed by your employer, such as a company car or private medical insurance
• Your marriage allowance being applied, transferred, or cancelled
• An underpayment from a previous year being collected through your code
• A change in your pension contributions affecting the tax relief calculation

The critical thing to understand is that HMRC builds your code from data it holds on file. If that data is out of date, incorrect, or based on assumptions, your coding notice will reflect those errors. HMRC is not checking with you first. It is acting on whatever information it has, and then telling you the result.

What the Notice Actually Says: Reading the P2

Your coding notice, formally called a P2, lists every component that goes into your tax code. It is worth reading it line by line rather than skipping to the four-digit number at the end.

The notice will show:

Allowances added to your code (things that reduce your tax bill): your Personal Allowance (£12,570 in 2025-26 for most people), any marriage allowance transfer, pension contributions, professional subscriptions, and job expenses HMRC has already approved.

Deductions subtracted from your code (things that increase your tax bill): untaxed income from other sources, underpayments from previous years being collected, and the value of any taxable benefits your employer provides.

The final number is the result of all allowances minus all deductions, divided by ten. A code of 1257L means £12,570 of tax-free income. If a deduction has been applied incorrectly, that number shrinks and you pay more tax than you should.

The Most Common Errors on a Coding Notice

Phantom benefits in kind. Your employer told HMRC you have a company car. You handed it back two years ago. HMRC is still deducting the estimated benefit from your code, costing you hundreds of pounds a year.

Stale second income estimates. You did some freelance work four years ago and declared it on Self Assessment. HMRC assumed you would earn the same amount every year. You have not done a day of freelance since. The deduction is still there.

Underpayment from a previous year being collected twice. HMRC can spread underpayments across your tax code to recover them gradually. If a previous year's Self Assessment return has already settled that debt, the coding deduction should have been removed. It sometimes is not.

Marriage allowance applied incorrectly. If you or your partner has transferred marriage allowance but your circumstances have changed (divorce, a change in income levels, or one of you now earns above £50,270), the allowance may still be listed incorrectly. See our post on N Tax Code Marriage Allowance: What the Transfer Actually Does for the specific mechanics.

Wrong Personal Allowance. If HMRC believes your income exceeds £100,000, your Personal Allowance is tapered at £1 for every £2 over that threshold. If that estimate is wrong, the deduction is wrong.

The Real Cost of a Wrong Tax Code Notice

Here is a concrete example. Suppose your correct tax code should be 1257L but HMRC has issued a code of 857L because it thinks you are receiving a £4,000 company car benefit you no longer have. That £4,000 deduction reduces your tax-free allowance by £4,000. At the basic rate of 20%, that is £800 of extra tax you pay per year, or roughly £67 per month, leaving your account without justification.

If this has been running for three years without correction, that is £2,400 you could have spent on anything other than an error HMRC's own systems introduced.

This is not a hypothetical. The HMRC Tax Overpayment Repayment: Why the Money Is Yours post covers what happens when you finally reclaim it, but the sharper point is that none of this money would have left your account if the coding notice had been correct in the first place.

How to Challenge a Wrong Tax Code Notice

HMRC gives you the right to dispute a coding notice. The question is how quickly you act, because every pay period you delay is another month of incorrect tax deductions.

Step One: Identify Exactly What Is Wrong

Before contacting HMRC, be specific. Do not just say the code looks wrong. Find the exact line on the P2 that contains the error. Is there a benefit in kind listed that you no longer receive? Is there an underpayment deduction for a year you believe is already settled? Is the estimate for untaxed income wildly inaccurate?

Having a specific objection shortens every conversation you have with HMRC considerably.

Step Two: Use Your Personal Tax Account First

For many straightforward corrections, you do not need to phone anyone. Log into your HMRC Personal Tax Account, navigate to the PAYE section, and review your income and tax code details. If HMRC has incorrect information about a benefit in kind or estimated income, you can update or dispute it directly within the account.

Our post on HMRC Personal Tax Account: Update Your Tax Code Today walks through the specific steps in detail.

Step Three: Call or Write to HMRC

If the issue is more complex, including a multi-year underpayment being collected incorrectly, or a deduction that keeps reappearing after you have removed it, contact HMRC's Income Tax helpline on 0300 200 3300. Have your National Insurance number, your P2 reference, and the specific figure you are disputing ready before you dial. Vague calls produce vague results.

You can also write to HMRC at Pay As You Earn and Self Assessment, HM Revenue and Customs, BX9 1AS. Written challenges create a paper trail, which matters if the dispute takes more than one attempt to resolve.

Step Four: Tell Your Employer

Once HMRC issues a corrected coding notice, your employer should receive a copy and update their payroll automatically. However, it is worth confirming with your payroll department that the new code has been applied, particularly if you are paid weekly or your payroll runs on a tight schedule. A corrected code that sits in someone's inbox for three weeks is a corrected code that has not actually helped you yet.

If your employer is applying a code that HMRC itself has not yet corrected, you may find the guidance in Tax Code Error Your Employer Hasn't Fixed: Now What? useful for navigating that specific situation.

If the Wrong Code Has Been Running for Years

A wrong code that runs for a single month is a minor irritation. A wrong code that has been running since 2021 is a meaningful financial loss.

The good news is that HMRC allows you to reclaim overpaid income tax going back four tax years. The less good news is that it does not happen automatically. HMRC may send a P800 reconciliation letter at the end of the tax year identifying an overpayment, but this is not guaranteed, and the P800 system has its own delays and errors. We covered what those letters actually mean in Annual Tax Calculation P800: What HMRC's Letter Really Means.

If you have identified that a wrong code has been applied for multiple years, the cleanest approach is to write to HMRC setting out each tax year affected, the code that was applied, and the code that should have been applied. Include payslip evidence where you have it. HMRC will calculate the overpayment and either issue a cheque or arrange a bank transfer, usually within eight to twelve weeks.

Why Wrong Coding Notices Keep Happening

It would be reassuring to say this is a rare administrative glitch. It is not. HMRC's PAYE system processes information from millions of employers, pension providers, and financial institutions, often on a lag. When your employer tells HMRC about a benefit in kind, that information may sit in a queue before it updates your record. When you stop receiving that benefit, there is no automatic trigger to remove it.

The system is reactive, not proactive. It relies on you noticing the error.

This is a structural problem. HMRC's own data shows that tens of millions of PAYE coding notices are issued each year. The organisation does not have the resource to audit each one for accuracy. That responsibility, by default, falls on you, the person affected.

The practical implication is that checking your tax code is not a one-off task you do when something goes wrong. It is something worth reviewing at the start of every tax year when HMRC issues updated notices, and again whenever your employment circumstances change.

You can do that in minutes at /check-my-tax-code.

Multiple Jobs, Pension Income, and Coding Notices

If you have more than one source of PAYE income, whether that is two jobs, a job and a pension, or a job and rental income being collected through your code, the picture becomes more complicated.

HMRC assigns your full Personal Allowance to your primary income source and applies a BR (basic rate, 20%) or D0 (higher rate, 40%) code to secondary sources. If HMRC has misidentified which job is your primary employer, or if your total income across all sources crosses a tax band boundary, a wrong coding notice can leave you significantly under or overpaying.

The Tax Code Suffixes UK: What the Letter After the Number Does post covers how letters like BR, D0, and NT interact across multiple income sources. If you have more than one PAYE job, reading that alongside your coding notice will help you spot whether HMRC has allocated your allowances correctly.

One Check You Can Do Right Now

If you have a payslip within arm's reach, find the tax code printed on it. Then visit /check-my-tax-code and enter your gross salary and the code shown. The tool will tell you immediately whether the code looks correct for your circumstances, and flag the most likely errors if it does not.

That four-digit code on your payslip is not decorative. It is the instruction your employer uses to calculate how much of your money to send to HMRC every single month. If HMRC sent you a notice that changed it, and that notice is based on wrong information, every subsequent payslip is wrong too.

The letter sitting on your kitchen counter is not bureaucratic noise. It is HMRC changing the rules of your tax calculation. You have every right to check those rules, and to correct them when they are wrong.

You might also like

Photo: Unsplash

Tax Tips

Reasonable Excuse HMRC Penalty: What Actually Qualifies

HMRC rejects most reasonable excuse claims. Here's what the law actually says qualifies, what doesn't, and how sole traders can build a winning case.

26 May 20269 min read

Photo: Unsplash

Tax Tips

Expense Tracker for Sole Traders: What HMRC Actually Requires

HMRC's MTD rules change what a sole trader expense tracker must do. Here's what actually counts as compliant digital record-keeping — and what doesn't.

24 May 202610 min read

Photo: Unsplash

Tax Tips

Remote Worker Sole Trader Tax Return: The Home Office Trap

Working from home as a sole trader sounds simple until HMRC's rules bite. Here's what remote worker sole traders actually owe and can claim.

23 May 20269 min read