Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix SSI Spousal Deeming: Correct Income Exclusion Order and FBR Comparison #5608

Open
mexi-cano opened this issue Feb 17, 2025 · 3 comments · May be fixed by #5615
Open

Fix SSI Spousal Deeming: Correct Income Exclusion Order and FBR Comparison #5608

mexi-cano opened this issue Feb 17, 2025 · 3 comments · May be fixed by #5615

Comments

@mexi-cano
Copy link

The current SSI spousal deeming calculation incorrectly processes household income for cases with an eligible disabled individual and an ineligible working spouse. The implementation combines household incomes before applying exclusions and does not properly compare against the Federal Benefit Rate (FBR) differential.

@MaxGhenis
Copy link
Contributor

Thanks @mexi-cano could you share a test case that we calculate incorrectly?

@mexi-cano
Copy link
Author

Thanks @mexi-cano could you share a test case that we calculate incorrectly?

Absolutely! Here are a few cases that show the incorrect SSI value returned for these types of households. I have a fix that I will PR shortly. Please let me know if you have any other questions

@mexi-cano
Copy link
Author

See PR for fix here

@mexi-cano mexi-cano changed the title Fix SSI Spousal Deeming: Correct Income Exclusion Order and FBR Comparison Fixes #5608 SSI Spousal Deeming: Correct Income Exclusion Order and FBR Comparison Feb 20, 2025
@mexi-cano mexi-cano changed the title Fixes #5608 SSI Spousal Deeming: Correct Income Exclusion Order and FBR Comparison Fix SSI Spousal Deeming: Correct Income Exclusion Order and FBR Comparison Feb 20, 2025
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 a pull request may close this issue.

2 participants