State Pension in the enhanced FRS 2024-25 is well below both the FRS's own grossed estimate and DWP's administrative figures, in the data year itself. Found while fixing PolicyEngine/policyengine-uk#1921 (PolicyEngine/policyengine-uk#1922); part of PolicyEngine/policyengine-uk#1632.
Figures, 2024-25
|
Recipients |
Mean weekly amount |
Total |
| PolicyEngine UK on the enhanced FRS 2024-25 (policyengine-uk-data-private 1.57.4, snapshot ace89433), UK |
11.36m |
£201.6 |
£119.0bn |
| FRS grossed estimate, tables M.6a/M.6b |
11.53m |
£212 |
|
| DWP administrative, same tables |
11.88m |
£212 |
|
| FRS admin-linked grossed estimate, UK (transformation tables, sheet 16) |
|
|
£130.6bn |
| DWP administrative estimate, UK (same sheet: GB £131.6bn + NI £3.5bn) |
|
|
£135.1bn |
The model row is the weighted sum of state_pension_reported in the data year (equal to state_pension in 2024-25) and the weighted count of people with state_pension > 0.
Sources:
So the FRS itself gets within about 3% of DWP. The enhanced FRS is £11.6bn below the FRS's own UK estimate, with both fewer recipients and a lower mean amount.
Where to look
datasets/frs.py (origin/main b45c373, lines 1151-1182) sets state_pension_reported to the BENEFITS table's benamt for benefit code 5, times WEEKS_IN_YEAR. Check whether that is the admin-linked amount in the 2024-25 FRS, and whether other State Pension-type codes (e.g. Graduated Retirement Benefit, or a separate additional pension code) are missed.
- On the Survey of Personal Incomes donor rows (the zero-weight copy that calibration can upweight),
state_pension_reported is overwritten by a second-stage QRF: it is in FRS_ONLY_PERSON_VARIABLES (datasets/imputations/frs_only.py:85, tag 1.57.4), applied by impute_frs_only_variables from imputations/income.py. Compare the recipient count and mean amount on those rows with the FRS rows after calibration.
- Compare weighted recipient counts and mean amounts before and after calibration, to split the £11.6bn into weights and amounts.
- Check which State Pension calibration target is used, if any (
storage/tax_benefit.csv has an OBR March 2024 row).
State Pension in the enhanced FRS 2024-25 is well below both the FRS's own grossed estimate and DWP's administrative figures, in the data year itself. Found while fixing PolicyEngine/policyengine-uk#1921 (PolicyEngine/policyengine-uk#1922); part of PolicyEngine/policyengine-uk#1632.
Figures, 2024-25
The model row is the weighted sum of
state_pension_reportedin the data year (equal tostate_pensionin 2024-25) and the weighted count of people withstate_pension> 0.Sources:
So the FRS itself gets within about 3% of DWP. The enhanced FRS is £11.6bn below the FRS's own UK estimate, with both fewer recipients and a lower mean amount.
Where to look
datasets/frs.py(origin/main b45c373, lines 1151-1182) setsstate_pension_reportedto the BENEFITS table'sbenamtfor benefit code 5, timesWEEKS_IN_YEAR. Check whether that is the admin-linked amount in the 2024-25 FRS, and whether other State Pension-type codes (e.g. Graduated Retirement Benefit, or a separate additional pension code) are missed.state_pension_reportedis overwritten by a second-stage QRF: it is inFRS_ONLY_PERSON_VARIABLES(datasets/imputations/frs_only.py:85, tag 1.57.4), applied byimpute_frs_only_variablesfromimputations/income.py. Compare the recipient count and mean amount on those rows with the FRS rows after calibration.storage/tax_benefit.csvhas an OBR March 2024 row).