Verify Tax Code Accuracy UK: A Forensic Checklist

Most people glance at their tax code, shrug, and assume HMRC got it right. That assumption costs UK taxpayers an estimated £800 million in overpaid tax every single year.

Verifying your tax code accuracy in the UK is not a once-a-decade chore for the unusually diligent. It is a basic financial health check that takes less time than ordering a takeaway, and it can put real money back in your pocket. This article gives you a forensic checklist to work through, line by line, so you can confirm whether HMRC's numbers stack up or whether you have been quietly funding the Treasury's contingency fund.

Why HMRC's Starting Point Is Rarely Accurate

HMRC does not have a live feed into your life. It pieces your tax code together from employer returns, pension data, benefit-in-kind notifications, and whatever you told it last time. When any of those inputs change, and you do not tell HMRC, the code drifts.

The practical result: according to HMRC's own annual report, the department issues over 40 million PAYE coding notices each year, and the Low Incomes Tax Reform Group estimates that a significant proportion contain errors. These are not edge cases. They are a structural feature of a system that runs on stale data and educated guesses.

For someone earning £50,000, a tax code that is wrong by just one allowance band can mean overpaying by £200 to £400 annually. At £70,000, with a benefit-in-kind incorrectly logged, that gap widens further. The money does not disappear; it sits with HMRC until you claim it back. But HMRC will not chase you to do so.

The Forensic Checklist: Eight Areas to Examine

Work through each section below. You will need your current payslip, your most recent P60, and access to your HMRC Personal Tax Account (available at gov.uk). Better still, run your code through our free tax code checker first so you have a baseline before you start digging.

1. Confirm the Basic Number Matches Your Personal Allowance

For the 2024/25 tax year, the standard Personal Allowance is £12,570. Multiply the numeric part of your tax code by ten. If your code is 1257L, that gives you £12,570 -- correct.

If the number is lower than 1257, HMRC believes you owe it something: an underpayment from a previous year being collected, a benefit in kind, untaxed income, or a restriction because your gross income exceeds £100,000. If it is higher, you may have had an allowance added, such as a Marriage Allowance transfer or a flat-rate expense claim for your job.

Any deviation needs a reason. If you cannot identify the reason from your HMRC Personal Tax Account, that is your first red flag.

2. Check Whether Previous Year Underpayments Are Still Being Collected

HMRC sometimes discovers an underpayment -- say, from a year when your employer used the wrong code -- and rather than issuing a bill, quietly adjusts your current year code to claw it back. This is entirely legal under the PAYE system and is referenced in your coding notice as a "Simple Assessment" or an adjustment for "underpaid tax."

The problem: HMRC's estimate of the underpayment is occasionally wrong. It may be based on income figures that have since been corrected, or on a Self Assessment return that was later amended. Check whether your code includes any such adjustment and, if so, verify the underlying figure against your P60 and previous tax returns.

3. Verify Benefits in Kind Are Correctly Valued

If your employer provides a company car, private medical insurance, a season ticket loan, or any other benefit in kind, HMRC adds its estimated taxable value to your code. That reduces your tax-free allowance accordingly.

Company car figures are recalculated annually based on CO2 emissions and list price, and the taxable percentage changes each April. If you changed your car, handed it back, or your employer changed the terms, HMRC may still be working from last year's (or the year before's) figures. Private medical insurance premiums also rise annually; if HMRC is using the figure your employer reported two years ago, the deduction in your code could be too high or too low.

Cross-reference the benefit values in your code with what your employer has actually provided. Your P11D (the annual form your employer files to declare your benefits) is the authoritative source. If you have not seen your P11D, you are entitled to a copy.

For a deep dive into how benefit-in-kind errors stack up, see our post on company car tax codes and private medical insurance tax code errors.

4. Confirm Your Marriage Allowance Transfer Is Still Active

If you or your spouse transferred part of the Personal Allowance under Marriage Allowance, your code should reflect this. The transferring partner's code is reduced (typically to 1187L in 2024/25), and the receiving partner's code is increased (typically to 1383M or 1383N, depending on which direction the transfer flows).

Marriage Allowance transfers do not renew automatically if circumstances change. If the lower-earning partner's income now exceeds the Personal Allowance, the transfer should be cancelled. If it has not been, HMRC is applying an allowance that technically should not exist, which creates a liability rather than a saving.

5. Look for Emergency or Non-Standard Codes

If you see a code ending in W1, M1, or X (for example, 1257L W1), your employer is using an emergency basis. This means your pay is being taxed as though each pay period is a completely independent event, with no reference to earnings so far that year. Emergency codes are used when HMRC has not issued a proper coding notice in time, typically when you start a new job or return from a career break.

Emergency codes are supposed to be temporary. If you have been on one for more than two pay periods without it resolving, contact HMRC directly or check your Personal Tax Account. You may be overpaying, particularly if your income is irregular or weighted toward the start of the year.

If you have recently started a second job, the emergency code issue is especially common. Our post on multiple employment tax codes covers the mechanics in detail.

6. Check Whether Your Code Reflects Undisclosed Income HMRC Has Estimated

HMRC is not entirely passive. If it suspects you have untaxed income -- rental income, freelance earnings, a side business -- it may adjust your employment tax code to collect estimated tax through PAYE, even before any formal assessment. This is known as a Simple Assessment or a coding-in adjustment.

