Check Your Tax Code Before April or Pay the Price

April arrives whether you are ready or not. If you have not taken ten minutes to check your tax code before the new tax year begins, you are handing HMRC a decision it is statistically quite likely to get wrong.

This is not a guide to checking your code in five minutes (that is already covered here). This is about the timing of that check, why the weeks before 6 April are the single most valuable window in the calendar year, and what happens to people who miss it.

Tax Code

A combination of letters and numbers sent by HMRC to your employer that tells them how much income tax to deduct from your pay each month. The most common is 1257L, reflecting the standard Personal Allowance of £12,570 for 2024/25. An incorrect code means you pay too much or too little tax automatically, without any obvious error on your payslip.

Why April Is the Reset That Catches People Out

Every year, typically in February or March, HMRC issues P9 coding notices to employers. These tell payroll departments what tax code to use for each employee from 6 April onwards. It is an automated process at scale, and that scale is precisely the problem.

HMRC processes coding notices for over 40 million PAYE records. The data feeding that process comes from a patchwork of sources: your previous year's Self Assessment (if you have one), employer returns, pension providers, benefits in kind notifications, and information that may or may not have been updated since the last time you moved house, changed jobs, or started receiving a company car. Any stale or mismatched data becomes your new tax code on 6 April, by default, until someone notices.

The cruel irony is that HMRC does not have a legal obligation to tell you your code has changed in plain language. You may receive a generic P2 coding notice in the post, written in HMRC's characteristically impenetrable style, but many people mistake it for junk mail or simply do not understand what it is telling them.

What a Wrong Code Actually Costs on a Real Salary

Abstract warnings about tax code errors are easy to ignore. So consider Marcus, a site manager in Bristol earning £58,000 a year. His tax code at the end of last year was 1257L, reflecting the standard Personal Allowance. In January, Marcus started receiving a modest company van benefit, valued at £3,600 for the tax year. His employer reported this to HMRC, as required.

HMRC's system reduced Marcus's Personal Allowance by £3,600 to account for the benefit, which is correct in principle. But the coding notice it issued also included an estimated underpayment of tax from two years ago, something Marcus resolved via Self Assessment but which HMRC's database had not yet cleared. The result: a tax code of 893L instead of 921L (the correct code after accounting only for the van benefit).

The difference between 893L and 921L is £280 in annual Personal Allowance. At the basic rate of 20 percent, that is £56 a year. Small, yes. But if Marcus also had a pension contribution adjustment applied incorrectly, or if his estimated earnings were inflated, that figure compounds. On a coding error of 300 points (not uncommon after a job change or benefit notification), the annual overpayment is £600 at basic rate, £1,200 at higher rate.

Marcus will get that money back eventually, either through an automatic P800 reconciliation after the tax year ends, or by contacting HMRC directly. But he will wait months, with no interest paid on what HMRC held, and no apology forthcoming.

If Marcus had checked his tax code before 6 April, spotted the discrepancy, and called HMRC to correct it, he would have lost nothing.

The Three Situations That Corrupt a Code Over Winter

Most tax code errors do not appear from nowhere. They have a cause, usually something that happened between October and February that HMRC's automated systems processed incompletely or incorrectly. Here are the three most common triggers in the months leading up to April.

A New Job, Promotion, or Pay Rise in the Final Quarter

If you changed jobs between October and February, your new employer may have received an emergency tax code for you initially (typically 1257L W1/M1, meaning non-cumulative) and your actual code only arrived later. HMRC sometimes fails to update the following year's code correctly if the transition was complex. The same applies to a significant pay rise that pushed you into or out of the higher-rate threshold, as your estimated income for the following year needs to reflect the new salary.

If your circumstances changed because of employment, the How to Check My Tax Code After a Job Change post covers the specifics in more detail.

Benefits in Kind Added or Removed

Private medical insurance, company cars, interest-free loans above £10,000, and living accommodation provided by employers all reduce your Personal Allowance via your tax code. If your employer added, changed, or removed a benefit in kind during the year, the knock-on effect to your code for the following April is only as accurate as the P11D or payrolled benefits data HMRC received. Discrepancies here are extraordinarily common.

Underpayment Collected via Code

HMRC frequently uses tax codes to collect underpayments from previous years. The maximum it can collect this way in a single year is capped (generally £3,000 unless you have agreed otherwise), but the figure it uses may be estimated, outdated, or already settled. If you see an unexplained reduction in your allowance, an underpayment collection is a likely culprit. Check your P2 notice, or log into your Personal Tax Account, and query it before the new year begins.

For the fuller picture on what HMRC gets wrong at year end, see Tax Code Correct? What HMRC Gets Wrong at Year End.

Reading the Code on Your Payslip Right Now

You do not need to wait for a letter. Your current tax code is printed on every payslip. Here is what the most common structures mean.

