How Do UK PAYE Tax Codes Work, and What Does an Emergency Code Mean?
## The short answer
A PAYE tax code is a short string of numbers and letters that tells your payroll software how much of an employee's pay is tax-free and how the rest should be taxed. The numbers usually represent the tax-free amount divided by ten, and the letters describe the employee's situation. An **emergency tax code** is a temporary code applied when an employer does not yet have full details from HMRC; it typically gives the basic personal allowance but ignores any prior pay or adjustments, which can lead to over- or under-deduction until the correct code arrives.
## How to read a standard tax code
Take a common code structure of three or four digits followed by a letter. The digits, multiplied by ten, give the approximate annual tax-free allowance. The letter signals the type of allowance or adjustment:
- **L** – the employee is entitled to the standard personal allowance
- **M / N** – the Marriage Allowance has been transferred (received or given)
- **T** – the code includes items HMRC reviews individually
- **K** – deductions exceed allowances, so the code adds to taxable pay rather than reducing it
- **BR / D0 / D1** – all pay is taxed at the basic, higher or additional rate, common for second jobs
- **NT** – no tax is to be deducted
The letter prefix **S** indicates a Scottish taxpayer and **C** indicates a Welsh taxpayer, both of which can carry different rates or bands.
## Cumulative versus non-cumulative codes
Most codes operate on a **cumulative** basis. Each payday, payroll recalculates tax across the whole year to date, so under- or over-payments naturally even out. A code marked **W1**, **M1** or **X** is **non-cumulative**: it looks only at the current period in isolation. Non-cumulative operation is the hallmark of emergency codes and is why a new starter can see odd-looking deductions before their record settles.
## What an emergency code does
When someone starts a job and you do not have a P45 or a confirmed code from HMRC, payroll applies an emergency code. In practice this usually means:
- The standard personal allowance is given
- The code runs on a week 1 / month 1 (non-cumulative) basis
- Previous pay and tax in the year are ignored
For a straightforward employee this often produces broadly correct tax. The problems arise when someone has already used part of their allowance elsewhere, has multiple income sources, or earns enough to cross a threshold the emergency code cannot see. HMRC later issues a corrected, cumulative code, and any difference is reconciled.
## Where tax codes come from
Employers do not invent tax codes; they apply what HMRC instructs. The main sources are:
- The **P45** from a previous employer for a new starter
- The **starter checklist** statement when there is no P45
- **P6 and P9 coding notices** issued electronically by HMRC during the year and at year start
A disciplined payroll process collects coding notices automatically and applies them in the correct period. Applying a P6 late, or missing it entirely, is a frequent cause of an employee being on the wrong code for months.
## Common tax code problems and what causes them
- **Stuck on emergency code:** the corrected code never got applied, often because the coding notice was not retrieved.
- **Unexpected K code:** usually company benefits or untaxed income reducing the allowance below zero.
- **BR on a main job:** the starter declaration was completed as if this were a second job.
- **Two jobs, both with full allowance:** the allowance is duplicated and tax is underpaid, to be clawed back later.
- **Sudden change after a payrise or benefit:** HMRC adjusts the code mid-year to keep deductions roughly accurate.
## The employer's responsibilities
Your job is not to judge whether a code is "right" in the employee's wider tax affairs, but to apply HMRC's instructions promptly and correctly, retrieve coding notices each period, and operate the cumulative or non-cumulative basis exactly as specified. If an employee queries their code, the correct route is for them to contact HMRC, since the employer cannot change a code on request.
Modern payroll systems should pull coding notices automatically, flag emergency or non-cumulative codes that have persisted unusually long, and clearly show employees how their tax-free amount is being applied. neart.ai builds enterprise-grade products in this area, and the recurring lesson is that most tax code complaints trace back to a coding notice that was issued but never applied.
## Practical takeaway
Read the code as allowance (digits times ten) plus a letter describing the situation, and watch for W1/M1/X markers that signal emergency, non-cumulative operation. Make retrieving and applying HMRC coding notices an automated, every-period step, and direct employees with code queries to HMRC rather than changing codes yourself. Done consistently, tax codes correct themselves and surprises are rare.