A wrong tax code on an employee's payslip can create problems much faster than many employers realise. The employee may spot the error immediately because their take-home pay looks wrong, or the issue may sit quietly in the background for months until HMRC updates the record, a P60 looks off, or the employee receives an unexpected tax bill or refund. Either way, once a wrong tax code has been used in payroll, you need to deal with it quickly and carefully.

Tax code issues are one of the most common payroll mistakes because several moving parts have to line up properly. The employee's starter paperwork has to be right. The payroll record has to be set up correctly. HMRC notices need to be applied promptly. And employers need to understand the difference between using the code they have been told to use and trying to guess what the code should be.

The good news is that most tax code problems can be traced back to a small number of causes. If you know what to check, you can usually identify the issue quickly, correct the payroll record properly, and reduce the chance of the same problem happening again.

What a tax code actually does

A tax code tells payroll software how much income tax to deduct from an employee's pay. It reflects the employee's tax-free personal allowance and any adjustments HMRC has made because of other income, benefits, underpaid tax from earlier years, or other tax circumstances.

For the 2026/27 tax year, the standard PAYE tax code is 1257L, which gives an employee the standard personal allowance of £12,570. HMRC has also confirmed that the emergency code from 6 April 2026 is 1257L, typically shown with W1, M1, or X when operated on a non-cumulative basis.

Wrong tax code editorial illustration

That means a tax code is not just a label on a payslip. It directly affects how much tax is taken each pay period. If the code is wrong, the payroll result is wrong.

How employers end up using the wrong tax code

Most tax code errors do not happen because an employer deliberately ignores the rules. They usually happen because one of the setup or update steps goes wrong.

The employee joins without a P45

If a new employee does not provide a P45, you must use the HMRC starter checklist process. The statement they choose on that checklist determines the code you use initially. Statement A means use the current personal allowance. Statement B means use the current personal allowance on a Week 1 or Month 1 basis. Statement C means use tax code BR.

Employers get into trouble when they guess instead of following the checklist. A common mistake is applying 1257L cumulatively when the employee should have been on a Week 1 or Month 1 basis, or using BR when the employee's circumstances did not require it.

The payroll record was set up incorrectly

Even when the right documents are available, the wrong code can still be entered into payroll. A starter may have a valid P45, but the code is typed incorrectly. Or someone copies the code from another employee's record by mistake. Small data entry errors at setup can create real problems on payday.

HMRC issued an update and it was not applied

HMRC sends tax code notices to employers when an employee's code needs to change. If the payroll system is not updated promptly, the employee can continue to be taxed using an outdated code. HMRC says that once a code change is needed, it will tell both the employee and the employer, and the updated code should appear on the next or following payslip depending on the pay frequency.

The employer tries to override HMRC

This is a common misunderstanding. Employers are responsible for using the correct code in payroll, but they cannot simply invent or change a code because an employee says it looks wrong. If there is no HMRC notice and no starter-checklist reason to use a specific code, the employer should follow the official process rather than trying to improvise.

How to spot a wrong tax code quickly

The faster you identify the problem, the easier it is to fix. A wrong tax code often reveals itself through one or more practical warning signs.

The employee's net pay changes unexpectedly. If an employee's gross pay is stable but their take-home pay suddenly falls or rises, the tax code is one of the first things to check.
The code on the payslip does not match HMRC's notice. If the employee has received a coding notice from HMRC and the payslip shows something different, there is a mismatch that needs investigating.
The employee is on an emergency code for too long. Emergency codes like 1257L W1, 1257L M1, or 1257L X are often valid temporarily, but they should not sit there forever if HMRC later issues a cumulative code.
The employee complains about overpaying tax. Often the first sign is not a report or audit. It is an employee saying, "Why is my tax so high this month?"
The year-end figures do not make sense. If P60 totals, cumulative tax, or previous-pay figures look unusual, a tax code issue may be part of the problem.

What to check before changing anything

Do not rush into editing the payroll record the moment someone says the code looks wrong. First, gather the evidence and work through the source of the code step by step.

Check the payslip

Confirm exactly what code is being used right now. Note whether it includes W1, M1, or X, because that changes how tax is calculated.

Check the employee's paperwork

Look for the P45 if the employee had one when they joined. If they did not, check the completed starter checklist and confirm whether they selected Statement A, B, or C. HMRC's starter checklist guidance is clear: the employee's statement determines the code you should use at the start.

Check for HMRC coding notices

Review whether HMRC has sent an updated code since the employee joined or since the last tax year began. If there is a newer official notice than the code currently in payroll, that is likely the source of the problem.

Check the date the issue began

Was the wrong code used only this month, or has it been wrong for several pay periods? This matters because it affects how much correction may be needed and whether the employee has been overtaxed or undertaxed over time.

How to fix a wrong tax code on an employee's payslip

Once you have confirmed that the code in payroll is wrong, the correction process becomes much more straightforward. The key is to fix the cause, not just the visible symptom on the latest payslip.

Step 1: identify the correct code source

There are only a few legitimate sources for the code you should use: the employee's P45, the HMRC starter checklist rules for a new starter without a P45, or a tax code notice issued by HMRC. Start there. If none of those support the code currently in payroll, the code needs correction.

Step 2: update the payroll record

