How to Check If Your Tax Code Is Correct After HMRC Estimates

Your tax code was set by HMRC using guesswork. Not malicious guesswork, but guesswork all the same, based on estimates, old employer data, and assumptions about your income that may have been wrong for years. If you have never actively checked whether your tax code is correct, the statistical odds are not in your favour.

This post is not about reading the letters on your payslip. We have covered that in depth in What's My Tax Code? Read the Letters, Not Just the Numbers. This is about something more specific and more consequential: understanding how HMRC arrives at the number behind those letters, where that process breaks down, and what you need to verify to be confident your code reflects your actual circumstances.

Tax Code

A combination of numbers and letters sent by HMRC to your employer that tells them how much income tax to deduct from your pay. The number is typically your tax-free personal allowance divided by ten; the letters modify how that allowance is applied. HMRC sets your code using estimated income data, which means it can be wrong without either party noticing.

Why HMRC's Estimation Process Is the Root Problem

HMRC does not receive your P60 and then neatly recalculate your code for the new tax year. The process is messier than that. HMRC uses a system called dynamic coding, introduced to reduce year-end underpayments and overpayments. In theory, it adjusts your tax code in real time as your employer submits payroll data through Real Time Information (RTI). In practice, dynamic coding can and does overcorrect, undercorrect, or apply adjustments based on income that no longer exists.

The Office of Tax Simplification, before it was quietly wound down by the government in 2022, flagged PAYE coding errors as one of the most persistent sources of taxpayer confusion in its final reports. HMRC itself acknowledged in its 2022-23 annual report that around 5.5 million people were owed a PAYE refund at the end of that tax year, with the average overpayment running to several hundred pounds.

For a basic-rate taxpayer earning £35,000, being taxed on £1,250 less allowance than you are entitled to costs you £250 a year. Being placed on a BR code (all income taxed at 20%) instead of your correct code costs you the entire personal allowance, which at current rates means roughly £1,257 of avoidable tax deducted. These are not edge cases. They are the predictable output of a system that updates based on estimates rather than verified facts.

The Four Situations Where Your Tax Code Goes Wrong

Understanding how to check if your tax code is correct means understanding the specific circumstances that cause it to go wrong in the first place. HMRC does not randomly issue bad codes. There are four recurring failure points.

1. Benefits in Kind That Your Employer Reports Late or Incorrectly

If your employer provides a company car, private medical insurance, or other taxable benefits, those should reduce your personal allowance in your tax code. HMRC receives this information via your employer's P11D submission, which is due by 6 July after the tax year ends. That means HMRC may be coding you based on the previous year's benefit value, or on a P11D that contained an error your employer has since corrected.

If your company car was changed, your medical cover was dropped, or your employer submitted a corrected P11D, there is a reasonable chance your tax code has not caught up. The adjustment HMRC makes is based on the estimated taxable value of the benefit. If that estimate is wrong, your tax code is wrong.

2. Underpayments from Previous Years Collected Through Your Code

If you underpaid tax in a previous year and HMRC collected it via a tax code adjustment rather than a direct bill, that adjustment might still be sitting in your code after the debt is cleared. HMRC sometimes fails to remove historic underpayment adjustments, meaning you continue to pay extra tax on income you have already settled.

Check your tax code notice (sent by post or visible in your Personal Tax Account) for any deductions labelled as "underpayment" or "other income." If you cannot account for them, they warrant a call to HMRC.

3. Multiple Employers or Income Sources in a Single Year

When you change jobs, your new employer is supposed to operate your correct tax code. If you do not hand over a P45, or if your P45 is processed late, your new employer may apply a default emergency code, often 1257L on a week-one or month-one basis, or BR (basic rate on all income). Both are wrong if your personal allowance should apply to your primary employment.

We have covered this specific scenario in detail in How to Check My Tax Code After a Job Change, but the core issue is worth naming here: changing employer is the single most common trigger for a tax code error, and HMRC's RTI data does not always reconcile quickly enough to prevent overpayment.

4. Marriage Allowance Claims Not Reflected in the Code

If you or your spouse transferred part of your personal allowance through Marriage Allowance, the receiving partner should see an M suffix on their code and an increased allowance. The transferring partner should have an N suffix. If a Marriage Allowance claim was made but the code has not been updated to reflect it, one of you is overpaying. Marriage Allowance is worth up to £252 per year at current rates, and claims can be backdated up to four years, meaning a correction could unlock over £1,000.

How to Actually Verify Your Tax Code Is Correct

Checking is not the same as verifying. Looking at the letters on your payslip tells you what code HMRC has issued. It tells you nothing about whether that code is right. Verification requires cross-referencing the code against your actual circumstances.

Here is the methodical approach:

Step 1: Get your current code from your payslip or Personal Tax Account. Your payslip will show something like 1257L or 1100T. Log into your Personal Tax Account at gov.uk to see the full breakdown of how HMRC has calculated your allowance.

Step 2: Check the Personal Tax Account breakdown line by line. HMRC's Personal Tax Account shows what is adding to or subtracting from your allowance. Look for entries you do not recognise. Common unexplained deductions include old underpayment adjustments, benefits your employer no longer provides, or state pension additions that do not apply.

