Decoding HMRC Tax Codes: Essential Insights for UK Taxpayers

A tax code is HMRC’s instruction to an employer or pension provider about how much tax-free pay to give someone before deducting income tax. Most people never think about theirs until something looks wrong: a smaller payslip than expected, an unfamiliar letter appearing on it, or a P800 calculation arriving after the tax year has closed. Behind every one of those moments sits a short string of numbers and letters that most employees, and a surprising number of managers, cannot read.

This guide explains how UK tax codes are built, what each letter and prefix means, how emergency codes and K codes work, why codes go wrong and how to check and correct one. The second half is written for the people who deal with tax codes every working day: the payroll, finance and employment tax professionals who operate them under PAYE and Real Time Information (RTI), and the businesses deciding when that work needs a dedicated hire. HMRC’s own tax codes guidance on GOV.UK remains the primary source for any individual case.

How a tax code is built

Almost every code has two parts: a number and a letter. The number is the person’s tax-free allowance for the year divided by ten. A code of 1257L therefore reflects a tax-free amount of £12,570, which is the standard personal allowance. Payroll software spreads that allowance across the year, so an employee paid monthly receives roughly one-twelfth of it (about £1,047) free of tax each month, and a weekly-paid employee about one fifty-second.

The letter tells the employer which rules apply to that individual’s circumstances. Where an adjustment is needed, the number moves rather than the letter. A company car worth £3,000 in taxable benefit, for example, reduces the allowance from £12,570 to £9,570, and the code becomes 957L. Tax owed from an earlier year can be collected in the same way, by reducing the allowance so that a little more tax is taken each pay period.

The £12,570 personal allowance has been frozen since April 2021. The freeze was originally due to end in April 2028, but the November 2025 Budget extended it to April 2031, so 1257L is likely to remain the standard code for several more tax years. As ICAEW noted in its coverage of the extended freeze, more people are being drawn into tax, and into higher bands, as wages rise. Two further points affect the number. The allowance is withdrawn by £1 for every £2 of adjusted net income above £100,000, so it has gone entirely at £125,140. And codes change whenever circumstances change: a benefit starting, a second job, a pension beginning, or underpaid tax from a previous year.

What the letters mean

The table below covers the codes and prefixes that payroll teams see most often.

Code	Meaning
L	Entitled to the standard tax-free personal allowance. The most common letter (1257L).
M	Marriage Allowance: has received 10% (£1,260) of a spouse’s or civil partner’s allowance, so 1383M.
N	Marriage Allowance: has transferred 10% of their allowance to a spouse or civil partner, so 1131N.
T	Other calculations are included, often where HMRC needs to review the allowance or the person has asked not to have a standard letter.
0T	No tax-free allowance on this income: the allowance has been used up, tapered away above £100,000, or HMRC lacks the details.
BR	All income from this source taxed at the basic rate (20%). Usually a second job or pension.
D0	All income from this source taxed at the higher rate (40%).
D1	All income from this source taxed at the additional rate (45%).
NT	No tax deducted from this income. Rare, and only in specific circumstances.
K prefix	Deductions exceed the allowance, so notional income is added to pay rather than allowance given.
S prefix	Scottish income tax rates apply (for example S1257L; flat-rate codes SBR and SD0–SD3).
C prefix	Welsh rates of income tax apply (for example C1257L; CBR, CD0, CD1).
W1 / M1 / X	Emergency basis: the code is applied to each pay period on its own (non-cumulative), for example 1257L W1 or 1257L M1.

Scottish and Welsh status depends on where a person lives, not where their employer is based. Welsh rates are currently the same as those in England and Northern Ireland, so a C prefix rarely changes the deduction. Scottish rates and bands are different, which matters for anyone moving across the border mid-year and for employers running mixed payrolls.

The codes that cause most confusion

BR, D0 and D1

These alarm people because they appear to remove the personal allowance altogether, and on that source of income they do. They are usually correct. Where someone has two jobs, or a job and a pension, the allowance is given against the main source and the second is taxed at a flat rate. Problems arise when the allowance is attached to the wrong source, which is common after a job change or when a second job grows into the main one.

