Skip to content

Keep West Virginia 529 deductions separate from senior modifications - #10673

Draft
MaxGhenis wants to merge 7 commits into
mainfrom
wv-529-senior-modification
Draft

MaxGhenis wants to merge 7 commits into
mainfrom
wv-529-senior-modification

Conversation

@MaxGhenis

@MaxGhenis MaxGhenis commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

West Virginia residents who qualify for the senior or disability modification can deduct qualifying West Virginia 529 contributions without reducing that modification. This change removes contributions from the exclusions applied before the $8,000 senior cap, from the existing 2014 coverage boundary.

Filers deduct qualifying college-savings payments in addition to their subsection (c) modifications under W. Va. Code 11-21-12a. The Legislature lists the senior-cap offsets in section 11-21-12(c)(9), without college-savings contributions.

The Tax Division includes contributions on line 39 within the excluded range in box (c) of 2025 Schedule M, pages 5-6. Main follows that form calculation. This PR follows the statute for contributions and retains the existing exclusions for military pay and taxable state-tax refunds.

For example, a 66-year-old with $6,000 of wages who contributes $2,000 keeps a $6,000 senior modification, compared with $4,000 on main. With the separate contribution deduction, total subtractions reach $8,000, state AGI falls to -$2,000, and taxable income floors at zero. At $9,000 of AGI with the same contribution, the senior modification rises from $7,000 to $8,000.

Methodology choices

  • Follow CONTRIBUTING's statute-first source hierarchy. Under section 12a, filers can claim the additional deduction.
  • Retain 2014 as the existing model coverage boundary. The Legislature already authorized additional contributions in 2000 HB4679, page 3, and retained the senior provision in 2013 SB65, pages 6-7.
  • Deduct current-year contributions in full. PolicyEngine does not track the optional carryforward over up to five taxable years, beginning with the payment year, or optimize that election. State AGI can therefore fall below zero while taxable income stays nonnegative.
  • Record the contribution-specific statute/form choice in source_conflicts/candidates.yaml. Keep the existing broader income-base marker and register pin until post-merge registration. That follow-up also needs a capture of the page 5 contribution label.

Invariants and tests

  • Each eligible person's senior modification stays between zero and $8,000.
  • Changing a contribution by either spouse preserves both spouses' senior modifications.
  • Changing one spouse's excluded income receipt preserves the other spouse's modification.
  • Receipt-based subtractions preserve the existing income bound; separately deducted contributions can take total subtractions above AGI.
  • YAML cases cover senior and disabled contributors, both spouses, the cap, refunds, other modifications, 2014 coverage, and negative state AGI with zero taxable income.

Local validation passed five property tests, 24 senior-modification YAML cases, 11 claim-of-right YAML cases, 103 source-conflict checks, and formatting/lint. Restoring the old contribution exclusion in a scratch checkout failed the new property on the $6,000 versus $4,000 example; restoration matched the original hash.

The new property checks both spouses' contribution independence, which the existing receipt bound does not cover. Locked local runs took 707.556 seconds for a four-property comparison file and 456.185 seconds for the final five-property module, peaking at 1,110.359 and 1,109.563 MiB. Different import paths and host conditions prevent a performance comparison. The new property used 43.542 seconds of JUnit case time.

In the current main Linux CI baseline, the four properties summed 38.490 seconds. The entire 1,124-case group used 1,698.29 seconds and peaked at 7.707 GiB; those resources cover the whole group.

Additional main-changed core files are running separately under 4 GiB and 900-second caps. The accounting and head/spouse swap runs reached the time limit without test verdicts. Further core checks are still running.

Microsimulation impact

To be measured before merge.

Axiom parity

axiom: needed — the existing West Virginia resident pipeline excludes senior/disability facts, so its tests do not establish parity for this interaction.

🤖 Generated with Claude Code

MaxGhenis and others added 2 commits November 5, 2026 21:40
…ication

W. Va. Code 11-21-12a subtracts 529 and prepaid tuition contribution
payments "in addition to" the subsection (c) modifications of section
11-21-12. The senior citizen or disability modification now excludes
only income receipts (Schedule M lines 36 and 38) before its $8,000
cap, so a contribution no longer shrinks it. Schedule M box (c) counts
income not included in lines 35 to 46, a range that takes in the line
39 contribution; candidate us-wv:senior-modification-529-contribution
records the conflict.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MaxGhenis added a commit that referenced this pull request Nov 6, 2026
The senior citizen or disability modification keeps main's Schedule M
reading, in which the line 39 contribution reduces the income base.
The section 11-21-12a change, its tests and candidate
us-wv:senior-modification-529-contribution move to their own pull
request.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MaxGhenis and others added 4 commits November 14, 2026 21:32
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… reading

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MaxGhenis MaxGhenis changed the title Count West Virginia 529 contributions in addition to the senior modification Keep West Virginia 529 deductions separate from senior modifications Nov 15, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant