On this page9 sections
Your tax code is wrong right now. Not definitely, not provably yet, but statistically, there is a better-than-average chance. HMRC issued over 2.4 million incorrect PAYE tax codes in a single recent year, according to figures cited by the Low Incomes Tax Reform Group. Most of those errors were never queried. Most of those workers simply paid the wrong amount of tax, quietly, month after month, because the number printed on their payslip looked official enough not to question.
This post is for anyone who wants to go beyond "it looks about right" and actually verify that HMRC has got the maths correct on their behalf.
Why Checking Once Is Not Enough
Most articles about tax codes treat this as a one-time task. Find the code, confirm it matches the standard personal allowance, done. That framing misses the point almost entirely.
Your tax code is not a fixed label applied once and left alone. HMRC adjusts it dynamically throughout the year based on information fed through the Real Time Information (RTI) system by your employer, through your own Self Assessment returns if you file one, and through automated estimates HMRC makes when it thinks your circumstances have changed. Each of those data inputs is a potential error.
- PAYE Tax Code
- A code, typically a number followed by a letter (e.g. 1257L), issued by HMRC to your employer to indicate how much tax-free pay you are entitled to in the current tax year. Your employer uses it to calculate exactly how much income tax to deduct from each payslip. An incorrect code means incorrect deductions, every single pay period until it is fixed.
The practical consequence is that the correct question is not "what is my tax code?" but "what is my tax code based on, and is that information still accurate?" Those are very different investigations.
How to Check Your Tax Code in Under Five Minutes covers the mechanics of finding the code itself. This post focuses on something harder: verifying the assumptions behind it.
The Three Most Common Sources of Error

1. Stale Income Estimates
HMRC often calculates adjustments to your tax code using income figures from a previous tax year, or from an estimate it has made based on incomplete current-year data. If your income has changed, the adjustment baked into your code may be wrong.
A common example: you earned a bonus in the 2023/24 tax year. HMRC saw this, assumed it would recur, and reduced your tax-free allowance in 2024/25 to collect extra tax in advance. The bonus never came. You paid extra tax on income you never received.
To check this, log into your Personal Tax Account and navigate to "Check your tax code". Look for any income adjustments listed under your code breakdown. If there is a deduction for "other income" or a benefit-in-kind estimate, verify where that figure came from. If it is out of date, you can challenge it directly through the same portal.
2. Benefits-in-Kind That No Longer Apply
If you receive, or used to receive, a benefit from your employer such as a company car, private medical insurance, or a gym membership, your tax code will be reduced to collect the tax owed on that benefit through PAYE rather than a separate bill.
The problem is that when a benefit ends, the notification does not always reach HMRC promptly. Your employer may update their payroll records, but the P11D data that informs HMRC often lags by months. In the interim, you continue paying tax on a benefit you no longer have.
If you have lost a company car or any taxable benefit since your last P60, check whether your current tax code still contains a benefits deduction. The breakdown is visible in your Personal Tax Account. If a deduction is listed for a benefit you no longer receive, contact HMRC directly via the income tax helpline on 0300 200 3300 to request an immediate correction.
3. Multiple Employments Handled Incorrectly
If you work two jobs, HMRC is meant to split your personal allowance appropriately between them. In practice, this frequently goes wrong. Common outcomes include:
- All of your personal allowance allocated to one employer, leaving you taxed at 20% on every pound earned at the second job from the first pound
- Your personal allowance split in a way that bears no relation to your actual earnings at each job
- Emergency tax codes (0T or BR) applied to a second income and never corrected
If you hold more than one PAYE employment, check the tax code issued for each one separately. A BR code means basic rate tax is deducted on every pound with no personal allowance applied. That is correct if all your allowance is fully used by another job, but you should verify that this is genuinely the case by checking the tax code on your main employment and confirming its allowance equals your full personal allowance (currently £12,570, giving a code of 1257L).
Our tax calculator for multiple incomes can help you sense-check whether the split looks roughly right.
2.4m
Estimated incorrect PAYE codes issued in recent years, per LITRG data
£600
Typical annual overpayment for a basic-rate taxpayer on a wrong code
4 years
Maximum period HMRC allows for a tax code refund claim
Reading the Breakdown, Not Just the Code
The code itself, "1257L" for example, tells you almost nothing useful on its own. What you actually need to examine is the breakdown that generates it, which is the list of allowances added and deductions subtracted to arrive at the final tax-free amount.
Here is how to find that breakdown:
- Go to gov.uk/personal-tax-account and sign in with your Government Gateway credentials
- Select "Check your Income Tax" or "Check your tax code"
- Look for the itemised breakdown below the headline code
You should see your personal allowance (£12,570 for most people in 2024/25), any additions (for example, professional subscriptions or flat-rate expenses your employer has claimed for you), and any deductions (benefits in kind, underpaid tax from previous years being collected, or income from other sources).
Every single line deserves scrutiny. Ask yourself:
- Is the personal allowance figure correct? It reduces above £100,000 income; if you earn near that threshold, check the adjusted net income calculation carefully.
- Does the underpaid tax deduction reflect something real? If you previously underpaid tax, HMRC may be collecting it through your code. Confirm the amount matches what you actually owe.
- Are any additions correctly applied? Flat-rate expenses for specific occupations (uniform upkeep, tools, professional fees) can legitimately increase your tax-free amount, but they need to be claimed first. Many employees miss these entirely.
The April Trap: When New Year Codes Bake In Old Errors
The period between January and late March is the highest-risk window for a tax code error to take root for the entire coming year. HMRC calculates and issues new codes for the following April ahead of time, often using information that is months out of date.
If your circumstances changed after HMRC froze the data for its calculations, your new tax year code will be wrong from day one. It will then remain wrong for the entire year unless you actively challenge it.
This is not a hypothetical inconvenience. A basic-rate taxpayer on an incorrect code that over-collects by £50 per month will pay £600 too much across the year. That money is not lost permanently, HMRC will eventually issue a P800 reconciliation letter and refund the difference, but that process can take until November or later. You will have lent HMRC £600 interest-free for most of a year.
The fix is straightforward: check your new tax code when the April payslip arrives, not in December. If you spot a discrepancy, you can check your tax code is correct and challenge it before the error compounds.
For workers who changed jobs close to a new tax year, the risk is even higher. A new employer starting payroll in March or April may receive a code based on incomplete year-to-date data. See How to Check My Tax Code After a Job Change for the specific checks that apply in that situation.
When HMRC Uses an Emergency Code

