Emergency tax on a payslip usually shows up as a sudden jump in PAYE deductions, even though the gross pay looks normal. In UK workplaces it often happens after starting a new job, returning after a gap, switching from agency to permanent, or being paid for the first time through a new payroll system. The payslip may show a tax code such as 1257L W1/M1 (week 1/month 1), 0T, BR, or sometimes an “X” suffix. Take-home pay can drop sharply for that pay period, which can be a shock when rent, council tax, and direct debits are due.
Most cases settle once HMRC matches the job to the right tax record and the employer receives an updated tax code. The difficulty is timing: payroll cut-offs mean a fix can miss the next pay run, so the same wrong code can repeat for another month if nothing is done.
Common causes in UK payroll
Start without P45
The most common trigger is starting a job without a P45 from the previous employer. Payroll then relies on starter details (the “starter checklist”, previously P46). If the wrong statement is selected, or the form is missing, the employer may apply an emergency basis until HMRC confirms the correct code.
Use a week 1 basis
Even with the right personal allowance code (often 1257L), the W1/M1 marker means tax is calculated per pay period without looking back at earlier pay in the tax year. This is common after job changes and can delay refunds that would normally happen automatically through PAYE.
Hold multiple jobs
Where there is a main job plus a second job, HMRC may allocate the personal allowance to one employment and use BR (basic rate) or 0T on the other. If the allowance is allocated to the wrong job, the higher-paid role can be taxed too heavily.
Change payroll mid-year
Switching payroll providers, moving from weekly to monthly pay, or being moved between PAYE schemes within the same employer group can temporarily break the link to the existing tax record. This often produces a temporary 0T or W1/M1 code until HMRC updates the record.
Have benefits or adjustments
Company benefits (medical cover, car benefit), underpaid tax from a previous year, or a restriction for untaxed income can reduce the allowance in the code. This is not always “emergency tax”, but it can feel the same on the payslip. The pattern is usually a consistent higher deduction, not a one-off spike.
Check the payslip first
Find the tax code
Look for the tax code line on the payslip. Common emergency-style codes include 1257L W1/M1, 0T, BR, D0, and D1. If the code ends with W1 or M1, it is on a non-cumulative basis. If it is 0T, no personal allowance is being applied.
Confirm the pay period
Check whether the payslip is weekly, fortnightly, four-weekly, or monthly. A change in pay frequency can make deductions look unusual for one period, especially if the pay covers an odd number of days.
Compare with last payslip
If there is a previous payslip, compare the tax code and the taxable pay to date figures. A reset of “year to date” numbers can indicate a payroll record change, which often coincides with temporary emergency coding.
Check starter paperwork
If the job is new, confirm whether a P45 was provided and, if not, which starter checklist statement was used. In UK cases, the wrong statement is a frequent cause of over-deduction for the first one or two pay runs.
Fix it step by step
Ask payroll to confirm details
Request confirmation of the tax code currently held on the payroll system and whether it is marked W1/M1. Ask whether an HMRC “P6” notice (tax code notice) has been received for the employment. If payroll has not received an update, the employer usually cannot change the code manually unless HMRC instructs it.
Check HMRC employment record
Use the personal tax account to check that the employer is showing under the correct PAYE employment and that the start date looks right. Where the wrong employer appears, or an old job is still marked as current, HMRC can allocate allowances incorrectly. The quickest route is often through the online account rather than waiting for a letter.
Update estimated income
If the personal tax account shows an unrealistic annual income estimate (common after overtime, bonus months, or a partial-year start), update it. HMRC sometimes issues a restrictive code when it believes income will exceed the allowance thresholds, and correcting the estimate can trigger a new code.
Report missing P45 information
If a P45 exists but was not processed, provide payroll with the details again (previous pay and tax to date). If the P45 is lost, HMRC can still correct the record based on starter information and Real Time Information submissions, but it may take an extra pay cycle.
Chase the next payroll cut-off
Ask payroll when the next cut-off date is and whether an updated code received after that date will apply to the following pay run. In practice, many UK employees see the fix land one pay later than expected because the code arrives just after cut-off.
Check for automatic refund
Where too much tax has been taken under PAYE, the refund is often corrected through the payroll once the code becomes cumulative again. If the code stays W1/M1, refunds may not flow automatically and HMRC may need to intervene. Keep an eye on the next two payslips rather than assuming it will correct immediately.
If it’s ignored
Expect repeat deductions
If the code stays on an emergency basis, the same over-deduction can repeat each pay period. UK patterns show this can run for several months where the employer record is wrong or an old job is still open on HMRC’s system.
Watch for knock-on bills
Reduced net pay often leads to missed direct debits, overdraft fees, and arrears notices. If a move has just happened, this can overlap with council tax account changes and create confusion about what is actually affordable that month. If there is also a council tax issue after a move, see Council tax bill wrong after moving for the typical evidence councils ask for.
Risk year-end corrections
Leaving it until the end of the tax year can mean waiting for a P800 calculation or a refund process that takes longer than a payroll correction. Some people do get money back later, but the cashflow impact is usually the main problem.
When to escalate
Escalate after two payslips
If two consecutive payslips show an emergency-style code and payroll confirms no updated HMRC notice has arrived, it is usually time to contact HMRC directly. In many UK cases, HMRC can issue a corrected code within days once the employment record is aligned, but it still depends on payroll processing times.
Escalate immediately for big errors
Escalate straight away if the tax code is clearly wrong for the situation (for example, 0T on a first and only job with no other income), or if there are multiple employments listed that are not correct. Also escalate if the employer name on the HMRC record is unfamiliar, which can indicate a duplicated payroll record.
Gather useful evidence
Having the right details to hand speeds things up. Typical evidence that helps in UK calls and webchat sessions includes:
- Latest payslip showing the tax code and PAYE reference (often near employer details)
- P45 details if available (previous pay and tax to date)
- Start date and payroll number
- Confirmation of whether there is another job or pension paying income
- Any recent HMRC coding notice letter or message in the personal tax account
FAQ
Will emergency tax be refunded?
Often yes, if too much tax has been taken and the correct cumulative code is applied later in the same tax year. If the code stays non-cumulative (W1/M1), a refund may not appear through payroll and HMRC may need to calculate it.
How long does a tax code…
HMRC can issue an updated code quickly, but it commonly takes one to two pay cycles to show on payslips because of payroll cut-offs and processing schedules.
Can an employer change the code?
Employers normally apply the code HMRC sends. They can correct obvious payroll input errors (such as a missed starter checklist), but they usually cannot invent a new tax code without HMRC instruction.
Why does it say 1257L M1?
That usually means the standard personal allowance is being used, but on a month 1 basis. Tax is calculated as if it is the first month of the tax year each time, which can prevent automatic refunds for earlier overpayments.
What if there are two jobs…
HMRC may have an old job still marked as active, or a duplicate employment record. This can split allowances or apply BR/0T incorrectly. Correcting the employment status in the personal tax account often resolves it.
Before you move on
Save a copy of the last two payslips, note the tax code and PAYE reference, and check the personal tax account for the employer record and income estimate; then ask payroll for the cut-off date and whether an HMRC notice has arrived. If you felt pushed to accept a quick explanation or told it would “sort itself out”, that’s a common sign the issue needs a clear timeline and written confirmation.
Get help with the next step
If the tax code still looks wrong after the checks above, use the contact form at https://ukfixguide.com/contact/ with a photo of the payslip tax code line and the employer PAYE reference.
1 thought on “Emergency tax on payslip”