Wrong tax code after changing jobs: P45, HMRC and payroll checks

How to check a UK PAYE tax code after a job change, correct employment information and follow a revised code or refund through payroll.

A smaller than expected first pay packet does not by itself establish that your employer has used the wrong tax code. Start with the payslip, the information HMRC holds and the dates on which you changed jobs. Those three records often show whether the issue is missing employment information, a code that has not yet reached payroll, or a deduction unrelated to Income Tax.

This guide concerns checking a UK employee's PAYE tax code after a job change or while holding more than one job. It explains how to organise a correction request and follow the resulting payroll adjustment. It does not calculate an individual's final tax liability. Benefits, pensions, other income and circumstances affecting allowances can change the answer, so a familiar code is not necessarily the correct one for everyone.

1. Identify the deduction before challenging the code

Download the complete payslip for the affected payment and the preceding payment if available. Record the pay date, taxable pay, Income Tax deduction, tax code and any wording showing the calculation basis. Separately note National Insurance, pension contributions, student loan deductions and other items. A change in take-home pay can have several causes; changing the Income Tax code will not automatically correct each one.

Compare like periods. A first payment covering part of a month is different from a normal monthly salary, and a final payment from the previous employer may include additional amounts. Write down what each payslip covers. If the gross pay or hours themselves are wrong, raise that with payroll as a separate issue. Otherwise a request headed simply “wrong tax” may obscure the actual discrepancy.

2. Read the code without choosing a replacement yourself

HMRC's tax-code guide explains the letters and numbers. For example, BR generally taxes all income from that job or pension at the basic rate, while 0T can reflect an allowance already used or missing details for a new job. Neither code alone proves an error. The appropriate treatment depends on your wider record.

Keep the whole code, including any prefix and W1, M1 or NONCUM indication, when asking for help. Do not leave out a suffix because it looks administrative. Use HMRC's official explanation to understand the code, then compare the underlying facts. Asking payroll to substitute a friend's code or an internet example is not a reliable way to correct your own account.

3. Check the employment list HMRC actually holds

Use the official HMRC online service or app to review your current employments and estimated income. Make a list of the employers shown, which ones you still work for and which have ended. A company may appear under its legal payroll name rather than the shop or brand you recognise. Compare that entry with the employer details on your payslip before declaring it a duplicate.

HMRC's guidance for a new or additional job explains how to add missing employment information, report an ended job and update income details. It also says details of a new job should become available within six weeks after the first payday. Keep that reference point distinct from the start date written in your employment contract.

4. Locate the P45 or the starter information you supplied

If you left another job, find the P45 and establish whether you gave it to the new employer. If the previous employer has not supplied one, ask for it. Record the request and response. HMRC explains that the P45 can provide information needed to correct the tax position. A photograph of part of the document may be less useful than a complete, legible copy delivered through payroll's accepted channel.

Where a P45 was unavailable, check the starter checklist you completed. Read what you actually selected rather than relying on memory. HMRC describes how starter information can affect a new-job tax code. If an answer was mistaken, explain the true employment history and ask what needs correcting. Do not create a replacement document that suggests it was supplied earlier.

5. Separate a replacement job from a second job

A new employment does not always mean the old one has finished. You may continue occasional shifts, receive a final payment, or genuinely hold two jobs. Write down the actual dates and whether work continues. If HMRC shows an old job as active when it has ended, report the correct end information through the appropriate service. If it remains active, do not mark it ended merely to obtain a different deduction.

Each job can have its own code. HMRC's multiple-job guidance explains that the standard allowance code should not simply be duplicated across employments. A BR code on an additional job can be consistent with the facts. The useful question is whether HMRC has allocated allowances and estimated income using accurate information, not whether every payslip displays the same code.

6. Review estimated income on a consistent annual basis

Check the tax year and the employer to which an estimate relates before editing it. A contractual annual salary, income received so far and income expected for the rest of a tax year are different figures. Gather payslips and any known changes in working hours. If a service asks for an estimate, read its instructions and keep a note of the assumptions used.

For example, someone starting a job partway through the tax year should not automatically treat a full twelve months of the new salary as the amount earned from that job in that tax year. Equally, excluding expected bonuses or ongoing second-job income can produce an incomplete estimate. Ask HMRC for guidance where the service's requested basis is unclear; avoid repeatedly entering different guesses to force a preferred code.

7. Send a correction request built around specific facts

HMRC's correction guidance directs you to check employment, pension, income and other relevant details. Use its supported online process or contact route. A useful working note identifies the affected employer, the code shown on the payslip, the information you believe is wrong and the documents supporting the change. Keep unrelated personal information out of a general payroll email.

An original example of a focused request is:

My payslip for the stated pay date shows the code copied below. My HMRC account still lists my previous employment as continuing, although it ended on the date shown on my P45. I supplied that P45 to my new employer on the recorded date. Please check whether the employment and income information is correct and tell me whether a revised code is needed. I can provide the supporting documents through your accepted channel.

Change the example to match the actual problem. If both jobs continue, say so. If the P45 has not arrived, do not claim you already supplied it. The request should allow someone to identify a concrete record to check, rather than ask them to approve a code you selected yourself.

