Emergency Tax Codes Explained: Why You Are on One and How to Get Your Money Back

An emergency tax code does not mean HMRC thinks something is wrong. It means your employer or pension provider has been told to tax you without looking at what you have already earned or already paid this year. You still get the £12,570 Personal Allowance, but only one twelfth of it in each month, with nothing carried forward from the months before. On a salary that costs you a few hundred pounds for a few weeks. On a first pension withdrawal it can cost you five thousand pounds in a single payment.

You can spot one instantly. An emergency code ends in W1, M1 or X, and some payslips print NONCUM next to it instead. GOV.UK gives the examples 1257L W1 for weekly pay, S875L M1 for monthly pay in Scotland and C663L X where pay dates vary.

What the code is actually doing to your pay

A normal tax code operates cumulatively. Every payday your employer looks at your total pay for the year so far, your total tax-free allowance for the year so far, and the tax you have already paid, then works out what is owed at that point. If you were out of work for three months, the allowance for those three months is still sitting there waiting for you, and it gets used the moment you start earning again.

An emergency code switches that off. Each pay period is treated as though it were the first one of the tax year and the only one. You get 1/12 of the Personal Allowance in a month, 1/52 in a week, and 1/12 of each tax band as well. Nothing before it exists as far as the calculation is concerned.

People use “emergency tax” loosely to mean any of those last four rows, and that is why so much advice about it is useless. A W1/M1/X code gives you your allowance and generally sorts itself out. A 0T or BR code on your main job does not, and every week you leave it is money you then have to go and reclaim. Our tax code checker will tell you which one you are looking at, and the full guide to UK tax codes explains every letter.

Why HMRC put you on one

GOV.UK lists the triggers, and they are all versions of the same thing: somebody is being asked to tax you before HMRC has caught up with your circumstances.

• A new job with no P45. Your new employer does not have your previous income and tax details, so they cannot operate a cumulative code safely. See our guide to what a P45 is and what to do with it.
• A new job where you ticked statement B on the starter checklist. Statement A (this is your only job and you have had no other income since 6 April) gets you a cumulative code. Statement B (you have had another job this tax year) gets you 1257L on a week 1/month 1 basis. Statement C (you have another job or a pension as well) gets you BR.
• You started getting company benefits, such as a car or medical cover, part way through the year.
• You started getting the State Pension.
• You took money flexibly out of a pension for the first time. This one is in a class of its own and is dealt with below.

HMRC says it “will usually update your tax code when they get all your details from your new and previous employers” and that this “can take up to 35 days from when you start your job”. That is the number to hold in your head. Thirty-five days is normal. Three months is not, and at that point something has gone wrong that will not fix itself.

Worked example: Marcus starts a job in August

Marcus left a job in early April 2026 and was out of work until 1 August 2026, when he started at £36,000, paid £3,000 a month. He had mislaid his P45 and ticked statement B, so his first payslip shows 1257L M1.

August is month 5 of the tax year. Under the emergency code his employer gives him one twelfth of the allowance and taxes the rest.

The cumulative code gives him nothing to pay in August, because four months of unused allowance are still banked. The emergency code ignores all of it. If the code were never corrected he would pay £390.50 in each of the eight months to March, a total of £3,124, when his actual liability on £24,000 of earnings is £2,286 — an overpayment of £838.

What happens in practice is that HMRC issues a cumulative code in September or October, and that month’s payslip shows a large negative tax figure as the overpayment washes back through payroll in one go. The refund is the system working correctly, not a mistake. You can sanity-check the figures with the emergency tax calculator before you ring anyone.

The pension version, where the numbers get serious

When you take money flexibly out of a pension for the first time, the provider has no tax code for you from HMRC, so it must apply the emergency code on a month 1 basis to that payment. The consequence is severe, because a single large withdrawal is treated as though it were one month of a very much larger annual income. One twelfth of every band is applied, and the rest of the payment is pushed straight into 40% and then 45%.

