Why it appears on your payslip, what the common codes mean, and how to get back onto the right tax code faster.
Emergency tax is the temporary setting employers use when HMRC does not yet have enough information to tax you on the normal cumulative basis. It usually appears when you start a new job without a P45, go back to work after a break, receive your first pension payment, or move between payroll systems in the middle of the tax year. The important bit: emergency tax is usually an admin problem, not a penalty. It does not mean HMRC thinks you have done something wrong.
On a payslip, emergency tax often shows up as 1257L W1, 1257L M1 or 1257L X. The code still points to the standard Personal Allowance, but the W1, M1 or X marker tells payroll to treat that pay period on its own instead of looking at the tax year so far.
Normal PAYE is cumulative. That means it checks how much you have earned and how much tax you have already paid since 6 April, then works out the right running total. Emergency tax breaks that link. Payroll only looks at this week's or this month's pay, which can create an inflated deduction if your first payslip includes back pay, overtime, commission or a bonus.
You may also see codes like 0T, BR or D0 while HMRC sorts your record. Those can feel even harsher because they may remove your allowance or tax all earnings at one rate. BR is normal for some second jobs, but it can also be used by mistake if payroll does not know which employer should get your allowance.
It is also common after university, after parental leave, or when switching quickly between jobs in the same tax year. In other words, it often shows up during messy life admin rather than because of anything unusual in your tax affairs.
If you have overpaid because of emergency tax, that money is normally recoverable. Once HMRC receives the right information and your code moves back onto a cumulative basis, the overpaid amount is often refunded automatically through a later payslip. Sometimes that happens on the very next payroll run. Sometimes it takes a couple of cycles.
If the problem is not corrected before the end of the tax year, HMRC may issue the refund after year end instead. So an ugly first payslip does not always mean the loss is permanent. It often means the timing of the deduction is wrong.
When you speak to HMRC, ask them to confirm which job should have your Personal Allowance and whether they have already sent a coding notice to your employer. If the hold-up is in payroll, your employer may need to apply the updated code on the next run.
Imagine you start a role in June on £36,000 a year and your first monthly pay includes two weeks of back pay. On a normal cumulative code, PAYE would spread your allowance and previous unused tax bands properly across the year. On a Month 1 code, the payroll system treats that payment like a standalone month, so the tax looks heavier than it should. Once HMRC gets the right record, later payslips can reverse the overpayment.
You should move faster if any of these apply:
Emergency tax is usually temporary, and it is often fixable with the right paperwork. Check the code, make sure HMRC has the right employment details, and do not ignore it if it keeps repeating. If you have overpaid, the system will usually refund you through payroll or through HMRC once your record is corrected.