Skip to content

UK pensions after #1084: open rulings, residual gaps and the engine pieces #1069

Open

Description

@juaristi22

Status (16 October 2026)

This issue began as the plan for #1084 (work packages WP0 to WP7). #1084 merged on 2 October (fe4e38dfa) and delivered WP0 to WP5 and WP7's HBAI and reform-stability checks. Its measurements and rulings are in experiments/1069-uk-pensions-receipts.md, and the original plan is in this issue's edit history. The body now lists only what is still open.

Delivered since #1084

Open in microcosm

Rulings

  • Single ages (R3). WP2's 3% acceptance for single ages around State Pension age isn't met. Rule on the split (65, 66, 67–69), or bind the singles beside the five-year band.
  • SPI Table 3.8 contributions. Table 3.8 splits contributions by relief mechanism; the engine's columns split them by provider. Rule on binding the combined amounts against employee plus personal contributions.
  • Employer NICs relief at 15%. Confirm the restatement from 13.8%, which changes the rate alone.

Work

Blocked on policyengine-uk

Related

Done when

  • The three rulings are recorded.
  • The open microcosm items are bound, vendored or re-measured, with receipts.
  • The engine items are in the lock, and the WP7 DWP path has been run.

Activity

  1. juaristi22 commented on Oct 2, 2026

    @juaristi22
    CollaboratorAuthor

    #1084 is merged (fe4e38d). It delivered WP0–WP5 and WP7's HBAI and reform-stability checks; the measurements and rulings are in experiments/1069-uk-pensions-receipts.md. This issue stays open for what's left, most of which is blocked on policyengine-uk.

    Blocked on policyengine-uk

    • Set State Pension age from date of birth, including the rise to 67 policyengine-uk#1899 (open PR: State Pension age by date of birth, including the rise to 67). It blocks:
      • c0, microcosm's engine bump with the State Pension age migration. uk_runtime/frs_take_up.py reads gov.dwp.state_pension.age.{male,female}, which #1899 deletes.
      • The State Pension type boundary. Until then state_pension_type keys on age and sex. The 70–74 boundary zig-zags, and single ages 69–73 are off by 10–20%.
      • Two items of the engine follow-up below: the basic-to-new reclassification double count, and Additional State Pension uprated by CPI rather than the triple lock.
    • The engine follow-up PR (WP6), to be filed after #1899. Four of its items are drafted locally; nothing is filed yet. The items:
      • Reforms of triple-lock inputs propagate.
      • The Pension Credit FY2025-26 rates and the guarantee's uprating rule. Until then Pension Credit calibrates at the engine's current FY2025-26 values, which WP3 wanted corrected first.
      • The April 2027 rate.
      • A guard against datasets that carry a state_pension column.
      • The two #1899-dependent items above, and the income-tax easement switch (decision 10).
    • Model Winter Fuel Payment high-income recovery separately from entitlement policyengine-uk#1760 (Winter Fuel Payment recovery above £35,000). Until it lands, DWP's 11.0m recipients stay a diagnostic.
    • Pension Age Disability Payment isn't modelled in the engine, and there is no engine issue yet. So Attendance Allowance in Scotland isn't bound.
    • WP7's DWP path, the baseline State Pension and Pension Credit against DWP's forecast to FY2030-31, runs after the engine follow-up.

    Open in microcosm, not blocked on the engine

    Of the decisions listed above, 9 (the Pension Credit guarantee after 2026) and 10 (the easement switch) belong to the engine follow-up; the plan ruled the rest.

  2. changed the title [-]UK pensions: calibrate State Pension, Pension Credit and pension contributions to the resident administrative facts (PolicyEngine/chronicle#305), pin the State Pension age boundary, fix the pension spine stages, and the engine pieces a State Pension uprating analysis needs[/-] [+]UK pensions after #1084: open rulings, residual gaps and the engine pieces[/+] on Oct 16, 2026
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