K codes

K codes are the least understood. A K code arises when deductions such as taxable benefits (a company car, private medical insurance) or tax owed from an earlier year exceed the personal allowance. Instead of tax-free pay, the code adds notional income. K475, for instance, adds £4,750 a year to taxable pay. K codes are frequently correct, but this is also where errors have the biggest effect on take-home pay, so they deserve checking. A statutory overriding limit means tax deducted under a K code cannot exceed 50% of the employee’s pay in any pay period, so it can never consume a whole salary.

Emergency codes

Emergency codes (marked W1, M1 or X) are used when HMRC or the employer lacks the information to operate a cumulative code, typically for a new starter without a P45. They tax each pay period in isolation rather than taking account of pay and tax earlier in the year, which often means paying too much tax at first. HMRC’s page on emergency tax codes explains the position. They usually resolve once HMRC has full details, with any overpayment corrected through payroll or refunded after the year end.

0T codes

A 0T code gives no allowance at all and is cumulative, unlike BR. It is correct for high earners whose allowance has been fully tapered away, but it is also what appears when HMRC has incomplete information. On a main employment with ordinary earnings, a 0T code is worth querying promptly because the monthly cost is significant.

Why codes go wrong

Tax codes are generated from the information HMRC holds, so errors almost always trace back to information that is missing, late or wrong. The common causes are:

• A job change where the P45 was not provided or the starter checklist was completed incorrectly.
• Multiple employments or pensions, where the allowance is allocated to the wrong source.
• Benefits in kind starting, ending or changing value, since the code adjusts for them prospectively based on estimates.
• Estimated income proving wrong, particularly for people with bonuses, commission or variable hours.
• An earlier underpayment being collected through the code, which surprises people who had forgotten about it.
• Life changes such as a Marriage Allowance election, the State Pension starting or self-employment beginning, which HMRC learns about with a lag.

Correcting a code usually means giving HMRC the right information rather than disputing a calculation. HMRC rarely gets the arithmetic wrong; the inputs are what go astray.

Checking and correcting a code

For an individual, the process is simpler than the worry it causes.

• Check the code on your payslip or P60 or, most usefully, in the HMRC app or your personal tax account, which shows how HMRC built it: the allowance, deductions for benefits and any adjustment for earlier underpayments.
• Work out whether it is actually wrong. An unfamiliar code is often correct, particularly where a benefit has started or there is a second income.
• If it is wrong, tell HMRC rather than your employer. Your employer cannot change it, and the fix is almost always supplying correct information: an estimate of income, a benefit that has ended, a job that has finished.
• Expect the correction to flow through in a later pay period. Where a cumulative code is restored, overpaid tax normally comes back through payroll automatically. Where tax has been over- or underpaid across a full year, HMRC’s year-end reconciliation generally picks it up and issues a P800.

The cases worth acting on quickly are a K code or 0T code on your main employment, or an emergency code that persists beyond a couple of pay periods, because the monthly cash effect is large enough to resolve within weeks rather than at the year end.

What employers and payroll teams should do

This is where tax codes stop being a personal curiosity and become an operational discipline. Employers do not set tax codes and cannot change them; only HMRC can. But employers are responsible for operating the code they are given, correctly and promptly, and for reporting pay and deductions to HMRC under RTI on or before every payday through the Full Payment Submission (FPS), with an Employer Payment Summary (EPS) where adjustments are needed. HMRC’s guide to running payroll sets out the obligations. A well-run process has five features.

• Starter information collected properly. A P45 where available, and a correctly completed starter checklist where not. Most emergency-code problems begin here.
• Code notices applied promptly. In-year P6 notices and the annual P9 notices for the new tax year should be actioned in the next available pay run, not batched, because late application creates corrections that alarm employees.
• Benefits reported accurately and on time. Code adjustments flow from benefit data, and errors there feed into every affected employee’s code.
• A clear line for employee queries. Payroll should be able to explain what a code means and direct the employee to HMRC to change it, rather than guessing or refusing to engage.
• Reconciliation discipline at the year end, catching anomalies before they become P800 surprises, and sitting within a wider framework of internal controls over payroll.

