Emergency Tax Codes Explained — Why You're Overpaying and How to Fix It (2026)

What Is an Emergency Tax Code?

An emergency tax code is a temporary code applied to your pay when HMRC or your employer doesn't have enough information to work out the right tax. Specifically, they're missing details of your income for the year so far and how much tax you've already paid. Rather than guess, the system applies a default code that keeps tax flowing — but often at a level that means you overpay.

The standard personal allowance code for the 2026/27 tax year is 1257L. The numbers represent your tax-free personal allowance (£12,570) divided by ten, and the letter signals how that allowance is applied. Most employed people in the trades are on 1257L for the bulk of their salary. An emergency code is what you get instead when the system is working blind.

Emergency codes usually appear in one of these forms:

• 1257L W1, 1257L M1 or 1257L X — you still get your personal allowance, but on a "week 1" or "month 1" (non-cumulative) basis. The X is a generic marker used where pay is irregular.
• BR — all income from that source is taxed at the basic rate of 20%, with no personal allowance applied.
• 0T — no personal allowance at all, and pay is taxed across the basic, higher and additional rate bands as it rises.
• D0 and D1 — all income taxed at the higher rate (40%) or additional rate (45%) respectively.

Not every one of these is technically an "emergency" code in HMRC's strict definition — the true emergency codes are the 1257L W1/M1/X variants — but in everyday terms, any of them landing on your payslip unexpectedly is a sign your code needs checking.

Quick Reference: Common Tax Codes Explained

When Emergency Tax Happens

Emergency tax codes aren't random — they appear in specific, predictable situations. If you recognise any of these, check your code straight away rather than waiting for a payslip to tell you something's wrong.

• Starting a new job without a P45: If you can't hand your new employer a P45 from your last job, they have no record of your year-to-date pay and tax, so a temporary code is applied until HMRC catches up.
• Your first salary from your own limited company: When you set up PAYE for a new company and run your first payroll as a director, there's often no prior-year information feeding through, so the software defaults to an emergency or 0T code.
• Moving from self-employment to employment: Coming off the tools as a sole trader and into a PAYE role mid-year means you have no P45 — your Self Assessment income isn't reported through PAYE — so an emergency code is common.
• Taking a taxable pension lump sum: Drawing a one-off taxable amount from a pension frequently triggers an emergency code, and because the pension provider treats it as month 1, the tax taken can be eye-wateringly high.
• Second jobs: Your personal allowance is normally allocated to your main job, so a second job is often coded BR, D0 or D1 — all of it taxed without any tax-free portion.

Cumulative vs Week 1 / Month 1 — Why Non-Cumulative Costs You

This is the part that catches most people out, so it's worth understanding properly.

A normal, cumulative tax code looks at your total pay and total tax for the whole tax year to date every time you're paid. It works out how much of your personal allowance you've used so far and how much tax you should have paid by this point, then corrects for any difference. If you've overpaid in earlier months, a cumulative code automatically gives some back. It's self-correcting.

A week 1 / month 1 (non-cumulative) code does not look back. It treats every pay period as if it were the first period of the year, giving you only one period's worth of allowance and ignoring everything that came before. There's no looking back to reclaim unused allowance or correct earlier overpayments.

Why does this lead to overpaying? Say you start a new job in month 6 of the tax year. Under a cumulative code, you'd be entitled to six months' worth of unused personal allowance — a big chunk of tax-free pay. Under a month 1 code, you only get one month's allowance and the other five months' worth is left on the table. The tax you overpay because of that doesn't come back through payroll until your code is switched to cumulative or the year is reconciled.

A Worked Example: BR Code on a £2,500 Month

Numbers make this concrete. Imagine you take a £2,500 gross monthly salary — a fairly typical director's drawing or a steady PAYE wage. Here's the difference between being stuck on a BR code and being on the correct cumulative 1257L code. (Figures are for income tax only and ignore National Insurance, which is calculated separately.)

On a BR code you'd hand over £500 in income tax that month against the £290.50 you actually owe — overpaying around £209.50. Left unchecked over several months, that's well over a thousand pounds of your cash sitting with HMRC instead of in your business. The money isn't lost, but it's your working capital tied up needlessly until the code is fixed or the year is reconciled.

How to Get Your Tax Code Fixed

The good news is that emergency codes are almost always quick to sort out. The fix depends on the cause, but the steps below cover the common cases.

• Give your employer your P45: If you have one from a previous job in the same tax year, hand all parts to your new employer. It tells them your year-to-date pay and tax so they can apply the correct cumulative code.
• Complete HMRC's starter checklist: If you don't have a P45 (common when leaving self-employment), fill in the starter checklist your employer provides. Answering the questions honestly lets them apply a more accurate code from the off, rather than defaulting to 0T or an emergency code.
• Check your code in your Personal Tax Account: Log in to your Personal Tax Account on GOV.UK or open the free HMRC app. You can see your current tax code, the income HMRC thinks you have, and whether an emergency marker is applied.
• Contact HMRC if it's wrong: If the code still looks wrong, tell HMRC through the app, online, or by phone. Once they update it, they issue a revised code to your employer (a P6 or P9 notice) and your next payslip should use it.

For directors of their own limited company, the quickest route is often to make sure your payroll software has accurate director details and that you've checked your code in your Personal Tax Account before the first run. Getting it right before you process payroll avoids the overpayment entirely.

How Overpaid Tax Gets Refunded

If you've overpaid because of an emergency code, you don't have to write it off — it comes back to you in one of two ways.

• Automatically through payroll: If your code is corrected to a cumulative one during the same tax year, the next payroll run looks back over the year and refunds the overpaid tax through your wages. You might see a payslip where your tax deduction is negative or much lower than usual — that's the refund coming through.
• Via a tax year reconciliation (P800): If the year ends before the code is corrected, HMRC reconciles your records after the tax year closes and, if you've overpaid, sends a P800 calculation explaining the refund and how to claim it — usually paid by bank transfer or cheque.

Either way, the overpayment is recoverable. The cost of getting it wrong is cash flow, not lost money — but for a trade business running tight on working capital, having an extra few hundred pounds a month locked up with HMRC is exactly the kind of avoidable squeeze worth fixing fast.

Directors Paying Themselves a Salary

If you run your trade through a limited company and pay yourself a salary, you wear two hats: you're both the employer running PAYE and the employee receiving the wage. That means emergency codes are something you can both cause and cure.

A frequent scenario is the first payroll of a newly incorporated company. With no prior-year data and no P45 fed in, the software may apply a 0T or emergency code to your salary, so you over-deduct tax from your own pay and the company sends too much to HMRC. Because the company funds the PAYE, the overpaid tax leaves the business bank account just as it would for any employee.

The fix is the same in principle: get your code corrected so it's cumulative, then the overpayment self-corrects through the next payroll run or via reconciliation after year end. The practical tip for directors is to verify your tax code in your Personal Tax Account before the first salary run, and make sure your payroll software (or your accountant) has your correct details and start date. A few minutes of checking up front saves you reclaiming your own money from yourself later.

The Bottom Line

An emergency tax code isn't a penalty and it doesn't mean you've done anything wrong — it's simply HMRC's way of keeping tax flowing while it works out your full picture. The catch is that "keeping tax flowing" usually means taking too much. Know what the codes mean, check yours in the HMRC app whenever you start a job, set up a company, or change how you're paid, and get any error corrected promptly. Do that and the overpaid tax either lands back in your next payslip or comes through after year end — and your cash stays where it belongs, in your business.