Step 3: Cross-reference against your current benefits in kind. Ask your employer or HR team for the current P11D value of any benefits you receive. Compare this to what HMRC has included in your code.

Step 4: Use an independent checker to validate the number. HMRC's own tool shows you what your code is, not whether it is right. Check your tax code free at TapTax to see whether the code you are on matches your actual income and allowance position. This takes under five minutes and costs nothing.

Step 5: If something is wrong, contact HMRC directly on 0300 200 3300 or update your details through your Personal Tax Account. You can also ask HMRC to send a corrected tax code notice to your employer.

People also ask

How do I know if my tax code is wrong?

Log into your Personal Tax Account at gov.uk and check the breakdown of your tax code. Look for deductions you cannot explain, such as old underpayment adjustments or benefits you no longer receive. You can also use the free checker at taptax.co.uk/check-my-tax-code to see whether your code matches your actual circumstances.

Can HMRC give me a wrong tax code without me knowing?

Yes, and it happens regularly. HMRC uses estimated income data to set tax codes, and those estimates can be outdated or simply incorrect. Around 5.5 million people were owed a PAYE refund at the end of the 2022-23 tax year, most of them without knowing their code was wrong.

How far back can I claim if my tax code has been wrong?

You can claim a refund for overpaid tax going back up to four complete tax years. So in the 2025-26 tax year, you could potentially reclaim overpaid tax dating back to 2021-22. Contact HMRC directly or use your Personal Tax Account to initiate a repayment claim.

Will HMRC automatically fix a wrong tax code?

Not reliably. HMRC may update your code when new payroll data comes in through Real Time Information, but historic errors, old underpayment adjustments, and incorrect benefit values often persist until you actively report them. Do not assume HMRC will spot and fix the problem without your input.

What a Wrong Code Actually Costs: A Concrete Example

Consider Sarah, a nurse employed by an NHS trust earning £38,000 a year. Her employer provided private healthcare cover worth £800 per year as a taxable benefit. When she opted out of that scheme in April 2024, her employer informed HR but did not immediately update HMRC via a corrected P11D.

HMRC continued to deduct £800 from Sarah's personal allowance in her 2024-25 tax code, reducing it from £12,570 to £11,770. At the basic rate of 20%, that £800 reduction cost Sarah £160 in additional tax deducted from her pay across the year. Not devastating, but entirely avoidable, and entirely invisible unless she checked.

Now extend that across four tax years, perhaps because Sarah assumed HMRC would sort it automatically. That is £640 sitting with HMRC that belongs to her. A correction today, with a four-year backdated claim, recovers the lot.

Sarah's situation is unremarkable. It is the kind of quiet, low-drama error that affects millions of PAYE employees who have no particular reason to look closely at a code they have always trusted.

The PAYE Assumption That Costs Employees Real Money

There is a persistent belief among PAYE employees that because tax is deducted automatically, it is therefore deducted correctly. This is the core misconception that makes tax code errors so expensive at scale.

Your employer deducts exactly what your tax code tells them to deduct. They do not verify whether the code is right. HMRC issues the code using estimated data. No one in the chain is specifically tasked with checking whether your individual circumstances match the code you are on. That job, by default, falls to you.

The HMRC Tax Code Errors: The Silent Pay Cut on Your Payslip post makes this point bluntly: a wrong tax code is effectively a pay cut that neither you nor your employer necessarily notices. The difference is that a pay cut requires your employer's decision. A tax code error requires nobody's decision. It just happens.

If you have changed jobs in the last two years, have any taxable benefits in kind, have made or cancelled a Marriage Allowance claim, or have ever had an underpayment collected through your code, your risk of being on a wrong code is meaningfully higher than average. Run a free check at TapTax before assuming everything is in order.

If You Also File Self Assessment

For readers who have income outside PAYE, whether from rental property, freelance work, dividends, or savings interest, your tax code may also include adjustments that are supposed to collect tax on that additional income across the year. These adjustments are calculated by HMRC based on your previous Self Assessment returns, again using estimated figures.

If your non-PAYE income changed significantly from one year to the next, your code may be over- or under-collecting on that additional income. This is a separate problem from a standard PAYE coding error, but it compounds the same underlying issue: your code reflects what HMRC thinks you earn, not what you actually earn.

The Is My Tax Code Correct? The Multiple Income Problem post covers this specific scenario in full.

Check It Now, Not in January

Tax codes can be corrected mid-year. If HMRC issues a new code, your employer updates their payroll and your deductions adjust from the next pay period. Waiting until January, or until you receive an end-of-year notice, means overpaying for longer and potentially losing track of which years are still within the four-year claim window.

The question at the top of this article was whether you have ever actively checked if your tax code is correct. If the honest answer is no, or not recently, that is not a personal failing. The system is not designed to draw your attention to its own errors. But the cost of those errors lands on you, not on HMRC.

Check your tax code now at TapTax. It is free, it takes minutes, and if something is wrong, finding out today means you stop losing money tomorrow.

File your MTD quarterly updates in minutes

TapTax imports your bank statements, categorises expenses automatically, and submits to HMRC with a tap. Free plan, no card required.

Start free