Tax Code Notice of Coding: What HMRC Is Actually Telling You

HMRC sent you a letter. It is called a Notice of Coding, it is two pages of dense small print, and the vast majority of people file it straight in the recycling. That is an expensive habit.

The P2 Notice of Coding is one of the most financially significant documents a UK employee receives all year. It sets the tax code your employer or pension provider will use to calculate how much income tax to deduct from every single payslip until HMRC decides to change it. Get it wrong, ignore it, or misunderstand it, and you could spend twelve months overpaying tax, quietly funding the Treasury with money that is legally yours.

This post explains every section of the Notice of Coding in plain English, tells you what to look for, and shows you exactly where errors hide.

What Is a Notice of Coding?

The Notice of Coding is HMRC's working-out slip. Think of your tax code (for most people, something like 1257L in 2025/26) as the answer, and the P2 as the method. The letter breaks down how HMRC arrived at your code by totalling up everything it believes you are entitled to claim tax-free, subtracting anything it thinks you owe or that should reduce your allowance, and converting the result into that compact alphanumeric code.

Your employer never sees this working-out. They simply receive the code and apply it mechanically. Which is exactly why the detail in the notice matters so much: if HMRC's assumptions are wrong, nobody else is going to catch the mistake.

The Anatomy of the P2: Section by Section

Section 1: Allowances

This column lists every tax-free allowance HMRC is granting you. For most employees, this starts with the Personal Allowance, currently £12,570 for 2025/26. But it does not have to stop there.

If you have claimed job expenses (such as professional subscriptions, uniform costs, or tools), these should appear as additions here. If you are receiving the Marriage Allowance transfer from a partner with lower income, that £1,260 boost to your allowance should be listed. If you have a working from home allowance on record, that too should feature.

What to check: Are all your legitimate allowances listed? If you claimed flat-rate job expenses last year and they are not appearing, that is money being left on the table. HMRC does not automatically carry forward every claim; some require resubmission.

Section 2: Deductions

This is where things get complicated, and where errors most commonly lurk.

Deductions reduce your tax-free amount, meaning more of your income gets taxed. HMRC uses this section to claw back allowances or collect outstanding tax through your payslip. Common deductions include:

• State benefits taxed through PAYE (the State Pension, for example, is taxable income but is paid gross; HMRC adjusts your employment tax code to collect the shortfall)
• Underpaid tax from a previous year, carried forward and collected incrementally
• Company benefits in kind such as private medical insurance or a company car, which increase your taxable income
• Estimated income from other sources such as savings interest, rental income, or a second job

The deductions column is where HMRC's guesswork becomes your liability. If HMRC estimated you earned £3,000 in rental income last year and you earned nothing, that estimated deduction still sits in your code reducing your allowance, overtaxing every payslip until you correct it.

Section 3: The Resulting Code

At the bottom of the notice, HMRC states your final code. The number is derived by taking total allowances, subtracting total deductions, and dropping the last digit. So if your net tax-free amount is £12,570, the code number is 1257. The letter suffix (L, M, N, T, W1, and so on) tells your employer how to apply it.

If you want a deeper explanation of what each suffix letter means and why the letter matters as much as the number, the post on Tax Code Suffixes UK: What the Letter After the Number Does covers that in full.

Why HMRC Gets the Notice of Coding Wrong

HMRC processes tens of millions of tax code calculations, and the vast majority are handled by automated systems, not human caseworkers. Those systems rely on information fed to them by employers, pension providers, and HMRC's own records, all of which can be incomplete, out of date, or simply wrong.

Consider a few realistic scenarios:

The benefit-in-kind that ended. You had private medical insurance through your employer two years ago. You left that job, but HMRC's records still show the benefit. Your new employer is deducting extra tax every month to account for a perk you no longer receive.

The savings interest estimate. In 2022/23, you earned £800 in savings interest. HMRC estimated similar interest for the following year and embedded that estimate as a deduction. Interest rates changed, your savings moved, your actual interest was £120. The code was never updated.

The State Pension miscalculation. You receive both the new State Pension (currently £11,502.40 per year for 2024/25) and a small occupational pension. HMRC adjusts your employment code to collect tax on the State Pension. If the pension amount changes and HMRC's records are stale, the adjustment is wrong.

None of these errors are the employee's fault. All of them result in the wrong amount of tax being deducted. And because the Notice of Coding is sent once and then largely ignored, many persist for years.

This is precisely why checking your tax code at /check-my-tax-code is worth doing even if you have not received a new notice recently. The code active on your payslip today may reflect assumptions HMRC made months or years ago.

The Mid-Year Notice: When HMRC Changes Your Code

