Skip to content

UC deductions scale advance repayments with the standard allowance, but advances are recovered as fixed sums #2410

Open

Description

@MaxGhenis

What is wrong

uc_deductions is min(uc_deduction_rate × uc_standard_allowance, award − minimum payable) for every deduction type. So any change to the standard allowance moves every household's deductions in proportion, advance repayments included.

The law does not tie advance recovery to the standard allowance. Regulation 10 of the Social Security (Payments on Account of Benefit) Regulations 2013 (SI 2013/383) says a payment on account "is to be offset by the Secretary of State" "against the sum payable … under the award", or "is to be deducted" from it or a later award. What is recovered is the advance itself. No standard-allowance rate applies.

uc_deduction_rate documents its above-cap excess as covering last resort and child maintenance deductions. That excess also scales with the standard allowance. Whether child maintenance deductions are flat amounts in law is still to be checked.

Effect

For a reform or uprating that raises the standard allowance, the model raises advance repayments (and the above-cap excess) in proportion. That overstates how much deductions rise.

For a capped family, whose award the cap holds flat, it also overstates the fall in the payment net of deductions. A qualification check (population_uc_standard_allowance_plus_10) found exactly that pattern on full 1.58.1 data: 139 capped units with deductions saw their payment fall.

Deductions set as a percentage of the standard allowance in law are not affected:

Fix

Hold the advance component (and any fixed-sum component) at its baseline cash amount when the standard allowance changes. For example, store the advance part as an amount rather than a rate, and scale only the percentage-of-allowance types.

Add a test: raising the standard allowance leaves a household's advance repayment unchanged.

Related: #1814 (deductions model), uk-data#450 (imputing deduction attributes).

Activity

  1. MaxGhenis commented on Oct 14, 2026

    @MaxGhenis
    CollaboratorAuthor

    Adding scope, at the UK Budget CI coordinator's request.

    PolicyEngine/policyengine.py#614 restates W1's UC allowance contract check. It now asserts that no award before deductions falls, and that each payment change equals the award change less the deduction change. It does not check how much deductions rise, and it names this issue as the owner of deduction size. So please make the fix here include model tests for the Schedule 6 limits themselves (SI 2013/380 Sch 6):

    1. Percentage heads. The "5% of the standard allowance" deductions (paras 6(3), 8(4)(a), 9(6)(a), 11(4), 12(4)) scale with the standard allowance. The fixed-sum components do not: advances under SI 2013/383 reg 10 (this issue), and child maintenance once its legal form is confirmed.
    2. The overall cap. Para 4(1) still reads 40% of the standard allowance. Since 30 April 2025 the cap has been 15% administratively (the Fair Repayment Rate; EM to SI 2025/387 para 5.2), which cap.yaml already sets. Test that the deductions the cap limits never exceed the parameter, and that the para 4(3)–(4) exceptions (continuing-need fuel and water, housing costs, rent) are the only amounts above it.
    3. The one-penny floor. Para 3(1)(a) requires at least one penny to stay payable (reg 11(7) of SI 2013/384 for its own deductions). Test that universal_credit never goes below that floor when deductions are present.

    The legal reading is the UK hub's independent check: ~/reviews/uk-hub/reviews/uc-cap-deductions-ruling/review-opus.md.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions