Tax Code Checker UK 2026/27: How to Check YoursWhat Is a P11D? UK Benefits in Kind Explained for 2026/27State Pension at 66 UK 2026: What You Actually GetTax Rebate UK 2026: The Refund HMRC Won't Tell You AboutRoyal London Pension Review 2026: Mutual DifferenceWhat Is a P45? The UK Form Your Employer Owes YouAegon Pension Review 2026: After the Standard Life DealStandard Life Pension Review 2026: Stay, Transfer or Consolidate?Best Fixed Cash ISA Rates UK 2026: Should You Even Fix?

Tax Code Checker UK 2026/27: How to Check Yours

1.5 million UK workers are on the wrong tax code right now. Most never check. Here is how to pull yours from HMRC in five minutes - and the four codes that mean you are overpaying every payslip.

Michael McGettrick 13 June 2026 11 min read
Infographics
Cite this article
Freedom Isn't Free (2026) Tax Code Checker UK 2026/27: How to Check Yours. Available at: https://freedomisntfree.co.uk/articles/tax-code-checker-uk (Accessed: 13 June 2026).

Italicise the article title in your bibliography. Accessed date set to today.

TLDR

  • The fastest way to check your tax code is the HMRC personal tax account at gov.uk/personal-tax-account. The code on your latest payslip is what your employer is using; the code in the HMRC portal is what HMRC currently holds.
  • The standard 2026/27 tax code is 1257L. Anything else has a specific reason behind it - and an HMRC arithmetic that can be wrong.
  • Four codes routinely overcharge you: BR (basic-rate on every penny), 0T (no allowance applied), W1 / M1 / X (emergency cumulative-disabled), and K-codes calculated against a stale benefit-in-kind estimate.
  • Wrong code refunds run on the four-year backstop. The 2022/23 window closes on 5 April 2027 - after that the overpayment is permanently HMRC's.

How to read your UK tax code 2026/27

CodeWhat it meansAction
1257LStandard - full £12,570 allowance applied through PAYENo action - this is the default
BRAll income taxed at 20% basic rateConfirm you have a separate code on your main job
0TNo personal allowance applied at allUsually wrong on a single PAYE job - call HMRC
1257L W1 / M1 / XEmergency code - each period taxed in isolationHMRC should fix after the first full month of RTI
K [number]You owe more than your allowance coversCheck the underlying BIK or pension underpayment is real
S1257L / C1257LScottish / Welsh standard allowanceCorrect for residents of Scotland / Wales
NTNo tax deducted at allRare - usually a specific HMRC instruction

Source: HMRC PAYE manuals, gov.uk tax codes guidance, 2026/27 tax year.

Tax Code Checker UK 2026/27: How to Check Yours

A tax code checker is the single most useful five minutes of admin a UK worker can do this tax year. The Office for Tax Simplification's last published estimate was that around one in twenty PAYE workers carries a wrong tax code at any time, with the median overpayment running into the hundreds of pounds. On a working population of 30 million PAYE earners, that is in the region of 1.5 million wrong codes operating right now, and the only person who finds them is you.

This article walks through how to pull your live tax code from HMRC, how to decode what you find, the four codes that quietly overcharge you, and what to do if the number is wrong. It is the practical companion to tax code 1257L explained and feeds the tax rebate UK guide.

The fastest tax code check (five minutes)

Two routes. Use both. The numbers should match.

Route 1: Your latest payslip. Look for a field labelled "Tax code". Every UK payslip is legally required to show it. This is the code your employer is operating right now and is the figure that controls how much tax is coming out of your salary this month.

Route 2: HMRC's personal tax account. Sign in at gov.uk/personal-tax-account. Sign-in uses GOV.UK One Login. You will need a passport, a driving licence, or a recent P60 to verify on first use. Once in, the front page shows the code HMRC has on file for you, the code's effective date, and the underlying calculation.

If the payslip code and the HMRC code differ, your employer is running an out-of-date instruction. This happens routinely after a tax-code change letter (P2) that HMRC issues to you and to your employer separately. The employer is supposed to apply it by the next pay period; some payroll systems take a cycle longer.

If they match, the next question is whether the code is right. That is the bit nobody tells you how to check.

How to read your tax code

Every UK tax code is a number plus a suffix letter. The number is your tax-free allowance for the year with the last digit dropped. The letter is the category HMRC has sorted you into.

For 2026/27 the standard tax code is 1257L, which translates to a £12,570 personal allowance applied through PAYE with no special circumstances. That has been the default since April 2021 because the personal allowance is frozen until at least April 2028 under the threshold-freeze extension confirmed in the 2022 Autumn Statement.

