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

Support couples - complex version #50

Open
danielabar opened this issue Sep 15, 2019 · 0 comments
Open

Support couples - complex version #50

danielabar opened this issue Sep 15, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@danielabar
Copy link
Owner

Follow-on from #20 to improve accuracy of couples GIS amount:

Given that user has selected married or common-law as marital status, present two more input fields asking for current user's age and their spouse's current age. The differences in their respective ages matter when determining GIS because it guides which lookup table to use and for how many years. Lookup tables are as follows:

Table 1 - GIS for single, widowed or divorced person who receives an OAS pension
-> No spouse
Table 2 - Married or common-law OAS pensioner and spouse is also an OAS pensioner
-> Spouse is 65+
Table 3 - Married or common-law OAS pensioner and spouse is not an OAS pensioner
-> Spouse is below 60
Table 4 - Married or common-law OAS pensioner and spouse receives the Allowance
-> Spouse is 60 - 64

May need to re-think design of some charts, or make some assumptions that the Monthly and Annual charts represent first year of user receiving GIS.

Then for total lifetime of GIS chart, need to calculate "phases" as user and spouse go through the ages that would hit the different tables.

@danielabar danielabar added the enhancement New feature or request label Sep 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant