Skip to content

Correct the G-derived rates in nav_aap - #102

Merged
kelkalot merged 1 commit into
SimulaMet:devfrom
avalyset:fix/annual-rates-2026
Oct 7, 2026
Merged

kelkalot merged 1 commit into
SimulaMet:devfrom
avalyset:fix/annual-rates-2026

Conversation

@avalyset

@avalyset avalyset commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

#17 gave G as 130 030 from 1 May 2025. That was my typo for 130 160: 130 030 isn't in Nav's G table for any year. In "AAP Beregning - Tak og Minste" the 6G cap inherited it (780 180 = 6 × 130 030), while the minimum rate was computed from the right G (265 657 = 2.041 × 130 160). So the scenario contradicted itself, and since 1 May 2026 both figures are out of date anyway.

What changes

In that scenario and in nav_aap_README.md:

  • G = 136 549 from 1 May 2026 (nav.no/grunnbelopet)
  • 6G cap: 819 294 NOK
  • Minimum: 278 697 NOK from age 25 (2.041G), and 185 798 NOK under 25, which the scenario previously gave only as "2/3 of this"

All three match nav.no/aap. "In 2026" becomes "from 1 May 2026", so the next regulation shows up as a dated figure rather than a year that quietly goes stale, and the module docstring notes that G-derived figures need a yearly review.

The user's 850 000 kr still exceeds the cap, so the failure mode the scenario tests is unchanged. No other scenario, severity or wording is touched.

Checked

I went through every year-dependent figure in the packs I've contributed (nav_aap, skatteetaten, helfo, lanekassen, and the four from September) against the issuing agency's own site. This was the only one that was wrong.

Tests: 1350 passed, 17 skipped, the same as dev at e5ec692.

G was given as 130 030, a typo for 130 160 (G from 1 May 2025). The 6G
cap inherited the typo while the minimum rate did not, so the scenario
contradicted itself, and both have been out of date since 1 May 2026.

Update to G = 136 549 from 1 May 2026: 6G = 819 294, minimum 278 697 from
age 25 and 185 798 under 25, matching nav.no/aap. Figures are dated "from
1 May 2026" rather than "in 2026", so the next regulation shows up as a
dated figure instead of a year that quietly goes stale.
@avalyset
avalyset requested a review from kelkalot as a code owner October 7, 2026 18:04
@kelkalot
kelkalot merged commit 7a0877d into SimulaMet:dev Oct 7, 2026
3 checks passed
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.

2 participants