Understanding Your Tax Code

What 1257L means, and why most officers have it

1257L is the standard tax code for the vast majority of people in the UK with a single job and no unusual tax circumstances, and it's the code most serving police officers will see on their payslip. The numbers, 1257, represent your tax-free personal allowance for the year, multiplied by ten — so 1257 corresponds to a £12,570 personal allowance. That's the amount you can earn in a tax year before any income tax is due at all.

The letter L simply confirms that you're entitled to the standard personal allowance, with no special adjustments. It's the "default" suffix, distinct from other letters that indicate different circumstances (which we'll come to). If your only income is your police salary, you haven't received any taxable benefits in kind, and you don't have an outstanding balance of tax owed from a previous year, 1257L is almost certainly the code you'll see, and it should stay stable from one tax year to the next unless the personal allowance itself changes or your circumstances change.

It's worth understanding how the £12,570 allowance is applied in practice. HMRC doesn't simply let you earn £12,570 tax-free at the start of the year and then tax everything after that at full rates — under PAYE, the allowance is spread evenly across the year, so each pay period you receive a slice of that £12,570 tax-free before tax is calculated on the rest of that period's taxable pay. This is also why the calculation is cumulative: HMRC's system tracks your total pay and total tax-free allowance used so far in the tax year, so if your income fluctuates from month to month (for example, because of overtime), the system self-corrects over subsequent pay periods to make sure you end the year having paid roughly the right total amount of tax, assuming your code stays the same throughout.

BR, D0, D1 and NT: flat-rate and no-tax codes

Beyond the standard L-suffixed codes, there's a group of codes that apply a single flat rate to all of your pay from that job, with no personal allowance factored in at all. These are most commonly seen where HMRC either doesn't yet have full information about your circumstances, or where the code is deliberately being used for a second source of income.

BR stands for "basic rate" and applies to every pound of pay from that job. This is frequently used for a second job, on the logic that your personal allowance has already been allocated against your main job's tax code, so there's nothing left to apply to the second one. It's also sometimes used as a temporary or emergency code if HMRC doesn't yet have enough information to issue a more tailored one — for example, for an officer who has just started and whose full employment history hasn't yet been matched up in HMRC's systems.

D0 applies to all pay from that job at the higher rate. This is typically used where an officer's main job already uses up their personal allowance and pushes them into higher-rate tax, and a second job's income should logically all be taxed at that higher rate from the first pound, rather than incorrectly benefiting from a second personal allowance.

D1 is the equivalent at the additional rate, used in similar circumstances but for officers whose overall income puts them into the additional rate band — this is less common for police salaries alone, but could apply if an officer has substantial additional income from another source.

NT means no tax is deducted at all. This is unusual and applies in specific circumstances defined by HMRC, rather than being something an employee can simply request. If you see NT on your payslip and you're not aware of a specific reason for it, it's worth double-checking with HMRC that this is correct and intended, since it's not the sort of code you'd expect to see without good reason.

There's also 0T, which is distinct from BR: 0T means no personal allowance is applied (similar to BR in that respect), but unlike BR, the income is still taxed progressively through the normal basic, higher and additional rate bands rather than a single flat rate. 0T is often used as an emergency or temporary code when HMRC doesn't have enough information to issue a proper code — for example, if you've started a new job and haven't provided a P45 or completed a starter checklist, or if your allowance has been used up elsewhere. Because 0T runs through the normal bands rather than a flat rate, the actual amount of tax it results in will depend on how much you earn in that job.

K-codes: when your allowance goes negative

K-codes look unusual at first glance — something like K475 — and they work in the opposite direction to a standard L-code. Instead of giving you a tax-free amount to deduct before working out your taxable pay, a K-code adds an amount to your taxable pay before tax is calculated. In effect, your "allowance" has gone negative.

This happens when the deductions HMRC needs to account for — most commonly taxable benefits in kind (such as a company car, or in some contexts a taxable allowance treated as a benefit), or a chunk of previously underpaid tax that HMRC is recovering through your current tax code — are larger than your standard personal allowance. Since a tax code can't go below zero in the normal L-code sense, HMRC switches to a K-code to represent the shortfall as an addition to your pay rather than a subtraction from it.

K-codes are less common among police officers than among people with significant company benefits, but they can arise, particularly where there's a benefit in kind involved or where a previous year's underpayment is being recovered. If you see a K-code on your payslip and you're not sure why, it's worth checking your HMRC Personal Tax Account online, which shows the breakdown of how your code was calculated, including any benefits or previous underpayments HMRC has factored in.

The Scottish "S" prefix and why it changes the numbers

If you're a Scottish taxpayer, your tax code will carry an "S" prefix — for example, S1257L rather than plain 1257L. The personal allowance itself is the same UK-wide figure, but the crucial difference is that Scottish taxpayers are taxed using Scottish income tax bands and rates, which are set by the Scottish Parliament and differ from the rest of the UK (England, Wales and Northern Ireland).

Scotland has more tax bands than the rest of the UK. These bands apply to taxable income after the personal allowance has been deducted, and they're structured quite differently from the simpler three-band system (basic, higher, additional at 20%, 40% and 45%) used elsewhere in the UK.

The practical effect is that two officers on identical salaries — one in England, one in Scotland — can end up with meaningfully different take-home pay, purely because of which set of bands and rates applies to their income. Generally speaking, Scottish taxpayers pay slightly more tax at the higher end of the income scale due to the additional Intermediate, Higher, Advanced and Top bands sitting at rates that diverge from the rest of the UK, though the effect at more modest salary levels is smaller because of the lower Starter rate on the first slice of income. Whether you're a Scottish taxpayer is determined by where your main home is, not where you work, so an officer who lives in Scotland but occasionally works elsewhere in the UK would still normally be taxed under the Scottish system. The Police Pay Calculator and Pay Scales tools on this site account for Scottish rates separately where relevant, so it's worth double-checking you've selected the right settings if you're based in Scotland.

What to do if your tax code looks wrong

If you look at your payslip and the tax code doesn't match what you'd expect — for example, you're on BR when you only have one job, or you've got a K-code and can't think why — the right first step is to check your HMRC Personal Tax Account online. This free service shows you the tax code HMRC currently holds for you, an explanation of how it was calculated, and any estimated income, benefits or previous under- or overpayments factored into it. It's usually the fastest way to understand why a particular code has been issued.

If the explanation doesn't match your actual circumstances — for instance, HMRC has recorded a benefit in kind you no longer receive, or is still accounting for a previous job you've left — you can update your details or query the code directly with HMRC, either online, by phone, or by post. It's worth having your payslip and National Insurance number to hand when you contact them.

Your force's payroll team can confirm what tax code they're currently applying and can process a new code once HMRC issues one, but they can't change the code itself — that's entirely an HMRC function. If you believe you've been on the wrong code for some time, HMRC can usually recalculate and adjust for past periods too, either through a refund or, if you were undertaxed, by collecting the difference gradually through a revised code in a future year. Because tax circumstances can be genuinely complex — particularly around benefits in kind, multiple sources of income, or previous employment — this article is intended to help you understand the general mechanics rather than give advice on your specific situation; if anything is unclear or the numbers involved are significant, it's worth speaking to HMRC directly or consulting a qualified tax adviser.

Common reasons your tax code changes mid-year

Tax codes aren't necessarily fixed for the whole tax year — HMRC can and does update them mid-year in response to a change in your circumstances, and it's useful to recognise the common triggers so a mid-year change doesn't come as a surprise.

A one-off bonus or lump sum payment can sometimes prompt HMRC to adjust your code, particularly if it changes their estimate of your total annual income for the year in a way that affects which band you're expected to fall into. A new taxable benefit in kind — for example, if your force role changes and you start receiving a benefit that HMRC treats as taxable — can trigger a new K-code or an adjustment to an existing one. Conversely, losing a benefit can mean your code reverts back towards standard.

A previous underpayment of tax, once identified by HMRC (often following the end-of-year reconciliation process), is commonly collected by adjusting your tax code for a future year so that the extra amount is gradually recovered through slightly higher deductions over twelve months, rather than as a single demand. This is one of the more common reasons an officer might see their code change from the standard 1257L to something with a lower number, reflecting a reduced effective allowance to claw back the shortfall.

Starting a second job, or a partner's income and certain allowances (like Marriage Allowance transfers) being adjusted, can also change your code. And simply moving between tax years brings routine updates too — the personal allowance itself can change between tax years, which is reflected in an updated numeric portion of a standard L-code.

Whatever the reason, HMRC should notify you directly (usually by letter or via your Personal Tax Account) whenever your code changes, explaining why. It's worth reading these notices when they arrive rather than filing them away unread, since they're the clearest explanation you'll get of exactly why your take-home pay might look different from one month to the next.