Update current CRA family benefits and model benefit-year/family boundaries
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 45/100
Direzione di ricerca
No files or test paths are named. Start by locating the existing CRA benefit parameter definitions and period/entity tests, then consult the linked CRA guidance. Done means updated metadata and parameters, benefit-year evaluation, zero-income handling, and tests for age bands, reductions, and multiple tax families.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem
PolicyEngine Canada's parameters for several CRA-administered family benefits
stop in older benefit years. Current July 2026 to June 2027 calculations cannot
be compared reliably with the engine:
- Canada Child Benefit
- Child Disability Benefit
- Ontario Sales Tax Credit
- Nova Scotia Affordable Living Tax Credit
There are also two output-contract differences that parameter updates alone do
not resolve:
- CRA publishes these benefits for a July-to-June benefit year using prior-tax-
year adjusted family net income, while PolicyEngine variables use a generic
calendar-year period. - CRA calculations apply to a tax family, while PolicyEngine Canada's benefit
variables use its co-residentHouseholdentity.
Scope
- Update amounts, thresholds, and reduction rates through the July 2026 to June
2027 benefit year. - Define how the July-to-June benefit year is requested and represented.
- Audit whether the existing household entity can represent the CRA tax-family
boundary; introduce or derive the appropriate unit if it cannot. - Floor adjusted family net income at zero where the CRA formula requires it.
Acceptance criteria
- Parameter metadata cites current CRA guidance and records the applicable
benefit year. - Tests cover children in both CCB age bands, CDB phaseout, and the Ontario and
Nova Scotia credit reductions. - Tests include a negative adjusted-family-net-income case.
- Tests include a co-resident household containing more than one tax family and
show that benefits are allocated to the correct family. - Outputs can be evaluated for the July 2026 to June 2027 benefit year without
treating it as an undifferentiated calendar year.
Official sources:
- https://www.canada.ca/en/revenue-agency/services/child-family-benefits/canada-child-benefit/how-much.html
- https://www.canada.ca/en/revenue-agency/services/child-family-benefits/child-disability-benefit.html
- https://www.canada.ca/en/revenue-agency/services/forms-publications/publications/rc4210/gst-hst-credit.html
- Lingua principale
- Python
- Stelle
- 17
- Fork
- 35
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di PolicyEngine/policyengine-canada
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
-
enhancement
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
-
enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 42/100
-
enhancement
Difficoltà 4/5 3-5 giorni Idoneità per principianti 52/100
-
enhancement
Difficoltà 4/5 3-5 giorni Idoneità per principianti 68/100
Tutte le issue di PolicyEngine/policyengine-canada
Issue simili
-
`burr` fails to start when the Python path has a space in itForse già presa @enekoreto l’ha presa oggi. Apertastatus/needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 5 giorni
-
gemini 出现了新的域名需要加入Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
-
Difficoltà 2/5 Mezza giornata Idoneità per principianti 72/100
debpalash/VoiceStudio#2903 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
dagster-io/community-integrations#367 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
aws-samples/sample-per-model-bedrock#243 ·
I maintainer di solito rispondono entro 1 giorno