Denise is 58 and takes £20,000 out of her pension in June 2026 as her first flexible withdrawal. A quarter of it, £5,000, is tax free, so £15,000 is taxable. She has no other income that year.

Her actual liability for the year is nothing like that. On £15,000 of taxable pension income with a full £12,570 allowance she owes 20% of £2,430, which is £486. She has had £4,642.87 taken that she does not owe.

She does not have to wait until the following April to get it back. There are three claim forms, and picking the right one matters:

• P55 — you have flexibly accessed the pot but not emptied it, you will not be taking regular or flexible payments before the end of the tax year, and the provider cannot refund you itself. This is Denise’s form.
• P53Z — you have flexibly accessed all of your pension and you are still working.
• P50Z — you have flexibly accessed all of your pension and you have stopped working.

HMRC pays the refund by Faster Payments into an account in your name or your nominee’s, and says it will check the position again at the end of the tax year and contact you if the amount turns out to be different. If you take a further payment later in the same year, the provider will usually have a proper code by then and the arithmetic behaves normally. Before you draw anything, run the number through the pension lump sum tax calculator and read our guide to the 25% tax-free lump sum, because the order and timing of withdrawals is the part you can actually control.

How to get off an emergency code

The fix depends on why you are on one.

1. Give your employer your P45. If you have parts 2 and 3 from your old job, hand them over. This is the fastest route and it often resolves the code before the next payday.
2. If you have no P45, complete the starter checklist and answer it honestly. Ticking B when A is true is the most common self-inflicted cause of an emergency code. Ticking A when it is not true creates an underpayment you will have to repay later, which is worse.
3. Check what HMRC actually thinks you earn. Sign in to the check your Income Tax for the current year service. It shows the code in force, the income figure behind it, and every deduction built into it. A wrong estimated salary is the usual culprit when a code refuses to settle.
4. Tell HMRC if the underlying facts are wrong, through that service or the app. Your employer cannot change your tax code on your say-so — they are legally required to operate whatever code HMRC issues, so asking payroll to fix it will not work.
5. If the tax year ends first, HMRC reconciles automatically and sends a P800 calculation with a refund. You do not need to claim it, though it is worth chasing if nothing has arrived by the autumn.

One thing worth being clear about: there is no penalty and no black mark attached to any of this. An emergency code is a timing problem, not a compliance problem.

Where people lose money

Three mistakes account for almost all of it.

Assuming a BR code will fix itself. It will not. BR taxes every pound at 20% with no allowance, which is right for a genuine second job and wrong for a main one. If your only job is on BR you are overpaying roughly £2,514 a year, and nothing in the system will notice on your behalf until the year end. Our guide to the BR tax code covers how to get it changed.

Taking a large pension withdrawal in March. The emergency deduction is the same whenever you take it, but a withdrawal early in the tax year gives HMRC eleven months to put the code right through your other income, whereas one taken in March leaves you reclaiming the whole overpayment on a form. If you get to choose the timing, choose April.

Ignoring a code that has stopped moving. Thirty-five days is the published expectation. If you are still on W1, M1 or X after two full pay cycles, the usual reason is that HMRC never received a Full Payment Submission linking you to the employer, and that only gets resolved by someone telling them. Compare what the code implies against what you should be taking home using the income tax calculator and our guide to calculating your take-home pay, and if the gap is real, ring HMRC rather than waiting another month.

The short version

An emergency code ending W1, M1 or X gives you the right allowance in the wrong shape. It is an irritation on a salary, where it usually corrects itself within about 35 days and refunds through payroll, and it is expensive on a first pension withdrawal, where it can take thousands of pounds that you can reclaim straight away on a P55, P53Z or P50Z rather than waiting for the year end. What you should not do is assume that any code you do not recognise is an emergency code. Read the suffix, check the figures behind it on GOV.UK’s emergency tax code page and its guide to what your tax code means, and act on the ones that will not fix themselves.