Most people receive a Notice of Coding in January or February, ahead of the new tax year starting in April. But HMRC can issue one at any point during the year if something changes: a new employer reports your salary, a benefit in kind is added or removed, you file a Self Assessment return, or HMRC receives new information about your income.

A mid-year notice is particularly worth scrutinising because it can trigger an immediate change to your payslip with no warning beyond the letter itself. If you miss the letter (it goes to your registered address, which may not be current, or to your Personal Tax Account inbox), the first you know about it may be a noticeably smaller pay packet.

If you have had an unexpected change in your take-home pay and cannot account for it, a new Notice of Coding is the first place to look. You can view your current and historical codes through your HMRC Personal Tax Account or by calling HMRC directly on 0300 200 3300.

For more context on why codes change mid-year, the post Why Is My Tax Code Different This Year? covers the most common triggers in detail.

How to Read the Deductions Column Without a Degree in Tax

HMRC uses specific phrases in the deductions column that sound technical but translate into plain English fairly simply.

The Personal Allowance tapers at a rate of £1 for every £2 of income above £100,000. Once your income hits £125,140, the entire Personal Allowance is withdrawn. If HMRC has incorrectly estimated your income as above £100,000, your allowance could be reduced without justification. That is one of the more punishing errors possible, and it is worth verifying independently.

What to Do If the Notice Is Wrong

First, do not wait for HMRC to spot and fix its own mistake. The system is automated and will not self-correct unless prompted.

Step 1. Identify the specific error. Is an allowance missing? Is a deduction based on outdated information? Is a benefit listed that you no longer receive?

Step 2. Contact HMRC through your Personal Tax Account, the HMRC app, or by phone on 0300 200 3300. Be specific: give the relevant section of the notice, the figure shown, and the correct figure with your reason.

Step 3. Your employer will receive an updated code electronically, usually within a few days. Your next payslip should reflect the correction.

Step 4. If you have been overtaxed while waiting for the correction, any overpayment for the current tax year will typically be refunded through your payslip once the new code is applied. HMRC calculates the cumulative position and your employer adjusts accordingly.

If the dispute is more complex, or HMRC disagrees with your correction request, the post How to Dispute an HMRC Tax Code and Win walks through the formal challenge process step by step.

One Example That Shows Why This Matters

Sarah is a nurse earning £38,000 a year. She left a job with private medical insurance two years ago, but HMRC still has that benefit listed as a deduction in her Notice of Coding, reducing her tax-free allowance by £1,200 (the taxable value of the old benefit). On a 20% basic rate, that deduction is costing her £240 per year in extra tax she does not owe.

She has never queried the notice. Over two years, that is £480 overpaid. HMRC will not volunteer a refund. The error will persist until Sarah notices, checks, and corrects it.

This is not unusual. It is, if anything, a conservative example of how a single stale entry in an automated system translates into real, recurring money leaving someone's pay packet without justification.

Checking your current tax code at /check-my-tax-code takes less time than reading this sentence twice.

The Allowances You Might Be Missing

Beyond the standard Personal Allowance, the following are legitimate allowances that should appear in the deductions-and-allowances breakdown on your P2 if they apply to you:

• Job expenses: flat-rate deductions for uniforms, tools, professional fees, and travel between workplaces. HMRC publishes industry-specific rates; if your employer has not claimed these on your behalf, you can claim directly.
• Marriage Allowance: if your partner has unused Personal Allowance, they can transfer £1,260 of it to you, saving you up to £252 per year in tax.
• Blind Person's Allowance: worth £3,070 in 2025/26 for those who qualify.
• Payroll Giving donations: charitable donations made through a payroll scheme reduce your taxable income at source.

If any of these apply to you and are not reflected in your current notice, that is a conversation worth having with HMRC sooner rather than later.

A Note for People With Multiple Income Sources

If you have more than one employer, a pension alongside employment, or any untaxed income (bank interest above your Personal Savings Allowance, for example), your Notice of Coding becomes significantly more complex. HMRC attempts to consolidate everything through your primary employment code, which can result in large, apparently unexplained deductions.

For employees who also have self-employed income, HMRC sometimes embeds an estimated tax liability into your PAYE code rather than requiring a separate payment. This can be sensible, but only if the estimate is accurate. If you have had a significantly different year of trading income, verify that HMRC's estimate in your code reflects reality.

The interaction between PAYE codes and self-assessment is covered in more depth at Why Is My Tax Code Different This Year?.

That Notice of Coding HMRC sent you is not bureaucratic wallpaper. Every line of it is a number affecting your monthly take-home pay. Most people spend more time checking their energy bill than their tax code, which is exactly why HMRC's automated errors so rarely get corrected. Start with the two minutes it takes to verify your code at /check-my-tax-code. If something is wrong, now you know what to do about it.