Conversation
UC Regs 2013 reg 66(1)(a) counts retirement pension income as unearned income, and reg 67(1) gives it the State Pension Credit Act 2002 s.16 meaning, which includes the new State Pension (s.16(1)(za)) and the Category A/B retirement pension (s.16(1)(a)). UC unearned income counted state_pension from the first calculated UC (0e2d8be, 2020) until 055dce8 (2021-10-27) dropped it in a UC restructure; since then the list has had private pension income but not State Pension, so mixed-age couples on UC had their State Pension ignored. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Hypothesis properties: UC is non-increasing in State Pension; with no earnings it falls pound for pound (reg 22(1)(a)); State Pension counts exactly like private pension income, and like property income when the family has no earnings. A strict xfail pins #1942, where the benefit unit's tax on State Pension is deducted from a partner's earnings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ncome uc_earned_income subtracted benunit_tax, the whole benefit unit's income tax and NI on all income, from the unit's gross earnings. UC Regs 2013 reg. 55(5)(b) and reg. 57(2) step 3 deduct only tax and NI paid by the person in respect of their employment or trade. - uc_income_tax_on_earnings: income tax on the person's earnings, taken as the lowest slice of their non-savings income after their allowances (savings and dividends sit above it under ITA 2007 s. 16, property income above it in the engine and under s. 16A from 2027-28). - uc_national_insurance_on_earnings: Class 1 employee, Class 2, Class 4. - uc_individual_earned_income: gross earnings less the person's own pension contributions, tax and NI, floored at nil. - uc_earned_income: sum over the unit, less the work allowance. Fixes #1942. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- test_uc_earnings_deductions_properties.py: unearned income never changes earned income; UC is non-increasing in every kind of unearned income; the tax deducted equals the tax on earnings alone; earned income is never lower, and UC never higher, than under the pre-fix formula. - test_uc_state_pension_properties.py: the #1942 strict xfail now passes and loses its marker; pound-for-pound and the property-income equivalence cover families with earnings; a new strict xfail pins the Marriage Allowance transfer, which the model books on the recipient as the transferor's unused allowance (ITA 2007 s. 55B gives a fixed reduction). - Document the earnings deductions in the UC docs page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The transferor's election cuts their own personal allowance by the fixed transferable amount (s.55B(4)-(6)); the gaining party gets a Step 6 tax reduction at the basic or Scottish basic rate, capped at their Step 5 tax (s.55A(2), s.55B(1), (3), s.29(2)). The couple elects only when the conditions in s.55B(2) and s.55C(1)(b)-(c) hold, no married couple's allowance is claimed, it lowers their combined income tax, and the elder spouse's take-up draw is true. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…roperties YAML cases from ITA 2007 ss.55A-55E, hand-computed, including the issue's worked example and each departure it lists. The State Pension and earnings-deduction UC properties now run with Marriage Allowance claimed, holding each couple's election at its first-run choice; the strict xfail on the partner's Marriage Allowance now passes, and a new case pins the point where the couple stops electing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ential The couple's tax never rises with the model's election, which matches the cheapest allowed option found by running each election fixed; the gaining partner's reduction does not depend on the elector's income; transfers balance and reductions stay within s.55B(1)/(3) and s.29(2); couple tax never falls with more income. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The dataset draws would_claim_marriage_allowance independently per person at 50%. Reading the elder spouse's draw reshuffled take-up across about 0.65m couples on the Enhanced FRS for no legal reason. The gaining spouse's draw is the one that decided take-up before, so the same couples claim. Also add the changelog fragment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…est comments s.55B(2)(ba) asks whether dividends would reach the dividend upper rate, which starts at the basic rate limit (s.13); the dividends scale's own threshold lags it before 2026-27. State the married premise in the UC property tests, and correct the comments on why the couples do not elect. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The tie case no longer asserts income tax, which depended on the model's fixed allowance order rather than s.25(2). The married couple's allowance case uses spouses old enough to claim it. The ordering case cites s.27(2) and s.29(2)-(3); the limit notes s.27(6) for double taxation relief; the single election per couple is described as a modelling choice, since s.55E does not bar elections both ways. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e rate test s.16 puts dividends above property income as well as earnings, so a landlord whose dividends cross the basic rate limit is liable at the dividend upper rate (s.55B(2)(ba)). Note that a spouse outside the benefit unit is not modelled. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Resolve the election-independent income tax inputs before branching, so a reform that branches inside adjusted_net_income gives the same result whichever variable is asked for first, and free the branch arrays afterwards. Only a spouse can give allowance up, and spouses must be old enough to marry (16, the Scottish minimum). On a tie the lower-income spouse elects. The CPS expanded reform lifts the income condition only when remove_income_condition is set. Refresh stale comments. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…riage Allowance The locked policyengine-uk predates PolicyEngine/policyengine-uk#1963. A lock bump changes the dataset build, so it belongs in its own release. The test runs as soon as the installed model defines marriage_allowance_relinquished. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Heads-up from #1949, which this stacks on: its head moved from d0fc22f to 514132f with one added commit and no history rewrite. The commit changes two lines in |
|
Update from #1949: its head is now c98c53c, a merge of #1943's new head ce85220, which has main 7b9fc37 merged in. No history rewrite and no formula change. Rebasing or merging onto c98c53c brings in current main, so this PR's impact base moves too. The one conflict #1949 had was the UC docs means-test sentence. |
Fixes #1947.
Stacks on #1949 (the #1942 fix, which stacks on #1943). The base is
mainso CI runs, and the diff includes #1943 and #1949 until they merge.What the law says and what changes
ITA 2007 ss. 55A-55E (legislation.gov.uk, read 2026-09-30; verbatim text in the issue):
would_claim_marriage_allowancewould_claim_marriage_allowance, so each couple has one draw (the dataset draws it per person at 50%, so take-up stays at 50%)The rate test reads the model's own liabilities. Two points follow from the statute's wording:
Scottish savings and dividends are banded on UK rates, so an intermediate-rate Scottish taxpayer with savings stays eligible. The old band test made them ineligible.
Variables
New, all Person, YEAR:
marriage_allowance_transferable_amount: s. 55B(4)-(5).is_marriage_allowance_spouse: the two eldest married members of a benefit unit that has exactly two. This also works before Replace generic child and adult flags with each programme's legal definitions #1896 lands, whilemarital_statusstill marks children in a married benefit unit as married.makes_marriage_allowance_election: the couple's choice; users can set it as an input.marriage_allowance_relinquished: s. 55B(6).marriage_allowance_appropriate_percentage: s. 55B(3).marriage_allowance_tax_reduction_limit: s. 29(2)-(3).marriage_allowance_tax_reduction: s. 55B(1). Added toincome_tax_subtractions.Changed:
marriage_allowanceis now the amount received from the spouse's election, and only the gaining spouse has it. It no longer comes off taxable income: it was removed fromearned_taxable_income_exclusions.personal_allowancesubtractsmarriage_allowance_relinquished.meets_marriage_allowance_income_conditionsis the rate test above.Removed:
partners_unused_personal_allowance: it is not part of the law and nothing else used it.eligible_bandsparameter.The CPS expanded-MA contrib reform now overrides
meets_marriage_allowance_income_conditionsandmarriage_allowance_transferable_amount. Its mechanics follow the statute, so a higher-rate recipient saves the basic rate × the amount, not their marginal rate.How the election is computed
The election depends on the couple's tax with and without it, and the tax depends on the election. So
makes_marriage_allowance_electionruns two policyengine-core branches, the pattern PE-US uses for itemisation:For each spouse, the saving from electing is the partner's reduction (capped at their Step 5 tax left) minus the elector's extra tax. It is rounded to pennies. The couple elects if the saving is positive and the conditions hold. The spouse with the larger saving elects; on a tie, the elder. Branches are dropped after use.
Overhead: ~20% on small household simulations (noisy, on a loaded machine). Enhanced FRS: see below.
Universal Credit
uc_income_tax_on_earnings(from #1949) takes the recipient's reduction off the tax on their earnings first. That is how HMRC delivers it: gov.uk's tax code letters say code M means "you've received a transfer of 10% of your partner's Personal Allowance". So a pensioner's State Pension no longer changes the earning partner's UC earned income once the couple has elected. The strict xfailtest_state_pension_does_not_change_partners_marriage_allowancenow passes.Other Step 6 reductions (married couple's allowance,
other_tax_credits) keep #1949'smin(tax, income_tax), which sets them against other income first. That is the opposite order, and a comment says so. Married couple's allowance needs a birth before 6 April 1935, so it almost never reaches UC.Known interaction (intended): the election weighs the couple's income tax, not their UC. At the point where electing stops saving tax, the couple stops electing. The earner's tax then rises by up to £252, and their UC rises by up to 55% of that.
test_couple_stops_electing_when_it_no_longer_saves_taxpins an example: 2026, State Pension £12,500 → £12,600, UC £5,509.26 → £5,547.86. A choice rule that also weighed UC would behave differently; that is a separate modelling decision.Departures in the issue, each now a YAML test
Also covered:
meets_marriage_allowance_income_conditions.yamlis rewritten on incomes, not tax-band inputs. It includes s. 55C(1)(c) with the cut allowance (50,000 earnings: eligible with the full allowance, ineligible once it falls to 11,310).Invariants and property tests
test_marriage_allowance_properties.py(Hypothesis). It generates couples and singles with every taxable income type, in England, Wales and Scotland, with children and occasional married couple's allowance claims, for 2019, 2026 and 2027:UC properties now run with Marriage Allowance claimed.
test_uc_state_pension_properties.pycovers pound-for-pound, non-increasing, and the private-pension and property-income equivalences.test_uc_earnings_deductions_properties.pycovers invariants 1-3; the old docstrings said these "switch Marriage Allowance off until this is fixed". Where a property compares two runs, each couple's election is held at its first-run choice, because the election legitimately responds to income.Mutation testing of these tests is running; results will be added here before the PR leaves draft.
Enhanced FRS impact
Real
Microsimulationruns on a private copy of the Enhanced FRS 2024-25 (enhanced_frs_2024_25.h5, sha256e433e532…). Base is #1949's head d0fc22f and head is this branch (a1a4822); both trees were clean. There are 4 runs per year: base, head, and each with no one claiming (would_claim_marriage_allowancefalse for all). £m, head minus base:"MA cost" is income tax with no one claiming minus income tax as modelled. Housing Benefit and CTR move by less than £0.01m. Poverty rates (BHC and AHC; all, children, pensioners, working age) are unchanged to 0.001pp in 2026 and 2027, and move by at most 0.011pp in other years.
Differential check: with no one claiming, base and head agree exactly on all 32 recorded person, benefit-unit and household arrays in every year. So this changes nothing but Marriage Allowance.
2026 decomposition (aggregates only):
Take-up: the dataset draws
would_claim_marriage_allowanceper person at 50%. The couple's election uses the gaining spouse's draw, the same draw that decided take-up before. A first version used the elder spouse's draw. That reshuffled take-up across ~0.65m couples for no legal reason, so it was dropped; those runs are kept in the review folder.Runtime: the election's branches add about 0.4–1 s per year to a full Enhanced FRS run, on a heavily loaded machine.
Not modelled
The rate test inherits the model's own income tax stacking. Chips filed for pre-existing bugs found on the way:
Axiom
axiom: TheAxiomFoundation/rulespec-uk#362 queued (s.55C, extended for this PR with s.55C(1)(ca) and s.55B(2)(ba) and seven more companion cases) + the s.55B re-encode queued in rulespec-uk
bulk/worklist.yaml(batch PE-UK-CHILD-DEFS, pending), which already requires the fixed transferable amount, the s.55B(6) cut and the s.55B(1) reduction.rulespec-uk's s.55B module still caps the transfer at the partner's unused allowance: it encoded the same departure as PolicyEngine. The worklist entry and #362 both called the PolicyEngine side "a separate follow-up"; this is it.
Review
Independent verification (hand computation from the statute, adversarial law and robustness reviews) is running; results will be added before this leaves draft.
🤖 Generated with Claude Code