W1 M1 Tax Code Emergency: Why It Costs You Money
The W1 M1 emergency tax code could be silently overcharging you every payday. Here is what it means, why HMRC uses it, and how to fix it fast.
If your payslip shows a tax code ending in W1 or M1, HMRC is treating you like a stranger. Not a valued taxpayer with a history and a personal allowance spread sensibly across the year. A stranger. And that distinction is costing many employees real money every single month.
- W1 and M1 are emergency tax code suffixes meaning your employer taxes each pay period in isolation, with no reference to what you have already earned or paid this tax year.
- This approach almost always results in overpaid tax, particularly if you started a new job mid-year or returned from a period without income.
- HMRC will not automatically chase down your overpayment. You have to act.
- The fix is straightforward: contact HMRC or your employer with your P45 or P60 details, or check your tax code free at /check-my-tax-code.
- Most W1 M1 codes are resolved within weeks once the correct information reaches HMRC, but every payday you wait costs you more.
- W1 M1 Tax Code
- An emergency tax code suffix used by HMRC and employers when your full tax history for the current year is not yet available. W1 stands for Week 1 basis and M1 stands for Month 1 basis, depending on whether you are paid weekly or monthly. Under this code, your employer calculates tax as if each pay period is the first of the tax year, ignoring any personal allowance already used or tax already paid. The result is almost always too much tax deducted.
What W1 and M1 Actually Mean in Pounds
The normal way HMRC operates is called a cumulative tax code. Your employer looks at your total earnings so far this tax year, your total tax paid so far, and calculates what you owe on today's pay. If you were undertaxed last month, they claw a little back. If you were overtaxed, you get a small refund in your next payslip. It balances continuously.
W1 and M1 break that mechanism entirely.
Under Week 1 or Month 1 basis, your employer treats every pay period as a fresh start. They apply one week's or one month's worth of your personal allowance to that pay packet and tax the rest. They do not look back. They do not look forward. Each pay period is an island.
Here is why that matters in practice. Suppose you started a new job in August, three months into the tax year. From April to July, you were not working or were earning elsewhere. The cumulative system would recognise that you have used very little of your £12,570 personal allowance so far and give you the benefit of the unused portion across your remaining pay periods. The W1 M1 system does not. It gives you one month's allowance, roughly £1,047, and taxes everything above that at 20 per cent. The allowance you did not use in April, May, June and July? Gone. You simply do not get it.
For a mid-year starter earning £2,800 per month gross, the difference between a correct cumulative code and an M1 emergency code can easily exceed £200 overpaid in a single month. Over a few months before the code is corrected, that is real money sitting with HMRC rather than in your bank account.
Why Does HMRC Issue an Emergency Code at All?
Emergency codes are not malicious. They exist because HMRC needs a fallback for situations where your employer does not have the information they need to apply a correct code. The most common triggers are:
Starting a new job without a P45. Your P45 tells your new employer how much you have earned and paid in tax so far this year. No P45, no history. Emergency code.
Starting your first ever job. Student finishing university and entering the workforce for the first time? HMRC has no employment record for you. Emergency code.
Returning to work after a gap. Career break, redundancy, illness. If you were out of the PAYE system for a while and HMRC cannot confirm your current year position, emergency code.
Employer fails to receive a coding notice in time. Even when HMRC has all the right information, there is sometimes a timing gap between HMRC issuing a new tax code and your payroll system updating. Some employers run payroll days before the updated code arrives.
Starting a second job. If you pick up a second role alongside your main employment, your second employer will almost certainly start you on an emergency code because your personal allowance is already allocated to your primary job.
None of these situations is your fault. But the financial consequences land on you regardless.
The Hidden Problem: HMRC Will Not Chase Your Refund
This is the part that frustrates most people once they understand the system. HMRC has mechanisms to detect and recover underpaid tax automatically. They will send you a P800 or a Simple Assessment if you owe them money. But overpaid tax, the kind that results from an emergency code being left in place for months, does not trigger the same proactive behaviour.
You can read more about this dynamic in our post on Claim Back Overpaid Tax: Why HMRC Won't Chase You. The short version: HMRC may eventually reconcile your position at year end and issue a refund via a P800 notice, but that process is neither guaranteed nor speedy. It can take until the following tax year. In the meantime, you are effectively giving HMRC an interest-free loan.
The faster route is to resolve the emergency code itself. Once your code is corrected to a cumulative basis, your employer's payroll software will recalculate what you have actually overpaid and begin returning it to you through your monthly pay, without you having to claim a formal refund at all.
How to Spot a W1 or M1 Code on Your Payslip
Your payslip or P60 will show your tax code as a combination of numbers and letters. Common examples in an emergency scenario might look like: 1257L W1, 1257L M1, BR M1, or 0T W1.
The number and main letter define your allowance and rate. The W1 or M1 at the end is the emergency suffix. If you see either of those on your payslip, you are on a non-cumulative basis. If you are unsure what any part of your code means, our post on Tax Code on Your Payslip: What Each Part Actually Means breaks down every element.
You can also check your current tax code instantly at /check-my-tax-code without needing to log in to the HMRC personal tax account or call anyone.
People also ask
What to Do Right Now
The steps to resolve a W1 M1 code are not complicated, but they do require you to take action rather than wait.
Step 1: Confirm the code you are actually on
Check your most recent payslip or log into your HMRC personal tax account at gov.uk. Alternatively, check your tax code at /check-my-tax-code for a quick read on your current position. You need to know the exact code before you can dispute it.
Step 2: Gather your P45 or earnings history
If you have just started a new job and you have a P45 from your previous employer, give it to your new employer's payroll team immediately. That single document often resolves the issue without any further involvement from HMRC. Your new employer can use the P45 figures to apply a correct cumulative code from the next pay run.
If you do not have a P45, perhaps because your previous employer has not yet issued it or you have never been employed before, fill in a Starter Checklist (previously called a P46) through your employer. This tells payroll which of three standard situations applies to you and allows them to apply a reasonable code while HMRC issues the correct one.
Step 3: Contact HMRC directly if the code persists
If your code has not changed after two or three pay periods and you have already submitted a P45 or Starter Checklist, call HMRC's income tax helpline on 0300 200 3300. Have your National Insurance number, employer's PAYE reference (from your payslip), and estimated annual income to hand. HMRC can issue a new coding notice to your employer directly.
You can also update your details and flag a wrong code through the HMRC personal tax account online, which some people find faster than the phone queue. Our post on HMRC Wrong Tax Code Contact: What They Can Actually Fix has a practical breakdown of what each contact route can and cannot achieve.
Step 4: Understand how your refund arrives
Once your code is corrected to cumulative basis, your employer's payroll software will automatically calculate the difference between what you have actually paid and what you should have paid. In most cases, the overpayment is returned to you as a reduction in tax on your next payslip or spread across the remaining pay periods in the tax year. You do not need to file a separate refund claim.
If you are already past the end of the tax year when you discover the problem, you will need to claim the overpayment through self-assessment or by writing to HMRC. Our post on How to Get a Tax Rebate UK 2025: Claim What Is Yours covers that process in detail.
A Concrete Example: What the Numbers Look Like
Meet Jamie, an electrician who left one firm in June and started with a new employer in August. His previous salary was £38,000. His new salary is the same.
Because there was a gap in employment and his P45 took three weeks to arrive, his new employer started him on 1257L M1.
In August, Jamie earns £3,167 gross. Under M1, his employer applies one month's personal allowance (£1,047) and taxes the remaining £2,120 at 20 per cent. Tax deducted: £424.
But the cumulative picture tells a different story. Jamie earned nothing from HMRC's perspective in July (gap month) and nothing in the first three months of the tax year either, because his previous employer's earnings and tax are tracked separately via the P45. With the P45 data correctly loaded, his cumulative position shows he has already paid appropriate tax on his April to June earnings and his August tax should reflect that running total.
The result: Jamie is overtaxed by roughly £180 in August alone. Across three months on the wrong code before it is resolved, that totals around £540 overpaid.
Not a catastrophe. But not nothing either, especially if you are watching your cash flow carefully after a job change.
For employees whose income sits between £50,000 and £80,000, an uncorrected emergency code can interact badly with High Income Child Benefit Tax Charge obligations. If that applies to you, it is worth cross-checking your position with our tax calculator for multiple incomes to understand the full picture.
One Common Misconception Worth Naming
Many people assume that if they are on tax code 1257L, the standard code, they must be fine. The suffix is the trap. 1257L M1 and 1257L are two entirely different things. The allowance number may be correct, but the M1 suffix means it is being applied on a non-cumulative basis. You can be on the right number and still be significantly overtaxed.
For a fuller picture of how your personal allowance is supposed to work across the year, Personal Allowance Tax Code 2025: Are You Getting It? explains the mechanics clearly.
The Payslip You Cannot Afford to Ignore
You searched for "W1 M1 tax code emergency explained" because something on your payslip did not look right. That instinct is correct. An emergency code suffix is not a minor technicality. It is a signal that HMRC's system is making assumptions about your income rather than using real data, and those assumptions almost always work in HMRC's favour, not yours.
The fix is not complicated. Check your code today at /check-my-tax-code, locate your P45 or fill in a Starter Checklist, and get the correct information to your employer's payroll team. Every month you wait is another month of overpaid tax that you will eventually have to chase back, rather than simply keeping in the first place.
You might also like
Ready to simplify your tax filing?
Join the waitlist and be the first to know when TapTax launches.