8. Follow the correct clock for an HMRC update

HMRC's general correction page says that, where a code needs changing, it should tell you and your employer within fifteen working days. It also advises waiting thirty-five days before contacting HMRC to update income details when you have started a new job. These are different stages. They should not be combined into a promise that a refund will appear a fixed number of days after your first shift.

Record when you updated the information, when HMRC issued a new code and when payroll received it. Keep any confirmation number. If you must follow up, provide those dates and explain what remains wrong. Repeating the same submission through several channels without linking the references can make it harder to establish which version of your employment information was used.

9. Check when payroll applies the revised code

HMRC says a monthly paid employee should see a new code used on the next or following pay, while a weekly paid employee should see it on the third pay. These timings relate to the employer receiving the new code. Ask payroll which code it received and for which payment it will be applied, particularly if a payroll cut-off falls close to the notification.

When the next payslip arrives, compare the code and basis with the HMRC notice. If the expected change has not appeared, HMRC advises contacting the employer. Send the relevant notice and payslip through a suitable channel, and ask payroll to explain the difference. Avoid concluding that HMRC ignored your request when the record shows a code was issued but has not yet been applied.

10. A changed code and a refund are related but separate

HMRC's overpayment guidance explains that it needs the relevant income details for the tax year to work out any difference. Where it has those details, it can ask the employer or pension provider to refund overpaid tax through pay, usually when the new code is used. Missing information may prevent that adjustment at the time you expect.

Therefore, check three things separately: whether the underlying record was corrected, whether a new code was applied and whether an overpayment was actually calculated and repaid. Do not assume the difference between this month's take-home pay and a colleague's pay is your refund entitlement. If the tax year has ended, follow HMRC's instructions for that year's calculation or refund rather than treating a current-year code change as a complete answer.

11. Keep a small reconciliation file

Store the affected payslips, the P45 or starter information, relevant HMRC notices and your correspondence in date order. Add a one-page timeline showing employment end and start dates, first payday, correction submission, code notice and the pay on which it appeared. That is usually more useful than forwarding an entire mailbox without explanation.

After an adjustment, compare the current payslip's year-to-date figures with the documents you used. Ask for clarification if a refund is shown differently from what you expected, and retain the explanation. A corrected code does not replace any separate obligation to report income through another applicable process. Where several income sources or previous-year issues overlap, get advice tailored to those facts instead of assuming one payroll change settles everything.

12. Use a clear follow-up when the issue remains open

Address the remaining problem to the party able to investigate it. Payroll can explain what it paid, what it reported and which code it applied; HMRC can explain the information behind the code it issued. A concise follow-up can attach the latest notice and payslip and ask which specific mismatch remains. Keep a note of the response and any promised next action.

If the answer does not address the evidence, ask for the relevant correction or complaints process and preserve the existing references. Avoid sending bank details or account credentials to an unverified contact. You can use the official service yourself or an appropriately authorised helper. You do not need to share your login merely to let someone help organise documents or draft the questions.

Tax-code correction checklist

  • Identify Income Tax separately from other payslip deductions.
  • Copy the full code and calculation basis from the affected payslip.
  • Match HMRC's employment entries to actual employers and dates.
  • Locate the P45 or the starter information supplied.
  • Distinguish an ended job from a continuing additional job.
  • Check the tax year and basis of any income estimate.
  • Keep correction confirmations and the revised code notice.
  • Check the relevant payroll cycle after the employer receives the code.
  • Verify any actual refund separately from the code change.
  • Keep a short timeline and protect personal account access.

Frequently asked questions

Does BR always mean payroll made a mistake?

No. HMRC explains that BR commonly applies where someone has more than one job or pension. Check your employment list and allowance allocation before requesting a correction. The code needs to reflect your circumstances, which may differ from those of another employee with similar gross pay.

Can payroll use a code I calculate myself?

Do not ask it to substitute an invented code. Check the information HMRC holds and follow the official correction route. Payroll can explain its records and apply the relevant code it receives, but an example found online does not establish your personal tax position.

Will updating my employment produce an immediate refund?

Not necessarily. HMRC needs the relevant income information, and payroll must receive and apply any revised code. Track those steps separately. A missing P45 or other incomplete information can affect when a calculation is possible; a confirmation that you submitted an update is not proof that money has been repaid.

What if my previous job still appears after I leave?

Compare the entry with your P45 and final payslip, and use HMRC's employment-update process to report accurate information. Retain the true end date and distinguish it from the date of a later final payment. Do not remove an employment that actually continues.

What should I keep after the problem is corrected?

Keep the code notice, relevant payslips, P45 or starter information and the correspondence explaining the adjustment. Record which payment used the new code and whether a refund was included. That makes a later query about the same tax year easier to answer accurately.

Sources and review date

The linked HMRC guidance was checked on 21 October 2026. The examples are original explanations of record checking and correspondence. Use the current official process and obtain individual advice where the facts involve multiple income sources, disputed liability or obligations outside this PAYE correction workflow.