Pension Plus Job: Why Two Income Sources Break Your Tax Code

Your pension started in April. Your employer kept paying you in May. By June, HMRC had quietly given both income sources the same personal allowance, and you were unknowingly overpaying tax on one of them. This is not a rare edge case; it is one of the most common tax code errors in the UK, and it affects hundreds of thousands of people drawing a pension while still in employment.

The keyword that brings most people to this page, "pension and employment tax code two sources", describes a situation HMRC's own systems handle poorly. The rules are clear enough in theory. In practice, the coding notices that flow between HMRC, your employer, and your pension provider are riddled with delays, assumptions, and miscommunications that cost real money.

The Personal Allowance Cannot Be in Two Places at Once

Every UK taxpayer gets one personal allowance. That is not controversial. What surprises many people is that when you have two separate payers, your single allowance has to be physically assigned to those sources via separate tax codes. HMRC does not automatically split it correctly, and the consequences run in both directions.

Scenario one: both your employer and your pension provider each believe they hold your full personal allowance. Both apply a 1257L tax code. You pay no tax on the first £12,570 from your job, and no tax on the first £12,570 from your pension. At the end of the year, HMRC calculates you received £25,140 of tax-free income but were only entitled to £12,570. The resulting underpayment is collected via a P800 tax calculation or a revised tax code the following year. On a pension of £10,000 a year, this error alone could generate an unexpected bill of around £2,000.

Scenario two: HMRC assigns your full personal allowance to your pension and gives your employer a BR code (Basic Rate, 20% on everything) or even a D0 code (Higher Rate, 40% on everything). You are overtaxed from your very first payslip. On a salary of £30,000, a BR code where 1257L should apply overtaxes you by roughly £2,514 in a year. That money sits with HMRC until you claim it back.

Neither outcome is acceptable. Both are preventable.

Why HMRC's System Defaults to the Wrong Setting

When you start drawing a pension, your pension provider notifies HMRC using a starter checklist process. HMRC then issues a coding notice to the provider. The problem is timing. HMRC does not always know the precise details of your employment income at the same moment it is coding your pension, particularly if you started the pension mid-year or switched employers recently.

In the absence of complete information, HMRC defaults to issuing an emergency tax code (often 1257L W1/M1, which is non-cumulative and ignores any tax paid so far that year) or a BR code to whichever payer registers second. This is not malice. It is a system built on sequential data flows that were designed before most people had multiple simultaneous income sources. The average UK worker in the 1970s retired and then drew a pension. Millions now do both at the same time.

The rise of flexible retirement is the structural cause here. The Pension Freedoms Act 2015 allowed people to draw down pension pots from age 55 (rising to 57 in 2028) without fully retiring. An electrician at 58 might draw £800 a month from a personal pension while still working three days a week for a firm. His pension provider gets a BR code. He loses 20% of his pension income in tax he was never meant to pay. He has no idea until he spots his pension statement.

If this sounds familiar, check your tax code at /check-my-tax-code before reading any further. Knowing your current codes is the starting point for everything that follows.

How HMRC Is Supposed to Split the Allowance

The correct approach when you have a pension and employment income simultaneously is for HMRC to allocate your personal allowance across both sources proportionally, or assign it entirely to the higher income and use a BR code on the smaller one (which is correct only if the smaller income is below the remaining allowance threshold).

A worked example makes this concrete. Suppose you earn £28,000 from employment and receive a private pension of £6,000 a year.

• Total income: £34,000
• Personal allowance: £12,570
• Taxable income: £21,430, all at 20% (basic rate)
• Tax due: £4,286

HMRC might correctly assign 1257L to your employer (covering the full allowance against your salary) and issue a BR code to your pension provider, since the pension itself is only £6,000 and falls well within what remains after your salary has used the allowance. The pension provider deducts 20% of £6,000, which is £1,200. Your employer deducts 20% of £15,430 (your salary minus the £12,570 allowance), which is £3,086. Total tax: £4,286. Correct.