One change on the horizon matters here. HMRC has confirmed that payrolling of most benefits in kind becomes mandatory from April 2027. Once benefits are taxed through payroll in real time, they stop being collected through tax code adjustments, which should mean fewer K codes and fewer mid-year code changes, but more work for payroll teams in setting up and maintaining benefit values. Employers should be preparing now.

When employees ask — what payroll can and cannot say

This boundary is worth being explicit about internally, because it causes friction in most businesses. Payroll can and should explain what the code means and what the employer has been instructed to do. Payroll should not give personal tax advice, speculate about why HMRC issued a particular code, or agree to operate a different code because an employee believes theirs is wrong. Operating anything other than the issued code is not permitted and creates liability for the employer.

The right response to “my code is wrong” is to explain the code, confirm that the employer is operating what HMRC issued, and point the employee to the HMRC app, their personal tax account or the HMRC helpline. Businesses that train payroll staff on that script have far fewer escalations than those that leave each conversation to improvisation. It costs nothing to train for, and it is one of the quieter marks of a well-run finance function.

The roles that own this work

Who owns tax codes in a business depends on its size and the complexity of its pay and benefits. In a growing business the line usually runs from payroll up to a Financial Controller, and later to an in-house tax manager once tax risk justifies one.

• Payroll clerk or administrator. Processes starters, leavers and code notices, and answers first-line queries. Our payroll clerk job description sets out the typical scope.
• Payroll manager. Owns the payroll calendar, RTI submissions, year-end, benefit payrolling and the relationship with any bureau. See the payroll manager job description.
• Finance Manager. In smaller businesses, payroll oversight sits with the Finance Manager, often with an outsourced bureau handling the mechanics.
• Employment tax manager or director. As benefits grow more complex (company cars, salary sacrifice, share schemes, internationally mobile employees), a specialist owns benefit reporting, PAYE Settlement Agreements, employment status and IR35, and HMRC employer compliance reviews.

The trigger for a specialist hire that we see most often is an HMRC employer compliance review that surfaces problems nobody knew existed, which is a considerably more expensive way to discover the need than hiring ahead of it. Our guide to when to bring employment tax in-house covers the decision, and senior appointments are handled through our employment tax director recruitment practice and wider tax recruitment team. For short-term cover through a year end, a benefits payrolling project or a compliance review, interim tax professionals can usually start within days.

For salary benchmarks across tax roles, see our in-house tax manager salary guide and the wider salary guides. Professionals in payroll and employment tax will also find the Chartered Institute of Payroll Professionals and the Association of Taxation Technicians useful for qualifications and technical updates.

Common questions

What does 1257L mean?

It means you are entitled to the standard personal allowance of £12,570 a year, with no adjustments. The allowance is frozen until April 2031, so 1257L will stay the standard code for some time.

Why did my tax code change mid-year?

Usually because HMRC received new information: a benefit starting or ending, a change in estimated income, or an adjustment to collect an earlier underpayment.

Why am I on an emergency code?

Most often because of a new job without a P45 or an incorrectly completed starter checklist. It normally resolves once HMRC has full details.

Can my employer change my tax code?

No. Employers must operate the code HMRC issues. To change it, update your details with HMRC through the app or your personal tax account.

What does the K in my code mean?

That deductions exceed your allowance, so income is added rather than allowance given. It is common where there are significant benefits in kind or tax owed from an earlier year, and tax under a K code is capped at 50% of pay in any period.

Do Scottish and Welsh taxpayers have different codes?

Yes. An S or C prefix shows that Scottish or Welsh rates apply, based on where you live rather than where you work.

Will I get overpaid tax back automatically?

Usually, either through payroll once a cumulative code is restored, or after the year end through HMRC’s reconciliation and a P800.