Pillar Guide · Updated June 2026
UK Tax Code Correction 2026/27: How to Fix a Wrong Tax Code and Reclaim Overpaid Tax
Your tax code tells your employer how much tax-free pay to give you. The standard code is 1257L, reflecting the GBP 12,570 Personal Allowance. A wrong code - an emergency code, a stray BR or 0T, or an outdated benefit - can mean you overpay or underpay tax through PAYE. This guide shows how to read your coding notice, identify a wrong code, update HMRC through your Personal Tax Account, get a revised code applied, and reclaim any tax you have overpaid.
Key tax code facts -- 2026/27
- Standard code: 1257L (Personal Allowance GBP 12,570)
- Emergency codes: shown with W1, M1 or X suffix
- BR code: all income taxed at 20%, no allowance
- 0T code: no allowance, taxed across the bands
- K code: deductions exceed the allowance (capped at 50% of pay)
- Fix it: Personal Tax Account on gov.uk, or phone HMRC
- Refund: cumulative code repays overpaid tax through your pay
Reading Your Tax Code
A typical tax code is a number followed by a letter, such as 1257L. The number is your tax-free allowance with the final digit removed: 1257 means GBP 12,570 of tax-free pay for the year, or about GBP 1,047.50 a month. The letter shows your situation - L is the basic Personal Allowance.
HMRC explains each code on a P2 PAYE coding notice, which lists your allowances and any deductions, such as company benefits or tax owed from an earlier year. You can view the same breakdown in your Personal Tax Account on gov.uk.
If your take-home pay drops unexpectedly, the first thing to check is whether the code on your payslip matches the one HMRC says you should have.
Common Wrong Codes
- BR - taxes everything at 20% with no allowance. Correct for a second job, wrong on your only job.
- 0T - no allowance, income taxed across the bands; common when an employer lacks details.
- D0 / D1 - taxes a source entirely at 40% or 45%.
- Two-job split error - the GBP 12,570 allowance not divided correctly between jobs.
- Stale benefit - a company car or medical cover still in your code after it ended.
Any of these can leave you paying too much. The fix is to give HMRC the correct information so it can reissue the code.
Emergency and Non-Cumulative Codes
Emergency codes appear with a W1, M1 or X suffix and are used when HMRC lacks full details, often after a new job started without a P45. They are non-cumulative: each pay period is taxed on its own slice of the GBP 12,570 allowance, ignoring earlier pay and tax in the year.
That isolation can produce over- or under-deduction. Once HMRC has your full details it issues a cumulative code, and any overpayment is corrected through your pay or, after the year ends, a P800.
How to Correct the Code
The fastest route is your Personal Tax Account on gov.uk. There you can:
- Check your current code and how it was calculated.
- Remove a benefit you no longer receive or a job that has ended.
- Add allowable expenses or update an income estimate.
You can also phone or write to HMRC. Once it has the right details, HMRC sends a revised code (a P6) to your employer or pension provider, who applies it on the next available pay run.
Reclaiming Overpaid Tax
If the corrected code is cumulative, it recalculates your tax for the whole year to date the next time you are paid. Any overpayment built up under the wrong code is repaid through that pay packet, which can give a visible jump in take-home pay.
If the correction comes too late in the year, or cannot be reconciled through the code, HMRC settles the difference after the year ends via a P800 calculation - paid by bank transfer if you claim online, or by cheque otherwise.
K Codes Explained
A K code applies when your deductions exceed your Personal Allowance - for example large taxable benefits or tax owed from a prior year. Instead of giving tax-free pay, it adds an amount to your taxable income: K500 adds GBP 5,000 to the income taxed.
A safeguard limits a K code to taking no more than 50% of your gross pay in any period. A K code is not automatically wrong, but if you do not recognise the deductions behind it, check the coding notice and query them with HMRC.
When a Wrong Code Means Underpaid Tax
Wrong codes cut both ways. A code that gives too much allowance - the full Personal Allowance applied to two jobs, or a benefit left out - causes underpaid tax that HMRC later recovers, often by adjusting next year's code, or through a Simple Assessment for larger sums.
Correcting the code early limits how much builds up. If you spot an underpayment, ask HMRC to update the code so the shortfall is spread rather than landing as one larger adjustment later.
Worked Examples
Example 1 - BR code on the only job. Liam started a job earning GBP 30,000 but, without a P45, was put on a BR code, taxing everything at 20% with no Personal Allowance.
- BR code tax: GBP 30,000 x 20% = GBP 6,000 over the year
- Correct 1257L tax: (GBP 30,000 - GBP 12,570) x 20% = GBP 3,486
- Annual overpayment under BR: GBP 6,000 - GBP 3,486 = GBP 2,514
- After correction to a cumulative 1257L, the overpaid tax to date is refunded through his pay
Liam updates his Personal Tax Account, HMRC issues 1257L, and his next payslip recovers the overpayment.
Example 2 - stale company car. Nadia's electric company car (4% BIK) was returned, but her code still deducted for it, lowering her tax-free pay.
- Benefit wrongly coded: car list price GBP 40,000 x 4% = GBP 1,600 deduction
- Effect: GBP 1,600 less tax-free pay, taxed at 20% = GBP 320 too much tax per year
- Nadia removes the benefit in her Personal Tax Account
- HMRC reissues a corrected code and refunds the excess through pay
Keeping benefits up to date in the Personal Tax Account prevents this kind of drift in the first place.