The estimate may be based on old data, a misread bank transaction report (from the Connect system), or an overly optimistic assumption about how much that side income has grown. Check your coding notice for any mention of "other income" or "untaxed income" and compare the figure used against your actual earnings. If HMRC has estimated £5,000 of rental income and you actually received £2,800, you are overpaying by £440 at the basic rate.

7. Confirm Child Benefit Adjustments Are Correctly Applied

If your adjusted net income exceeds £60,000 (from April 2024, following the Budget change to the High Income Child Benefit Charge threshold), you may need to repay some or all of your Child Benefit through a tax charge. HMRC may collect this through your tax code by reducing your allowances.

The adjustment should be based on your actual income and the actual Child Benefit payments received. If your income fluctuates year to year, or if a child has left the household, the figure in your code may be stale. Our post on High Income Child Benefit Charge and tax code errors walks through the specific scenarios.

8. Verify the Letter Suffix Is Correct

The letter at the end of your code is not decorative. It carries specific legal meaning:

• L: Standard Personal Allowance. Correct for most employees.
• M: You are receiving the Marriage Allowance transfer (10% of your partner's allowance).
• N: You have transferred 10% of your allowance to your partner.
• T: Your allowance calculation is more complex; HMRC needs to review it regularly.
• 0T: No Personal Allowance at all, either because you have not provided a P45 or your allowance has been entirely used up.
• BR: All income taxed at basic rate (20%), usually applied to a second income source.
• D0: All income taxed at higher rate (40%), typically a second job.
• D1: All income taxed at additional rate (45%).
• NT: No tax deducted at all.
• K: A negative allowance, meaning your untaxed income or benefits exceed your Personal Allowance.

A BR or D0 code on your main employment is a serious error. It means you are being taxed at a flat rate with no Personal Allowance applied, which will almost certainly result in significant overpayment. Verify your tax code accuracy now if you see either of these on your primary payslip.

What to Do When You Find an Error

Do not wait for HMRC to spot it. The system is largely self-reporting: HMRC relies on you to flag discrepancies. Here is the sequence:

1. Log into your Personal Tax Account at gov.uk and check the breakdown of your current code.
2. Identify the specific adjustment that appears incorrect (a benefit value, an underpayment figure, an estimated income).
3. Gather evidence: your P60, P11D, payslips, or any correspondence from HMRC.
4. Contact HMRC via the online service or by phone (0300 200 3300). Be specific: "My coding notice shows a company car benefit of £6,800 but the vehicle was returned in August 2023. Please remove this adjustment."
5. Confirm the revised code has been issued to your employer and check your next payslip to verify the change has been applied.

If the error spans multiple years, submit a separate claim for each tax year affected. You cannot claim a blanket refund; HMRC processes each year individually.

How Much Could This Actually Be Worth?

Let us make this concrete. A nurse earning £48,000 with a company car benefit incorrectly valued at £5,500 (the actual value having been £3,200 since the vehicle changed) is effectively being taxed on £2,300 of phantom income. At the higher rate of 40%, that is £920 overpaid per year. If this has been running for three years, the refund claim is worth £2,760.

A warehouse operative on £32,000 with an emergency W1 code applied after a job change, never corrected, pays basic rate tax on every month's earnings as though it were a standalone event. Depending on how their income is distributed across the year, they could overpay by £150 to £400 before the end of the tax year.

Neither person will receive a proactive refund notice. HMRC will reconcile PAYE at year end and, if the overpayment is obvious from the data it holds, may issue a P800 refund letter. But if the error is based on stale data HMRC does not know is stale, no P800 arrives. The money sits there, earning interest for the Treasury rather than for you.

The Annual Verification Habit

The single most effective thing you can do is treat tax code verification as a brief annual task, ideally at the start of each tax year in April, when new codes are issued, and again after any life change: a new job, a pay rise that pushes you over £100,000 (see our post on income over £100,000 and the shrinking tax code), a change in benefits, a marriage or civil partnership, or a child leaving home.

If you are also self-employed alongside employment, the interactions between your PAYE code and your Self Assessment liability add another layer of complexity. Our post on freelance and employed tax code defaults covers that specific scenario.

For pension savers, check whether your contributions affect your code as well. Relief at source pensions are handled differently from net pay arrangements, and the tax code implications are not always obvious. See pension contributions and tax code relief for the full picture.

You started reading this because HMRC has, in aggregate, overcharged UK employees by hundreds of millions of pounds. The checklist above gives you the tools to find out whether you are part of that statistic. Start by verifying your tax code accuracy now and work through each section methodically. The whole process takes under twenty minutes, and it could be the most financially productive twenty minutes of your year.

You might also like

Photo: Unsplash

Tax Tips

Reasonable Excuse HMRC Penalty: What Actually Qualifies

HMRC rejects most reasonable excuse claims. Here's what the law actually says qualifies, what doesn't, and how sole traders can build a winning case.

26 May 20269 min read

Photo: Unsplash

Tax Tips

Expense Tracker for Sole Traders: What HMRC Actually Requires

HMRC's MTD rules change what a sole trader expense tracker must do. Here's what actually counts as compliant digital record-keeping — and what doesn't.

24 May 202610 min read

Photo: Unsplash

Tax Tips

Remote Worker Sole Trader Tax Return: The Home Office Trap

Working from home as a sole trader sounds simple until HMRC's rules bite. Here's what remote worker sole traders actually owe and can claim.

23 May 20269 min read