Emergency Tax HMRC: Fix Your Code & Reclaim Overpayments

You start a new job, or you run payroll for a new starter, and the numbers don’t look right. The employee expected one take-home figure and sees something much lower. The employer gets the message straight away too, because the new joiner asks the same question most payroll teams hear sooner or later: “Why has so much tax come off?”

That’s usually where emergency tax HMRC enters the conversation.

The good news is that emergency tax usually isn’t a fine, a red flag, or proof that anyone has done something seriously wrong. Most of the time, it’s a temporary PAYE holding position used when HMRC or the employer doesn’t yet have the full picture. It feels dramatic on a payslip, but it’s often fixable.

For employees, the priority is understanding what you’re looking at and how to get it corrected. For employers, especially SMEs and owner-managed businesses, this is also a payroll process issue. If your onboarding, starter forms, and Real Time Information submissions are tidy, these problems are less disruptive and easier to sort out.

That Sinking Feeling Your First Payslip Is Wrong

A common version of this goes like this. You’ve left one role on Friday, started the next one on Monday, and your first payday arrives. You open the payslip expecting a clean handover from old employer to new employer. Instead, the tax deduction looks far too high.

If you employ staff, you see the same issue from the other side. A new team member joins, they haven’t got their P45 yet, payroll has to run, and everyone wants the tax to be right first time. Sometimes that happens. Sometimes HMRC’s temporary settings take over first.

That’s the uncomfortable part of emergency tax. It often appears at exactly the moment when people are already in transition. New job. New payroll record. New pension withdrawal. New benefit. New income mix. Cash flow matters most at that point, so an over-deduction feels bigger than it might later on.

What matters is recognising what this usually is. Emergency tax is generally a temporary placeholder, not a punishment. HMRC uses it when the system doesn’t yet have enough current information to apply the correct cumulative tax position. Employers often have to work with the information available on the day payroll is processed.

Practical rule: If a first payslip looks surprisingly low, check the tax code before assuming the gross pay is wrong.

Business owners should care about this just as much as employees do. A wrong-looking payslip creates worry, extra admin, and avoidable back-and-forth. It can also dent confidence in your payroll process, even if the root cause sits with missing or delayed HMRC information rather than a payroll mistake.

What Is Emergency Tax and Why Does It Happen

Think of a normal tax code as HMRC’s instruction sheet for your wages. It tells payroll how much tax-free allowance should be applied and how tax should be collected across the year. A standard code such as 1257L is part of that personalised instruction.

An emergency tax code is what gets used when that personalised instruction hasn’t caught up yet. You’ll often see codes ending in M1, W1, or X. Those letters matter because they show that tax is being worked out on a non-cumulative basis.

The default settings problem

Non-cumulative sounds technical, but the idea is simple. Payroll looks at that one pay period in isolation. It doesn’t properly take account of what happened earlier in the tax year.

That’s why people often feel overtaxed. HMRC explains that emergency codes such as M1 and W1 tax only the payment in that period, rather than using the cumulative year-to-date position, and that can lead to over-taxation because only a slice of the annual personal allowance and tax bands is applied to that payment. For a basic-rate taxpayer earning up to £50,270 in 2026-27, that could mean an overpayment of £2,514, according to HMRC’s guidance on emergency tax codes.

A good analogy is using sat nav with only half the route loaded. The system still gives directions, but it’s making decisions without the full journey. Payroll can still run, but the tax may not reflect your true position yet.

The most common triggers

Emergency tax doesn’t only happen when someone starts a job. It can appear in several everyday situations:

• New employment without a P45. The employer has to process pay, but prior pay and tax details haven’t been fed in.
• Moving from self-employment to PAYE. HMRC may need time to align records.
• Second jobs or changing income sources. The right allowances need to be allocated.
• Benefits starting or ending. Company benefits and taxable state benefits can affect coding.
• Pension withdrawals. First or ad hoc pension payments are a well-known trigger.

Emergency tax usually means “the system is missing context”, not “you’ve done something wrong”.

Why employers should understand it

For SME owners, this isn’t just an employee tax issue. It’s a payroll operations issue. If your starter process is weak, emergency tax queries multiply. If your payroll records are organised and your submissions are prompt, corrections tend to happen more cleanly.

That’s why good onboarding matters. The tax code itself may come from HMRC, but the speed and accuracy of correction often depend on whether the employer has collected the right starter details and filed payroll information properly.

How to Check Your Payslip and Identify an Emergency Code

The fastest way to spot a problem is to check the tax code on the payslip itself. In most payroll layouts, it sits near the employee details and often close to the National Insurance number. If you’re looking at a digital payslip in Xero, BrightPay, Sage Payroll or another payroll platform, it’s usually visible in the summary section rather than buried in the fine print.