An emergency code is HMRC's way of saying "we do not have enough information about this person, so we will tax them at a standard rate until we do." The most common emergency codes are:
- 1257L W1 or 1257L M1: The allowance is applied on a week-by-week or month-by-month basis rather than cumulatively, meaning you cannot benefit from unused allowance from earlier in the year
- 0T: No personal allowance applied at all
- BR: All income taxed at basic rate (20%), no allowance
Emergency codes are supposed to be temporary. They should be replaced by a correct cumulative code once HMRC receives the relevant information. In reality, many people remain on emergency codes for months, particularly if a new employer does not submit full RTI data promptly.
If your payslip shows any of the codes above and you have been in your current job for more than six weeks, contact HMRC immediately. Do not wait for it to resolve itself. It may not.
People also ask
How do I know if my tax code is correct for this tax year?
Log into your Personal Tax Account at gov.uk and check the breakdown behind your tax code, not just the code itself. Verify that every line, personal allowance, deductions, and additions, reflects your actual current circumstances. If anything looks unfamiliar or out of date, contact HMRC to query it.
Can I get a refund if my tax code was wrong?
Yes. If your tax code over-collected tax, HMRC should automatically issue a P800 refund letter after the tax year ends. However, you can also claim proactively through your Personal Tax Account or by contacting HMRC directly. You have up to four years to claim a refund for a tax code error.
What happens if I do not correct a wrong tax code?
The wrong code continues to apply until HMRC or your employer changes it. If you are overpaying, the money accumulates until HMRC reconciles it at year end, which can take until late autumn. If you are underpaying, HMRC will eventually bill you for the shortfall, usually by adjusting a future tax code.
Does my employer know if my tax code is wrong?
No. Your employer simply applies whatever code HMRC instructs them to use. They have no visibility into whether that code is accurate, and they are not responsible for verifying it. The responsibility for checking accuracy sits entirely with you and HMRC.
Child Benefit and the High Income Charge Adjustment
If you or your partner receives Child Benefit and either of you earns over £60,000 (from April 2024), you may be subject to the High Income Child Benefit Charge. HMRC can collect this charge by reducing your tax code, effectively increasing the amount of tax taken through PAYE each month.
This adjustment is easily misapplied. Common errors include:
- Applying the charge to the wrong person in the household (it should apply to the higher earner)
- Using an incorrect income estimate, particularly if your salary fluctuates or you have recently had a pay change
- Applying a charge when Child Benefit has already been stopped to avoid the liability
If you receive Child Benefit and earn near or above the £60,000 threshold, check your tax code breakdown explicitly for this adjustment and verify the income figure HMRC is using. Our child benefit tax calculator can help you sense-check what the charge should actually be.
What to Do When the Code Is Wrong
Finding an error is the straightforward part. Getting it corrected quickly is where things become frustratingly slow.
Your fastest options, in order of speed:
- Update through your Personal Tax Account: For simple corrections such as removing a benefit that no longer applies, or updating your income estimate, the online account allows self-service changes that can update your code within days
- Call the income tax helpline: 0300 200 3300, Monday to Friday. Have your National Insurance number and the specific error ready to describe. Ask for a revised code to be issued immediately rather than waiting for the automated cycle
- Write to HMRC: Slowest option, but creates a paper trail. Use PAYE and Self Assessment, HM Revenue and Customs, BX9 1AS
In all cases, note the date you reported the error. If your employer continues to apply the wrong code after HMRC has confirmed a correction was issued, the responsibility for reimbursing overpaid tax shifts to HMRC rather than your employer.
For a deeper look at what HMRC's own online checker does and does not show you, Check Tax Code Online: What HMRC Shows vs Reality covers the gaps in the system frankly.
The Habit That Actually Protects You

