Skip to main content

How do cumulative and non-cumulative tax codes work in UK payroll?

Marine de Roquefeuil
, Payroll Content Expert
Last updated on
6 mins
Rates & thresholds for 2025/26
Get your rate card
Key takeaways
  • The majority of UK employees are taxed on a cumulative basis, calculating tax on total earnings to date.

  • Non-cumulative codes (Week 1, or Month 1) treat each pay period as an isolated event.

  • Applying the wrong code can lead to administrative headaches and incorrect deductions.

  • When HMRC sends P6 and P9 notifications, they must be applied immediately.

  • Modern software automates updates, automating compliance for each new tax-year.

As an employer, you need to understand the distinction between cumulative and non-cumulative tax codes when navigating UK payroll legislation in order to ensure accurate pay and avoid costly errors

What is a cumulative tax code?

The cumulative basis is the standard for the UK workforce, designed by HMRC as the most accurate method for calculating PAYE (Pay As You Earn) across the tax year.

How does cumulative tax work?

So, how does it actually work? On a cumulative code, the calculation looks at the bigger picture every time you run payroll. It doesn’t just assess the current month, it calculates the overall balance owed based on:

  1. Total gross earnings: Accrued from the start of the tax period (6th April) to the current time.

  2. Accrued allowance: The total tax-free personal allowance accumulated by that specific pay run.

  3. Tax paid: The total tax actually deducted in previous periods.

The logic follows this specific formula:

(Total Gross Earnings − Accrued Allowance) × Tax Rate − Total Tax Paid Previously = Tax Due This Period

The ‘self-correcting’ nature of the calculation ensures stability. If an employee paid too much tax in April, a cumulative calculation in May will lower the deduction to compensate.

Why does cumulative tax benefit the employee?

Cumulative codes smooth out tax fluctuations for employees with variable wages. Among the various tax codes, the common tax code for 2025/26 and 2026/27 is 1257L. Using this cumulatively ensures the £12,570 frozen allowance is spread evenly, allowing for approximately £1,048 of tax-free income monthly.

Payroll complexity slowing down your HR team?

PayFit keeps you compliant with automatic tax and NI updates, lets employees access their own payslips and records instantly, and gets your system live in days, so payroll becomes background work, not a monthly project.

End the payroll struggle
feature-block-module-03

What is a non-cumulative tax code?

A non-cumulative tax code treats every pay day as a stand-alone event, and ignores history.

This means that tax is only calculated based on the earnings in that individual period and doesn’t consider any tax already paid, or personal allowance that has been used. In other words, it only concerns that window of time. 

The disadvantage, of course, is that any unused allowance won’t roll over into future pay periods. And that could mean an employee ends up paying too much tax at some stages.  

Non-cumulative tax codes are often referred to as ‘W1/M1’ or ‘Week 1/Month 1’ bases. Unlike cumulative codes, these do not take into account income or tax paid from previous periods within the tax year.

How do you identify Week 1 and Month 1 non-cumulative codes?

You can usually spot these codes by the ‘W1’, ‘M1’, or ‘X’ suffix (e.g. 1257L W1). The specific code used will determine how the tax is applied.

  • Mechanism: The system considers exactly 1/12th (or 1/52nd) of the annual allowance for that specific period only.

  • Isolation: It ignores previous pay or unused allowances.

  • Result: Employees may pay more tax in the short term as they cannot make use of unused allowances from previous periods.

What are the common triggers for non-cumulative codes?

Non-cumulative codes are often used on an emergency basis, typically when HMRC lacks sufficient information to set a cumulative one. This often happens when:

  • A new starter joins a job without providing a P45 immediately.

  • The employee’s tax affairs are under review by HMRC.

  • A temporary ‘pause’ is placed on tax history to prevent underpayment.

How do cumulative and non-cumulative tax code bases compare?

Feature Cumulative basis Non-cumulative (W1/M1) basis
Historical data Considers year-to-date earnings and tax paid Ignores previous pay periods completely
Adjustments Automatically refunds overpayments or collects underpayments No automatic adjustment for previous errors
Allowances Unused tax-free allowance rolls over to future periods Unused allowance is lost for that period
Stability Tax deductions smooth out over the year Deductions can fluctuate with variable pay
Accuracy Generally ensures correct total tax by year-end Often requires a year-end reconciliation (P800)

What is a practical example and how it affects pay?