1257L: Standard code, full Personal Allowance, nothing unusual affecting your tax position. Most employees should be on this unless something has changed.

BR: Basic Rate, meaning all your income from this employer is taxed at 20 percent with no Personal Allowance applied. Correct if this is a second job and you use your full allowance elsewhere. Wrong if it is your only job.

D0 or D1: All income taxed at 40 percent or 45 percent respectively, with no allowance. Again, usually appropriate only for additional income sources where allowance is fully used elsewhere.

K codes: A negative allowance, meaning your untaxed income or benefits exceed your Personal Allowance. These are legitimate but frequently miscalculated and deserve extra scrutiny.

W1 or M1 suffix: Emergency or non-cumulative basis. Tax is calculated on each pay period in isolation rather than cumulatively across the year. This often results in overpayment and should not persist beyond your first month in a new job.

If anything on that list does not match your situation, check your tax code now before 6 April locks in twelve months of incorrect deductions.

People also ask

When is the best time to check your tax code?

The weeks before 6 April are the most valuable window. HMRC issues new coding notices to employers in February and March for the upcoming tax year. Spotting an error before the year starts means your employer uses the correct code from day one, avoiding months of incorrect deductions and a wait for a refund.

What happens if my tax code is wrong for a full year?

If you overpay, HMRC should issue a P800 refund notice after the tax year ends, typically between June and October. If you underpay, HMRC may collect the balance via your code the following year or request payment directly. Neither outcome is immediate, and no interest is paid on amounts HMRC held incorrectly.

Can I change my tax code myself?

You cannot change it directly, but you can tell HMRC it is wrong. Log in to your Personal Tax Account at gov.uk, check what information HMRC holds about your income and benefits, and contact HMRC if anything is incorrect. Your employer then receives an updated coding notice, usually within a few weeks.

Does checking my tax code affect my employer or payslip immediately?

Not immediately. Once HMRC issues a corrected coding notice, your employer should apply the new code from the next available payroll run. It is worth telling your payroll department to expect the change so there is no delay.

What HMRC's Personal Tax Account Shows and What It Misses

Logging into your HMRC Personal Tax Account at gov.uk/personal-tax-account is the official way to see your current tax code and the allowances or deductions that make it up. For most people in straightforward circumstances, it works. You can see the numbers, identify obvious errors, and update details like your address or employment status.

But the Personal Tax Account is a view of what HMRC believes to be true, not necessarily what is true. If your employer submitted incorrect benefit figures, or if a P45 from a previous job was processed late, the account will reflect the wrong data confidently and without any warning flag. The system does not know it is wrong.

This is why the earlier post Check Tax Code Online: What HMRC Shows vs Reality makes the point that trusting the Personal Tax Account uncritically is its own kind of risk. You need to cross-reference what HMRC shows against your actual circumstances: your real income from all sources, your actual benefits, and any pension contributions you make. A mismatch between those two things is a tax code error waiting to happen.

For employees with income from more than one source (a second job, rental income, or savings interest above the Personal Savings Allowance), the complexity multiplies. Is My Tax Code Correct? The Multiple Income Problem covers that specific scenario in depth.

The Cost of Waiting Until After April

If you do nothing before 6 April and your code turns out to be wrong, you have not lost the money permanently. HMRC reconciles PAYE records after each tax year. If you overpaid, you will typically receive a P800 tax calculation between June and October, with a refund either sent automatically or accessible via your Personal Tax Account.

But consider what that actually means in practice. Say you overpay by £80 a month from April because your code is wrong. By the time you receive the P800 in September, you have handed HMRC £400 that was rightfully yours. HMRC pays no interest on that money. You had less cash in your pocket every month from April to September, for an administrative error that was not your fault and that a ten-minute check in March could have prevented.

For higher earners, the numbers are proportionally larger. On a salary of £75,000 with a coding error of 500 points (reflecting, say, an incorrectly applied benefit in kind), the monthly overpayment at the higher rate of 40 percent is £167. Over six months, that is £1,000 sitting with HMRC for free.

If you have not already, use our free tool at /check-my-tax-code to confirm what you should be on before the new tax year begins.

One Action That Takes Less Time Than a Tea Break

Opening this article meant you already knew something felt off, or that checking your tax code was overdue. Here is the simplest version of what to do next.

1. Find your most recent payslip and note the tax code printed on it.
2. Visit /check-my-tax-code and enter your details.
3. If the code does not match your actual circumstances (income, benefits, pension contributions), contact HMRC on 0300 200 3300 or update your details via gov.uk/personal-tax-account.
4. Let your employer's payroll department know a new coding notice is coming.

Do this before 6 April and the correction applies from the first day of the new tax year. Do it in July and you have already overpaid for three months.

The tax year waits for nobody. But a wrong code, caught before April, costs you nothing at all.

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