Tax codes are not a once-a-year problem. They change whenever HMRC receives new data, whenever your employer updates your payroll information, and whenever legislation shifts the standard personal allowance.
The practical protection is a quarterly habit: check your payslip tax code against your Personal Tax Account breakdown four times a year. April (when new codes take effect), July (after P11D benefits data flows through), October (mid-year check), and January (ahead of the following April's calculations). Twenty minutes a year in total. The alternative is lending HMRC several hundred pounds interest-free and hoping they notice.
If you want a definitive, structured check, verify whether your tax code is correct right now at TapTax before the current year gets any further away from April.
The 2.4 million people who received wrong codes last year did not know they were in that group. The only way to be sure you are not is to check.
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 freeFrequently asked questions
How often does HMRC change your tax code without telling you?
HMRC can and does update tax codes throughout the year whenever it receives new data from employers, benefit providers, or your own tax return. There is no requirement to notify you in advance, though HMRC should send a P2 coding notice when a significant change is made. Checking your payslip and Personal Tax Account quarterly is the only reliable way to catch unannounced changes.
Can a wrong tax code affect my pension contributions?
Indirectly, yes. If your tax code over-deducts income tax, your take-home pay falls, which can affect affordability for voluntary pension contributions. Additionally, salary sacrifice pension arrangements reduce your taxable pay, and if HMRC is unaware of these arrangements, it may apply the wrong income estimate in your code. Always check that HMRC's income figure in your tax code reflects your actual pensionable pay after any sacrifice arrangements.
What is the difference between a cumulative and a non-cumulative tax code?
A cumulative tax code (the standard type, shown without W1 or M1 suffix) takes into account all your pay and tax deductions since the start of the tax year, allowing unused allowance from earlier months to reduce your tax bill later. A non-cumulative code (marked W1 for weekly or M1 for monthly) treats each pay period in isolation, meaning you cannot benefit from allowance you did not use in April or May. Non-cumulative codes are typically used when HMRC lacks full information and should be replaced with a cumulative code once your records are confirmed.
How far back can I claim a tax refund from a wrong tax code?
You have four tax years to claim a refund resulting from a tax code error. For example, in the 2024/25 tax year you can claim back to 2020/21. Claims for earlier years are time-barred. You can submit a claim through your Personal Tax Account, by completing form R40, or by writing to HMRC directly.
Will HMRC automatically fix a wrong tax code at year end?
HMRC runs an annual PAYE reconciliation process after the tax year closes, issuing P800 letters to people who have overpaid or underpaid. However, this process is not infallible and can take until November or later. More importantly, it does not fix the problem during the year. If you identify a wrong code mid-year, challenging it immediately stops further over-deduction rather than waiting for a lump-sum refund months later.