If the code ends in M1, W1, or X, that’s your first sign. These endings usually show that tax is being worked out on a non-cumulative basis for that pay period.

Codes worth recognising

Here’s a simple guide to the most common emergency-style codes people notice first.

Employees often get confused by BR and 0T because they don’t always look like the classic M1 or W1 codes. They can still produce the same “why is my net pay so low?” reaction.

How expensive can it be

The reason this matters is simple. The sums can be meaningful. For 2026-27, basic-rate taxpayers earning up to £50,270 might overpay around £2,514 annually, while higher-rate earners up to £100,000 could overpay up to £5,028, because the emergency code fails to give the full benefit of the personal allowance across the year, as explained by Swift Refunds’ emergency tax guide.

That doesn’t mean every employee on an emergency code will lose that exact amount. It means the effect can be substantial enough that checking the code early is worth doing.

Where else to verify it

Don’t rely on the payslip alone. Cross-check the code using your HMRC online record. If you haven’t set that up, this guide on how to get a personal tax account is a useful starting point.

A quick check helps you answer three practical questions:

• Is the code on the payslip the same as HMRC’s current record
• Does HMRC show the correct employer or pension source
• Has the code already been updated, but payroll hasn’t used it yet

If the payslip code and HMRC record don’t match, that usually points to timing. If both look wrong, it’s time to update HMRC.

A Step-by-Step Employee Guide to Fixing Emergency Tax

If you’ve found an emergency code, don’t jump straight to reclaim forms. Start with the cause. In many employment cases, the quickest fix is getting the right information into the payroll and HMRC records so the code can be corrected.

Step one, gather the right paperwork

The first question is whether your employer has your P45 from the previous job. If they don’t, they’ll usually need the starter checklist information instead. That gives payroll enough detail to begin reporting your pay correctly.

Have these details ready before you contact anyone:

• Your National Insurance number. This is the anchor for your PAYE record.
• Your current employer’s PAYE details. Payroll or HR can usually provide this if needed.
• Your most recent payslip. You’ll want the tax code and pay figures in front of you.
• Your P45 if you have one. This often clears up the issue quickly.
• Details of any other jobs or pensions. HMRC needs the full picture to allocate allowances properly.

If you’re the employee, send the P45 to payroll as soon as you get it. If you’re the employer reading this on behalf of staff, ask for it early and chase it politely if it’s missing.

Step two, check whether payroll has already caught up

Sometimes the code has already been corrected in the background, but the payslip you’re worried about was processed before the update landed. Payroll software receives coding notices from HMRC, and those changes are only reflected once processed in the payroll cycle.

Before spending time on hold to HMRC, ask your employer or payroll contact one direct question: “Has a new tax code notice come through since this payslip was run?”

That single check can save a lot of frustration.

Step three, contact HMRC if the record still looks wrong

If the code remains wrong on your HMRC account, contact HMRC and update your employment details. The online personal tax account is usually the clearest route because you can review your employments, income sources and coding information in one place.

Phone is still useful where the situation is messy. That includes overlapping jobs, old employments still showing as active, or a mix of wages and pension income.

A practical explainer can help if you’re also trying to recover tax that’s already been deducted. This overview of claiming a tax refund from HMRC covers the main routes people use.

Step four, understand how the refund usually arrives

For employment income, the refund often comes through one of these routes:

1. A later payslip adjustment. If HMRC corrects the code during the tax year, payroll may refund the overpaid tax through a future wage packet.
2. End-of-year reconciliation. If it isn’t corrected in-year, HMRC may reconcile it after the tax year.
3. Direct HMRC contact. In some cases, HMRC will guide you on what to do next based on your record.

Many people assume they need to make a formal reclaim straight away for every case. That isn’t always true for normal employment income. Quite often, the system corrects itself once the right code is in place.

Pension withdrawals need special attention

Pension withdrawals are different enough to deserve separate treatment. This is one of the most persistent emergency tax HMRC problems because first or ad hoc pension payments are often taxed on a Month 1 basis.

HMRC has refunded over £1.5 billion to pension savers since pension freedoms began in April 2015 because of overtaxed withdrawals. In Q4 2025 alone, HMRC processed 13,652 claims and refunded £46.26 million, with an average refund of £3,388 per claimant, according to this summary of HMRC pension repayment figures.

That’s why pension overtax isn’t a niche problem. It happens regularly.

Here’s a video overview that may help if your issue involves reclaiming tax or understanding HMRC processes:

When forms like P55 matter

If you’ve taken a pension withdrawal and too much tax has come off, the reclaim process may not be the same as ordinary payroll correction. In some cases, form P55 is the relevant route for an in-year reclaim.