Amend the employee's tax code in your payroll software using the correct code and basis. If the new code should be cumulative, make sure it is not incorrectly left on Week 1 or Month 1 treatment. If the employee should be on BR, D0, D1, or another code because of HMRC's notice, apply it exactly as instructed.

Step 3: review the recalculation

When the tax code is corrected, payroll software will usually recalculate the tax position automatically based on the new code and cumulative figures. This is why tax code corrections often fix themselves through payroll rather than requiring a separate manual refund. If too much tax was taken earlier in the year, the recalculation may reduce tax in the next payslip. If too little was taken, the adjustment may increase tax.

Step 4: explain the change to the employee

Employees care less about the tax-code mechanics than the effect on their pay. Tell them what code was being used, what code is now being used, and whether the next payslip is likely to include a correction. If HMRC needs to issue a revised code, explain that the employer cannot invent it without the proper notice.

Step 5: document what happened

Keep a record of why the correction was made, what supporting documents were used, and when the payroll record was updated. If the issue is questioned later by the employee, HMRC, or your accountant, you will want a clear audit trail.

Editorial illustration of a payroll administrator correcting an employee tax code.

When the employee needs to contact HMRC

Not every tax code issue can be solved by the employer alone. Sometimes the payroll record is accurate based on the information available, but the underlying HMRC record is wrong. In that case, the employee needs to update HMRC directly.

HMRC says that if someone thinks their tax code is wrong, they should check and update the details HMRC holds about them using the online service. Once HMRC changes the code, it tells both the employee and the employer within 15 working days. For monthly-paid staff, the new code should usually appear on the next or following payslip. For weekly-paid staff, it should usually appear by the third payslip.

That means there are two different questions employers need to separate clearly. First: are we using the code correctly in payroll? Second: is HMRC's code itself correct based on the employee's circumstances? Employers can fix the first. HMRC must fix the second.

Common tax code mistakes employers make

Some tax code errors are much more common than others. Knowing them helps you build a process that catches them early.

Keeping an emergency code in place too long

Emergency codes are often valid at the start, especially for new starters. But if HMRC later sends a cumulative code and the emergency code remains in place, the employee may continue to pay the wrong amount of tax for longer than necessary.

Confusing cumulative and Week 1 or Month 1 treatment

This is a subtle but important distinction. A cumulative code considers the employee's pay and tax across the tax year to date. A Week 1 or Month 1 code taxes only that pay period in isolation. Using the wrong basis can lead to significant under- or over-deductions even when the code number itself looks familiar.

Ignoring the starter checklist statement

If there is no P45, the checklist matters. Statement A, B, and C are not just admin formalities. They determine the initial code you should use. Skipping that logic and defaulting to whatever looks normal is a common cause of wrong first payslips.

Trusting memory instead of checking notices

Payroll teams and small employers sometimes assume they know what code an employee should be on, especially if the employee has been there for a long time. But tax codes can change because of benefits, multiple jobs, prior-year adjustments, or HMRC reviews. The safe approach is always to check the latest notice, not memory.

How to stop tax code errors happening again

The easiest payroll corrections are the ones you never have to make. Once you have fixed the immediate problem, improve the process that allowed it to happen.

Use a proper starter process. Never add an employee to payroll without either a P45 or a completed starter checklist.
Review HMRC notices promptly. Do not leave coding notices sitting unread. Apply them as part of your regular payroll workflow.
Check payslips after updates. When a code changes, review the next payslip rather than assuming everything recalculated exactly as expected.
Train whoever runs payroll. Many tax code errors are process errors rather than system failures.
Use payroll software that automates updates and flags issues. The more payroll depends on manual data entry and memory, the more likely tax code mistakes become.

Why software matters here

Tax code errors are one of the clearest examples of why payroll software matters. When payroll is handled manually, employers have to remember code rules, starter treatments, update notices, and cumulative calculations themselves. That leaves too much room for inconsistency.

With modern payroll software, much of that risk is reduced. A system that receives and applies HMRC tax code updates automatically, tracks starter settings properly, and recalculates tax based on the correct basis can prevent a simple coding error from turning into months of incorrect deductions.

That is one reason many employers prefer platforms like Sage Payroll. It is built to apply HMRC tax code updates automatically, flag discrepancies, and reduce the manual handling that causes so many first-payslip mistakes. The employer still needs to review records properly, but the process becomes far more controlled.

A wrong tax code rarely starts as a tax problem. It usually starts as a payroll process problem.

What to do today if you have found a wrong code

If you have just discovered the issue, focus on speed and accuracy in that order. First, confirm the code currently in use. Second, gather the employee's P45, starter checklist, and any HMRC notices. Third, update the payroll record only when you know which code should actually be there. Fourth, review how the correction affects the next payslip and explain it clearly to the employee.

If the payroll record is correct but the employee still believes the code itself is wrong, direct them to HMRC's online tax code service. That keeps the responsibilities clear and avoids employers making unofficial changes that create bigger problems later.

The important thing is not to ignore it and hope HMRC sorts it out eventually. Wrong tax codes can often be corrected cleanly when dealt with early. Leave them too long, and what started as one incorrect code can become a year-end mess involving refunds, underpayments, employee frustration, and avoidable admin.

This article is for informational purposes only and does not constitute legal, tax, or payroll advice. For guidance specific to your circumstances, consult a qualified payroll professional, accountant, or HMRC adviser.

Command Palette