Pay & Payslips
Emergency Tax Codes And How They Unwind
An emergency code taxes each period in isolation without prior-year allowances, producing over-deduction that corrects itself once the correct code reaches payroll.

A first payslip showing unexpectedly high tax usually reflects the code applied rather than the pay calculated. Emergency codes are a default, not a penalty.
What an emergency code does
Tax systems that use codes give payroll an instruction about how much income to treat as untaxed before deduction begins. The code carries that allowance.
Where the employer has no reliable code, a default is applied. It typically grants a standard allowance for the current period only and ignores everything earned earlier in the year.
Deduction is then calculated on that period alone. The calculation is internally correct and produces the wrong annual answer, because it is missing information rather than misapplying rules.
Why it usually over-deducts
Allowances are cumulative in many systems. Someone who has not worked for part of the year has unused allowance that should reduce the tax due on later earnings.
A period-based emergency code cannot see that history, so the unused allowance is not applied and more tax is taken than the annual position requires.
The same effect appears where a new starter has already used allowance elsewhere, in which case the emergency code can under-deduct instead and produce a later bill.
What causes one to be applied
The commonest cause is a missing or incomplete starter declaration, which is the document telling the new employer about other employment and income.
A late final document from a previous employer produces the same result, since the new payroll has no record of pay and tax already accounted for that year.
Emergency codes also appear after a significant change such as a new pension, a company benefit or a second job, until the authority issues an updated code.
How the correction arrives
Once the correct code is issued, payroll applies it and, in a cumulative system, recalculates the year to date at the next pay run.
The refund then appears inside the normal payslip rather than as a separate payment, which is why a corrected month can show tax that is very low or negative.
Where the code arrives too late in the year, the position is settled after the year closes through whatever reconciliation process the jurisdiction operates.
Checking rather than waiting
The code appears on the payslip, and comparing it across two consecutive periods shows whether it has changed. A code that persists unchanged for months is worth querying.
Payroll can apply a code but generally cannot invent one. The correction usually has to come from the tax authority, which is where the query belongs.
Codes, thresholds and the mechanics of correction differ substantially between jurisdictions and are revised regularly, so the current rules where the employment sits are the ones that apply.
Questions readers ask
Should overtime be uplifted in backdated pay?
If the rate increase applies from an earlier date, overtime and premiums calculated on that rate generally should be too. Check the arrears figure against your hours for the period.
Will the extra tax on arrears come back?
In cumulative systems it typically unwinds over the following pay runs. In period-based systems it waits for annual reconciliation.
Also by Tobias Lindholm
- What a salary actually costs an employerPay & Payslips
- Why a bonus looks brutally taxed in the month it landsPay & Payslips
- Why a pay rise moves your take-home by less than you expectedPay & Payslips
- What each deduction line on a payslip actually fundsPay & Payslips