But if HMRC mistakenly assigns 1257L to both sources, your employer deducts 20% of £15,430 (£3,086) and your pension provider deducts nothing (the first £12,570 of pension is covered by a phantom allowance). You have paid £3,086 instead of £4,286. The £1,200 shortfall lands on you later, usually as a P800 demand or a reduced 2025/26 tax code.

This is not hypothetical. It happens every April when new tax year coding notices are issued and pension providers receive updated instructions that do not perfectly mirror what has been sent to employers.

The Three Tax Code Mistakes Most Pension and Employment Earners Make

Mistake One: Assuming the Codes Are Automatically Correct

HMRC issues a PAYE Coding Notice (form P2) whenever it changes your tax code. Many people ignore this document, or it goes to an address HMRC has not updated since a house move. If you have not read your most recent P2 for every income source, you have no idea whether your codes are correct.

You can view all active coding notices through your Personal Tax Account at gov.uk. You should see a separate tax code for each payer. If your employer and pension provider both show 1257L and your combined income exceeds £12,570, at least one of those codes is wrong.

Mistake Two: Not Telling HMRC When the Pension Starts

HMRC is supposed to learn about your pension from your pension provider. In practice, there is often a lag of weeks or months. You can short-circuit this by contacting HMRC directly the moment you start drawing income from a new source, using your Personal Tax Account or calling the Income Tax helpline on 0300 200 3300. HMRC can then issue revised coding notices to both payers immediately rather than waiting for the next quarterly reconciliation.

Mistake Three: Ignoring the K Code Risk

If HMRC overcorrects for a prior underpayment while simultaneously trying to code two income sources, you may end up with a K code. A K code means HMRC has added a debt to your tax code rather than a deduction. This effectively increases your taxable income and can result in more than 50% of your gross income being deducted in tax in some months, though there is a 50% cap on deductions for this reason. K codes on pension income are particularly disorienting because pension statements rarely explain them clearly.

For a deeper dive on how salary changes and cascading code errors interact, Tax Code Changed After Salary Increase: What HMRC Does Next covers the mechanics in detail.

Checking Your Codes Right Now: A Practical Sequence

This does not require an accountant. It requires about twenty minutes and your National Insurance number.

Step 1: Log in to your Personal Tax Account at gov.uk/personal-tax-account. Under "Pay As You Earn (PAYE)", you will see a list of your income sources and the tax code currently applied to each.

Step 2: Note the code for your employer and the code for your pension provider separately. Write down both.

Step 3: Add your expected annual income from both sources. If the combined total exceeds £12,570, you should not see two separate 1257L codes. If you do, one payer is using an allowance they are not entitled to.

Step 4: If your pension shows BR and you believe you have remaining personal allowance, check whether your employment income actually uses the full £12,570. If your salary is £10,000, your allowance is not fully used, and a BR code on your pension is overtaxing you.

Step 5: Use the free check at /check-my-tax-code to confirm whether your codes match what you should expect based on your income profile. This comparison takes two minutes and is the fastest way to identify whether you are in overpayment or underpayment territory.

If you want a broader income picture including how these sources interact with National Insurance, How Much Tax Should I Pay? UK Calculator Explained provides a useful reference point.

What to Do If Your Code Is Wrong

If you identify a coding error, here is exactly what to do.

For an overpayment (you are paying too much tax): contact HMRC and request a revised coding notice for the current year. If you have overpaid in the current tax year, HMRC can adjust your code so that future deductions are reduced to compensate. You do not have to wait until April for a P800.

For an underpayment (both sources used the full allowance and you have paid too little): do not ignore this. HMRC will discover it. It is significantly better to contact them now, arrange a payment plan or adjusted code, than to receive an unexpected P800 demand in October. The tax was owed; the error was administrative. HMRC is generally straightforward to deal with when you initiate contact rather than waiting for them to chase you.

