Matthew Katzen

I see that you've made the rent assistance an annual payment if you have an fy.year input but fortnightly if you have a Date input. I can see the logic...

Eligibility criteria for rent assistance should be handled within parent payment function http://guides.dss.gov.au/guide-social-security-law/3/8/1/10 Most notably the criteria for young single payment receivers http://guides.dss.gov.au/guide-social-security-law/3/8/1/104

Decided to make note in rent parameter regarding the board and lodging payments http://guides.dss.gov.au/guide-social-security-law/3/8/1/70 Also decided to add a logical argument to RA for the sharer's provision http://guides.dss.gov.au/guide-social-security-law/3/8/1/110

Do you think model_rent_assistance should take params fy.year and date? It kind of goes against the point of modelling your own values but it will make comparisons between the model...

Note that currently the functions takes rates at a constant amount, however rates are recalculated every quarter or so

Note that `Prop_rent_paid_by_RA`, `Max_rate`, and `Min_rent` are constant across all demographics which is not realistic. Perhaps have a dt input of all modelling params

26: - Age pension (http://guides.dss.gov.au/guide-social-security-law/5/2/2/10, table 2 note D)

Getting started on youth_allowance now. Is there any preference for if_else() over if(){...}else(){...}? I find the second way much easier to understand and edit.

OK. I can see how that would be helpful if you wanted to pass multiple individuals through the function at once.

Same goes for the income test. Adjusting from a reduction of $0.50 to $0.25 for each member in a couple