Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Universal Credit deductions

PolicyEngine UK models the money DWP takes off Universal Credit awards to repay debts: advance repayments, government debt (benefit and tax credit overpayments) and third party deductions such as utility arrears.

The implementation separates latent demand from the statutory cap. uc_latent_deduction_rate assigns deduction demand from the distribution DWP observed in March to May 2025 — the last full months under the 25% cap — and gov.dwp.universal_credit.deductions.cap applies the operational cap (40% to October 2019, 30%, 25%, then 15% under the Fair Repayment Rate from 30 April 2025) at runtime. Assigning observed post-cap rates directly would bake the cap into the data and make cap-raising reforms inexpressible.

Validation against DWP deductions statistics

Enhanced FRS 2023/24 v1.40.3, against DWP’s Universal Credit deductions statistics.

StatisticModelDWP published
Share of UC households with deductions47.0–47.1%46–47%
At-cap share, 25% regime (2024)13.4%13–14% (Mar–May 2025)
At-cap share, 15% regime (2025)26.4%21% (Jun 2025–Feb 2026)
Above-cap share (last resort)1.8%2%
Mean monthly deduction, 25% regime£66£67–68
Mean monthly deduction, 15% regime£50£51–54
Mean annual gain, 25%→15% cap£421£420 (gov.uk)
Households better off, 25%→15% cap1.01m~1.2m (gov.uk)

The pre-Fair-Repayment-Rate pileup at the cap and both regimes’ mean amounts reproduce without being separately fitted: the cap parameter generates them from the same latent distribution.

Limitations

These bound what the module can support. They are stated rather than tuned away.

Aggregates scale with the UC caseload

The model has 4.2m UC benefit units against roughly 7.2m administrative households, and correspondingly 1.9m deducting households and £1.2bn/year deducted against 3.3m and roughly £2.0bn/year in the administrative data. This is the model’s UC take-up and calibration gap, not a deductions artefact — per-household statistics validate precisely because the gap divides out. It is tracked in policyengine-uk-data#452.

The practical consequence: poverty headcounts and exchequer costs of a protected-floor or cap reform run low roughly in proportion to the caseload shortfall. Analyses replicating published floor estimates (such as JRF’s) should compare per-household gains and distributional shape, not totals.

The at-cap share under the 15% regime runs high

The model puts 26.4% of UC households at the 15% cap against 21% observed. The latent-demand model holds demand fixed while real deductions attrit under a lower cap through affordability requests and composition drift.

This has a direction. Reforms that lower the cap further overstate the number of constrained households and so overstate the gains from later raising it. Reforms that raise the cap toward 25% sit inside the observed window and are on firmer ground.

Only 2024 and 2025 are validated

The latent distribution is observed in 2025 and applied to all model years as a constancy assumption; published deductions statistics begin in March 2025. Simulations of years before 2021 apply a 2025-shaped demand distribution under the 40% and 30% caps then in force, which no published statistic can check. Treat pre-2024 deduction results as uncalibrated.

The protected floor binds on last resort deductions

The protected_floor lever limits combined deductions and benefit cap reductions to (1 − floor) × the standard allowance. It binds on the whole of uc_deductions, including the above-cap excess that current law exempts from the deductions cap (last resort and child maintenance deductions). JRF’s briefing does not say whether their floor exempts those categories — its worked example involves only cappable deductions and the benefit cap — so this is a modeling choice.

Other assumptions

Reform levers

# Return the cap to 25%:
{"gov.dwp.universal_credit.deductions.cap": {"2026-01-01.2030-12-31": 0.25}}

# Abolish government debt deductions only:
{
    "gov.dwp.universal_credit.deductions.abolish.government": {
        "2026-01-01.2030-12-31": True
    }
}

# JRF-style protected minimum floor at 85% of the standard allowance,
# binding on deductions and benefit cap reductions jointly:
{"gov.dwp.universal_credit.deductions.protected_floor": {"2026-01-01.2030-12-31": 0.85}}

A cap of 1 − x is equivalent to a protected minimum floor at x of the standard allowance for capped deduction types. The dedicated protected_floor lever additionally binds on benefit cap reductions, which is where most of JRF’s post-Fair-Repayment-Rate effect comes from.

Where the assignment lives

Statutory parameters — the cap, the protected floor, the minimum payable penny, the abolition switches — live under gov.dwp.universal_credit.deductions. The calibrated distributions live under gov.simulation.uc_deductions: they describe the world, not the law.

The assignment formulas are an explicit fallback. The end state imputes uc_latent_deduction_rate and uc_deduction_combination at dataset build, at which point the model consumes them as plain inputs and the fallback retires; raw-FRS users keep working through the fallback until then. Assignment uses deterministic splitmix64 hashes of benunit_id, reproducible across runs and machines, and overridable by datasets or situations through uc_deduction_random_draw and uc_deduction_type_random_draw. Every simulation built from data gets the hashed draws, including a constituency or local authority filtered from the national data, and a benefit unit gets the same draw there as in the national run. Household situations get no deductions unless set explicitly.