For a K code you do not understand: ask HMRC for a written breakdown of how the code was calculated. You are entitled to this. If the calculation includes a prior year underpayment being collected through your current code, confirm the underpayment figure matches your records before accepting it.

For historical overpayments beyond the current year: you can claim back overpaid tax for up to four prior tax years. For 2024/25, that means claims back to 2020/21 are still within scope. Use form R40 or your Personal Tax Account to submit a repayment claim.

The Tax Code Overpayment Calculator: How Much Is HMRC Keeping? post walks through the historical reclaim process in more detail if prior years are relevant to your situation.

The Broader Pattern: HMRC's Coding System Was Built for One-Job Britain

It is worth naming the structural problem directly. The PAYE system was designed in 1944 for a workforce where most people had one employer and retired cleanly at 65. Flexible retirement, portfolio careers, multiple pension pots, and part-time work in later life were not design requirements. They are now the reality for millions.

HMRC's Real Time Information (RTI) system, introduced in 2013, was supposed to make coding more dynamic and accurate. It improved things considerably. But RTI is only as good as the data submitted by employers and pension providers, and the sequencing of those submissions when someone starts or stops drawing from a source mid-year remains imperfect.

The burden of checking, as ever, falls on the individual. HMRC does not proactively audit every coding notice for accuracy. You are the quality control layer in a system that would prefer not to admit it needs one.

If you have recently changed jobs while also managing pension income, Changing Jobs? Your Tax Code Update Can Go Wrong Fast covers the compounding errors that can occur when a job change and pension coding interact badly.

One Scenario That Makes This Concrete

Denise is 59, a part-time office manager earning £22,000 a year. In April 2024 she starts drawing her workplace pension from a previous employer; £7,800 a year. Her combined income is £29,800.

HMRC assigns 1257L to her current employer (correct) and also assigns 1257L to her pension provider (incorrect). Her employer deducts tax on £9,430 (£22,000 minus £12,570), which is £1,886 a year. Her pension provider deducts nothing, treating the full £7,800 as tax-free under the mistaken 1257L code.

Denise's actual tax liability is 20% of £17,230 (£29,800 minus £12,570), which is £3,446. She has paid £1,886. The shortfall is £1,560.

In October 2025, Denise receives a P800 demanding £1,560. She had been spending her pension income assuming it was correct. The demand is not a penalty; it is tax she genuinely owed. But the timing is brutal, and the sum is significant on her income.

A twenty-minute check in May 2024 would have caught this. Both codes visible in her Personal Tax Account; both showing 1257L; combined income obviously above £12,570. One phone call to HMRC to request a BR code on the pension. Problem solved before any shortfall accumulated.

Your Personal Allowance Is Worth £12,570. Guard It.

When your pension started, HMRC had a small window to get the coding right. The question is whether it did. Given that millions of people are in Denise's position right now, and given that HMRC's own figures show billions in tax underpayments and overpayments coexisting in the system simultaneously, the probability that your codes are perfectly set is lower than most people assume.

Check both codes today. If they match what your income profile requires, you can stop worrying. If they do not, you now know exactly what to do. Start with the free check at /check-my-tax-code and go from there. Your personal allowance is worth £2,514 in tax at the basic rate. It deserves to be in the right place.

You might also like

Photo: Unsplash

Tax Tips

Reasonable Excuse HMRC Penalty: What Actually Qualifies

HMRC rejects most reasonable excuse claims. Here's what the law actually says qualifies, what doesn't, and how sole traders can build a winning case.

26 May 20269 min read

Photo: Unsplash

Tax Tips

Expense Tracker for Sole Traders: What HMRC Actually Requires

HMRC's MTD rules change what a sole trader expense tracker must do. Here's what actually counts as compliant digital record-keeping — and what doesn't.

24 May 202610 min read

Photo: Unsplash

Tax Tips

Remote Worker Sole Trader Tax Return: The Home Office Trap

Working from home as a sole trader sounds simple until HMRC's rules bite. Here's what remote worker sole traders actually owe and can claim.

23 May 20269 min read