Early-onboarding discount: £250 off your scheme setup if you go ahead within two weeks of your quote. see how it works →
Tax codes · For employees

Your tax code is wrong. How to get it fixed.

Take home pay drops for no reason you can see, and the only clue is a few characters on the payslip nobody has ever explained. Most bad codes come from one of six things, and all of them are fixable in one place.

Two minutes with your payslip

Find the tax code. If it is 1257L with nothing after it, you have the full Personal Allowance on a cumulative basis and the code is probably right. If it carries W1, M1 or X, if it starts with a letter, or if the number is a long way off 1257, something has told HMRC that your year does not look the way you think it looks. That is the thing to go and find.

The shorthand

What the code is actually saying

The number is your tax free pay for the year with the last digit dropped, so 1257 means £12,570. The letter says what kind of allowance it is. At 2026/27 rates the standard Personal Allowance is £12,570, which is where 1257L comes from.

CodeWhat it meansWorth checking?
1257LFull Personal Allowance, cumulativeNormal for one job
1257L W1 / M1 / XFull allowance, but each pay run taxed in isolationYes, if it lasts past a couple of paydays
BREverything taxed at the basic rate, no allowance hereNormal on a second job, wrong on your only one
0TNo allowance at all, taxed across the bandsAlmost always yes
D0 / D1Everything at the higher or additional rateYes, unless your other income really is that high
K at the frontDeductions exceed your allowance, so income is addedYes, find out what the deduction is

The rest of the payslip is worth knowing too. Our guide to payslip abbreviations covers every code and column you will meet.

Why it went wrong

Six causes, and the tell for each

HMRC builds your code from what it believes about your whole year. It is rarely lying. It is usually working from something out of date, and the shape of the error points straight at the cause.

CauseThe tell
You started a job with no P45 and no starter checklistAn emergency code from your first payday
HMRC thinks you still have an old jobBR or 0T on the job you actually have
A company benefit was added, changed or endedThe number moves by roughly the value of the benefit
Tax underpaid in an earlier year is being collectedA lower number, or a K code, with no change in your pay
HMRC's estimate of your income is staleD0 or a reduced allowance after a pay cut or a part year
Two sources of income, split the wrong wayBoth jobs taxed as if the other one is the main one

Priya, a lab technician in Swansea, is a fair example. She joined a mining equipment manufacturer in month 3 without a P45, got 1257L on a month 1 basis, and stayed on it because nothing in the system knew she had been out of work for the first two months. Her code was giving her a twelfth of the allowance every month and quietly ignoring the two twelfths she had not used. Nothing was broken. Nobody had told HMRC anything.

The fix

One route, and it is not your employer

Payroll cannot help you here, and it is not being awkward. An employer runs the code HMRC issues and has no authority to choose another one. The change has to come from HMRC, which then sends the employer a P6 coding notice telling them to switch.

  1. Open the Check your Income Tax service on GOV.UK. It shows what HMRC believes about your jobs, your pensions, your estimated income for the year and any benefits it has you down for. Most wrong codes are visible in about thirty seconds on that screen.
  2. Correct what is stale. You can update employment details, remove a job you have left, change the income estimate and add or take off company benefits yourself, without ringing anybody.
  3. Chase the missing P45. If you left a job without one, ask that employer for it. A gap in the record is the single most common reason a code is guessing.
  4. Give it fifteen working days. HMRC says it will update the code and tell you and your employer within that window, and the new code shows on a payslip within two or three pay cycles.
  5. If you cannot use the service, ring 0300 200 3300, or +44 135 535 9022 from outside the UK, Monday to Friday between 8am and 6pm. New starters are asked to wait 35 days first, because the record usually catches up without a call.
The money

When you actually get it back

This is the part people brace for and it is usually the easiest. If the overpayment happened in the current tax year and the corrected code is cumulative, you do not claim anything. The next payroll run works out the whole year again, sees that too much has gone, and the difference comes back in your pay. On a big correction that payslip can look startling. It is right.

An earlier tax year works differently. HMRC reconciles after 5 April and sends a P800 tax calculation if you have paid too much or too little, and those go out between June and March of the following tax year. A P800 is not a bill or a cheque, it is a statement of position, with the repayment or the collection arranged from there.

Underpayments are the same story in reverse. HMRC will usually collect the shortfall through next year's code rather than ask for it in one go, which is exactly what a K code often turns out to be.

If your employer is not in the UK

Same codes, nobody in the middle

A DPNI scheme is a real PAYE scheme, so it gets coding notices like any other. What changes is who is watching. The scheme is registered in your name, so there is no UK finance team reading the HMRC inbox, and a P6 can sit unopened for months while the wrong code keeps running. If you are on one of these, checking the code yourself once a quarter is not paranoia, it is the job.

If all of this is new, our guide for employees on direct payment schemes is the place to start, and there is a separate piece on whether you also need to file a tax return.

Common questions

What people ask when the code looks wrong

Can my employer just change it?

No, and you would not want them to. They run the code HMRC gives them. Asking payroll is still worth doing, because they can tell you which code they are actually running and whether it is on a week 1 or month 1 basis, and that is half the diagnosis.

How long does the change take?

Fifteen working days for HMRC to update the code and notify both sides, then two or three pay cycles before it lands on a payslip. If you have just started a job, wait 35 days before contacting HMRC, because the starter information usually arrives on its own.

Do I have to claim the refund?

Not for the current year on a cumulative code. It comes back through the payroll automatically. For an earlier year, wait for the P800, or contact HMRC if you are confident you overpaid and nothing has arrived.

Why am I on an emergency code?

Because your employer had nothing to work from. At 2026/27 rates the emergency code is 1257L on a week 1 or month 1 basis. It gives you the full allowance but ignores everything earlier in the year, so it overtaxes anyone who has had a gap. A completed starter checklist is the fastest way out of it, and the payroll glossary explains the rest of the forms.

Related guides

Read next

General guidance for people employed in the UK, correct for the 2026/27 tax year at the time of writing. It is not personal tax advice, and HMRC's own guidance is the authority on any figure or deadline here. Scotland sets its own income tax bands, so a Scottish code carries an S and the arithmetic differs. For your own position, check it or ask us.

Nobody reading your coding notices?

If your employer is overseas and your PAYE runs in your own name, we pick the notices up, apply them and tell you in plain English why your take home moved. Tell us the situation and we will confirm the right scheme and a fixed monthly fee.

Get my fixed quote
Reply within 1 UK business day Fixed fees, published No lock-in Questions answered, no sales pitch