The numbers move when HMRC believes your tax-free allowance is different from the default. They add things (marriage allowance you received, work-related expenses) and they subtract things (benefits in kind your employer reports on a P11D, pension underpayments being collected through PAYE). Whatever the net allowance is gets divided by 10 and printed on your payslip.

The suffix letter is the diagnostic. Reading the Suffix Letter Guide on gov.uk in full is fine if you have time. The condensed version that covers 95% of UK workers:

SuffixWhat it means in plain English
LStandard personal allowance, no adjustments. The default for most PAYE workers.
MYou received marriage allowance from your spouse (10% of their allowance).
NYou gave marriage allowance to your spouse (10% of yours).
THMRC is doing other calculations on your code - usually because you have crossed the £100,000 personal-allowance-taper threshold.
0TNo personal allowance at all is being applied.
BRAll income from this source taxed at 20% (basic rate) with no allowance.
D0All income from this source taxed at 40% (higher rate).
D1All income from this source taxed at 45% (additional rate).
NTNo tax deducted at all (rare; usually a specific HMRC instruction).
KPrefix code - your taxable extras exceed your allowance, so PAYE deducts more than the headline figure.
S prefixScottish income tax rates apply.
C prefixWelsh (Cymru) income tax rates apply.
W1 / M1 / XEmergency cumulative-disabled code; each pay period is treated in isolation.

If you are a single-job PAYE worker in England, Wales, or Northern Ireland on a salary under £100,000, your code should be 1257L. Anything else is a question worth asking.

The four codes that quietly overcharge you

This is where wrong codes do most of their damage. Each of these is HMRC's default when it does not have full information, and each of them taxes you too hard until corrected.

BR (basic rate on everything)

A BR code taxes every penny of income from that source at 20%. It is correct for a second job where the personal allowance is already used up on the main job. It is wrong, and expensive, if it is on your only job.

A common path to a wrong BR code: you started a new job mid-tax-year, your old employer sent the P45 late or not at all, the new employer applied the starter checklist without Parts 2 and 3 of the P45 and ticked statement B or C, and HMRC fell back to BR rather than 1257L. The reclaim route is the Self Assessment tax return or a quick HMRC online correction once you spot it.

0T (no allowance at all)

A 0T code removes your entire personal allowance. The maths is brutal: someone earning £40,000 a year goes from a £5,486 income tax bill on 1257L to a £8,000 income tax bill on 0T, an overpayment of £2,514 per year if it runs full term.

0T codes typically come from a starter checklist with no statement ticked, a P45 that HMRC could not match against an existing record, or a misapplied HMRC manual instruction. They are the highest-priority code to challenge.

Emergency codes (W1, M1, X)

Emergency codes are not standalone - they are flagged onto a normal code (1257L W1 means 1257L applied non-cumulatively). The PAYE system normally tracks your year-to-date earnings and tax to keep the cumulative balance right. The emergency flag turns that off: each pay period is treated in isolation, no catch-up for under or overpayments earlier in the year.

For most workers the emergency code self-corrects within one or two pay cycles once HMRC has a full set of RTI submissions from the employer. Where it does not - long gaps between jobs, mid-year switches between employer and self-employed, pension drawdown lump sums - the emergency code can run for months and rack up an overpayment that only resolves at the year-end reconciliation.

K codes

A K code prefix means HMRC has calculated that your taxable extras (benefits in kind, untaxed savings income, state pension, pension underpayments being collected through PAYE) are larger than your personal allowance. The K number is how much extra to tax. It is added to your gross pay before the band calculation rather than subtracted.

K codes are not necessarily wrong. But the underlying figure - usually the P11D benefit-in-kind estimate or a coding adjustment for last year's underpayment - is set in advance and rarely revisited. If you changed cars, dropped a benefit, or stopped having underpayments collected at source, the K-code estimate can be a year or more out of date. Worth a check.

How to challenge a wrong code

Three routes, in increasing severity.

Online via the personal tax account. Most simple cases can be fixed at gov.uk by updating your employment details, your income estimate, or your declared benefits. HMRC reissues a P2 coding notice and the employer updates within a pay cycle.

By phone to HMRC. 0300 200 3300 for individuals. Have your National Insurance number, your latest payslip, and your P60 for the prior year ready. The wait times are long; the conversation is short.

By letter if there is a refund involved for a closed tax year. HMRC requires a written claim for tax-year corrections more than one year past current. The address is HM Revenue and Customs, Pay As You Earn and Self Assessment, BX9 1AS. Quote the tax year, your NI number, the wrong code, the correct code, and the underlying reason.