That matters because pension overtax can create a real cash flow problem. If you withdrew money for a specific purpose, waiting until the end of the tax year may not be practical.

The key distinction is simple. Employment emergency tax often self-corrects through payroll. Pension emergency tax often needs a more deliberate reclaim route.

The Employer's Role and Modern Payroll Solutions

For employers, emergency tax is partly about compliance and partly about credibility. Staff don’t separate HMRC, payroll software and employer administration in their minds. If the payslip looks wrong, they see it as a workplace problem first.

That’s why strong payroll processes matter. A well-run business doesn’t just pay people on time. It captures starter data properly, submits Real Time Information accurately, and acts quickly when HMRC issues updated coding notices.

Where employers influence the outcome

You can’t always stop HMRC applying an emergency basis at the start. You can reduce the mess around it.

The biggest pressure points are usually these:

• Starter setup. If the employee has a P45, use it promptly. If they don’t, complete the starter checklist cleanly.
• RTI filing. Submit payroll information on time and accurately so HMRC can update records.
• Coding notices. Apply P6 or P9 notices when they arrive through payroll software or HMRC channels.
• Internal communication. Tell employees what’s happened and what the likely fix looks like.

When these basics slip, the payroll team spends more time explaining avoidable problems. The employee spends more time worrying, and the owner spends more time firefighting.

Why software helps, but process matters more

Cloud payroll tools such as Xero, BrightPay, Moneysoft and Sage Payroll make this easier because they centralise starter records, coding updates and reporting history. In practice, that means fewer scraps of paper, fewer manual re-keys and a clearer audit trail.

Xero is especially useful for growing SMEs because payroll sits alongside bookkeeping and reporting. If you’re reviewing payroll systems more broadly, this guide to best payroll software for small business in the UK gives a practical comparison.

Some businesses also operate with wider HR and workforce systems feeding into payroll. If you’re evaluating how employee data flows from onboarding into pay, a separate explainer on understanding UltiPro features is worth a read because it helps frame what good people-system integration should look like before payroll ever runs.

Pension payroll and provider processes also matter

Emergency tax isn’t limited to wages. Pension providers and payroll-connected reporting processes can influence what happens when someone first draws taxable pension income.

For initial pension drawdowns under 1257L M1, the overpayment can be striking. A £30,000 taxable withdrawal can create tax of about £10,943, which is around 37% higher than the correct cumulative tax of roughly £8,000. The same guidance notes that accurate and up-to-date RTI data helps reduce problems, and that individuals can reclaim overpaid tax using form P55, according to Aberdeen’s emergency tax and pensions guide.

Business owners often miss this because they think “pension issue” means “nothing to do with us”. But directors, owner-managers and employees nearing retirement regularly ask payroll and finance teams where the deduction came from. If your business supports salary, benefits, pension administration and payroll in one place, you need someone internally who understands the mechanics.

A payroll process that produces the right answer late still creates stress. Good employers aim for clean data at the start, not just corrections at the end.

When to Get Professional Help from Stewart Accounting Services

Many emergency tax cases are straightforward once the right records are in place. A missing P45 turns up. HMRC updates the code. Payroll applies it. The problem fades away.

Some situations are more awkward because the tax code is only one moving part. That’s usually when professional help saves time and reduces the chance of a second problem appearing after the first one is fixed.

Situations that tend to need extra care

You’ll usually want advice if any of these apply:

• You’re a company director taking salary alongside dividends. PAYE, coding and personal tax planning can overlap.
• You’ve got more than one income source. Multiple jobs, pensions, rental income or benefits can distort how allowances should be used.
• You’re moving between self-employment and PAYE. Record matching can be less tidy than people expect.
• Your business is growing and payroll is becoming operationally heavier. More staff means more starter forms, more coding notices and more room for avoidable admin.
• You don’t want payroll errors affecting staff trust. For many SMEs, that’s reason enough to tighten the process.

Why it matters for business owners

If you’re running a growing business, emergency tax isn’t just a personal annoyance. It’s one more example of how poor admin creates hidden cost. Staff confidence drops. Questions land in the owner’s inbox. Time disappears into follow-up.

Good accounting support solves more than the immediate code issue. It helps line up payroll, bookkeeping, pensions, director remuneration and year-end tax reporting so the same mismatch doesn’t keep repeating.

For employees, the win is clarity. For employers, the win is a payroll function that feels organised and dependable. That matters whether you’ve got a handful of staff or a larger team using cloud systems and tighter monthly reporting.

If you want help making payroll smoother, checking tax codes, handling director pay, or taking the stress out of HMRC compliance, Stewart Accounting Services can help. The team supports SMEs, sole traders, landlords and growing limited companies across the UK with payroll, tax, bookkeeping and practical cloud accounting systems, so you spend less time fixing admin and more time running the business.