To see this in practice, let’s use, as an example, John, who earns £300 per week. He works weeks 1-2, takes an unpaid break for weeks 3-4, and returns in week 5.

Scenario A: John is on a cumulative code

  • Weeks 3-4: John receives no pay, but his cumulative tax-free allowance continues to grow.

  • Week 5: His total accumulated earnings (£900) are lower than his accrued tax-free allowance (which now covers 5 weeks).

Result: The system recognises he technically overpaid earlier. John avoids paying tax in week 5 and receives a rebate.

Scenario B: John is on a non-cumulative code

  • Weeks 3-4: The system ignores the break.

  • Week 5: The system sees £300 wages and applies only one week’s allowance.

Result: John is taxed normally (approx. £11.60). He loses the benefit of the unused allowance from his break until reconciliation at the end of the tax year.

How should you manage code changes and year-end compliance?

With the UK government freezing personal allowance thresholds through to April 2028, staying compliant is vital in order to manage the effects of the fiscal drag. Whether your employees are in England, Wales, or Scotland, accurate application of codes (such as the 'S' prefix for Scottish rates or 'C' for Welsh) is critical, particularly when the tax rates differ.

How should you handle HMRC notices?

As an employer, you will frequently receive P6 (mid-year change) or P9 (start of tax year) notices instructing code changes (e.g. due to changes in company benefits, like the use of a company car, or medical insurance). Here’s what needs to happen:

  • Action: Apply these immediately.

  • Cumulative code: Your payroll software will recalculate the totals.

  • Non-cumulative code: The new rule must be applied moving forward only.

What are some common triggers of tax code changes?

To help you spot why a code might change, here are the most common triggers:

Reason Impact on tax code
Company benefits (e.g. car, medical insurance) Reduces tax-free allowance to collect tax on the benefit value
State pension Reduces allowance, as state pension is taxable but paid gross
Prior year underpayment Reduces allowance to collect unpaid tax in instalments
Professional expenses (e.g. uniforms, subscriptions) Increases allowance to give tax relief
Marriage allowance Changes allowance by transferring 10% to or from a spouse

Why are modern tools essential for UK SMEs in dealing with tax code changes?

Manually calculating cumulative adjustments is risky. The best solutions for UK SMEs handle these switch-overs automatically.

Using an HMRC compliant system ensures that, when a P6 notice arrives, all the relevant information updates instantly. This automation acts as a safeguard, flagging inconsistencies and ensuring statutory changes for the current tax year are applied without manual intervention. This allows you to focus on paying your people correctly, efficiently managing their benefits and workplace pension contributions, and growing the business, rather than manually wrangling Excel spreadsheets.

Rates & thresholds for 2025/26

Frequently asked questions (FAQs) about cumulative and non-cumulative tax codes

Here are some common questions managers ask about tax codes to help clarify the process:

This usually happens when an employee starts a new job and proper P45 information is missing, or if their tax affairs with HMRC are currently under review. It acts as a temporary holding position to prevent them from building up a tax debt, ensuring they pay roughly the correct tax until their full history is linked.

The number refers to the tax-free personal allowance. You typically multiply this by 10 to get the annual figure (e.g. 1257 means £12,570). The letter indicates their specific situation or region, such as ‘L’ for the standard allowance, ‘S’ for Scotland, or ‘C’ for Wales, which determines the exact tax rates applied.

If an employee has got more than one job, their full tax-free allowance is usually applied to their main job to guarantee efficiency. If they have got a second job, it is often taxed at the basic rate (BR code) or higher rate (D0 code) from the very first penny, as their allowance has already been used elsewhere.

No, an employer cannot manually change a tax code without official notification because doing so could create liability for underpaid tax. You must wait for an HMRC notification. However, employees can contact HMRC directly via their personal tax account to update their details, which will often trigger the release of a cumulative code much faster.

If they are on a cumulative code, explain that the system does this to correct an earlier overpayment automatically. By looking at their total earnings year-to-date against their accrued allowance on their payslip, they will see that the payroll software has calculated that they have paid too much previously (perhaps due to an unpaid break), and a rebate will therefore be issued to balance the books.

No, National Insurance is calculated strictly on a per-pay-period basis for almost all employees, meaning it is non-cumulative and does not look back at previous weeks. The only exception is for directors, who have a specific annual earnings period for NI that calculates liability on a cumulative basis over the year.