For any prior-year refund, remember the four-year backstop. You can reclaim back to and including the tax year ending 5 April 2023. After 5 April 2027, the 2022/23 window closes and any wrong-code overpayment that year is permanently HMRC's. The tax rebate UK guide covers the claim mechanics in full.

What if the code is right but the bill still feels too high

Sometimes the code is correct and the tax bill is still painful. That is the 60% tax trap, the frozen UK tax thresholds, and the dividend or savings interest bumping you up a band. None of those are tax-code errors. They are the rules working as designed.

The honest framing: the tax code is the mechanical settlement of HMRC's view of what you should be paying. The amount itself is set by the bands in UK tax brackets 2026/27. A correct tax code on a frozen-threshold band is still a tax rise - it is just the tax rise the government intended rather than the tax rise an arithmetic mistake created. Both deserve attention. Only one of them can be fixed by a five-minute call to HMRC.

Frequently Asked Questions

How can I check my tax code right now?

Log into your HMRC personal tax account at gov.uk/personal-tax-account. The current tax code is shown on the front page along with the effective date. Cross-reference against the "Tax code" field on your latest payslip. If the two match and the code is 1257L (England, Wales, NI single PAYE job under £100,000 income), you are on the standard 2026/27 code and there is nothing to fix.

What is the standard UK tax code for 2026/27?

The standard code is 1257L. The 1257 is the £12,570 personal allowance with the last digit dropped; the L is the suffix for "standard personal allowance, no adjustments". This has been the default since April 2021 because the threshold-freeze policy held the personal allowance at £12,570 through to at least April 2028.

What does emergency tax code mean?

An emergency code is a normal tax code (typically 1257L) with a W1, M1, or X flag attached. The flag tells PAYE to treat each pay period in isolation rather than cumulatively across the year. HMRC sets it when it does not have enough information to operate the code cumulatively, usually after a job change without a P45, a pension drawdown lump sum, or a self-employment-to-employment transition. The emergency flag normally drops off within one or two pay cycles once HMRC has a full set of Real Time Information submissions from your employer.

How do I fix a wrong tax code?

The route depends on the year. For the current tax year, log into your HMRC personal tax account and update your employment, income, or benefit details directly. HMRC reissues a coding notice (P2) and your employer applies the new code in the next pay cycle. For closed tax years up to four years back, you can claim the refund directly via the same portal. For older closed years - more than four years back - the overpayment is permanently HMRC's under Schedule 1AB of the Taxes Management Act 1970.

Why is my tax code different from my partner's?

Several legitimate reasons. The most common: one of you has claimed marriage allowance and has the M suffix while the other has the N suffix. Other reasons: different employer benefit-in-kind reporting, different Scottish/Welsh residence (S or C prefix), different second-job arrangements, one of you is into the £100,000 personal-allowance taper, or one of you has an underpayment being collected through PAYE (K code). Two people in identical-looking jobs can quite legitimately end the tax year on different codes.

Will HMRC tell me if my tax code is wrong?

In theory the year-end PAYE reconciliation catches it and triggers a P800 tax calculation letter. In practice this works reliably for clean PAYE years - same job, same code, no other income - and misses a meaningful share of mid-year movers, emergency-code cases, and pension drawdown cases. HMRC's own published National Audit Office reviews have flagged unreconciled employment income running into significant volumes each year. The five-minute personal-tax-account check is faster and more reliable than waiting for the post.

What is a K code and should I worry?

A K-code prefix means HMRC has calculated that your taxable extras - benefits in kind from a P11D, untaxed savings interest, state pension, a coding adjustment to collect last year's underpayment - are larger than your personal allowance. The K number is added to your gross pay before the band calculation rather than subtracted. K codes are not necessarily wrong; the underlying numbers may all be correct. They are worth a closer look because the figures HMRC uses are often a year or more old: a company-car benefit calculation from when you had a different car, a savings-interest estimate from when rates were lower, an underpayment that has already been collected. Each of these can leave you on a K code that is overcharging.

Further Reading:

I Will Teach You To Be Rich - Ramit Sethi - The classic playbook for the kind of fifteen-minute admin tasks a tax-code check is. The chapters on automating finances and reclaiming what you are owed fit beside this article cleanly. (Affiliate link - we may earn a small commission at no extra cost to you.)


This article is general educational content, not financial or tax advice. UK tax codes and the underlying allowances can change between tax years and at any Budget. Verify any specific rate, deadline, or coding-notice instruction against gov.uk before acting on it, and consider speaking to an accountant for material refund claims.

Enjoying the content?

If this site has been useful, a coffee goes a long way.

Buy us a coffee