Skip to content

fix(budget): cherry-pick VAT storage semantics fix to beta (#1387)#1388

Closed
steilerDev wants to merge 0 commit intobetafrom
fix/vat-cherry-pick-beta
Closed

fix(budget): cherry-pick VAT storage semantics fix to beta (#1387)#1388
steilerDev wants to merge 0 commit intobetafrom
fix/vat-cherry-pick-beta

Conversation

@steilerDev
Copy link
Copy Markdown
Owner

Summary

Cherry-pick of #1387 (hotfix merged to main) back to beta.

  • Removes the buggy /1.19 division in direct-mode toPayload — stored plannedAmount now equals exactly what the user entered
  • includesVat is now persisted for direct-mode budget lines (was always null), defaulting to true
  • Unit-mode save no longer bakes VAT into plannedAmount; VAT is applied at display/calculation time via the new effectivePlannedAmount() shared utility
  • DB migration 0031 converts existing unit-mode includes_vat=false lines from VAT-inclusive back to net amounts

Test plan

  • Quality Gates pass
  • Direct-mode budget line: enter €100 with "price includes VAT" → reloads as €100
  • Direct-mode budget line: enter €100 without "price includes VAT" → displays and totals as €119

🤖 Generated with Claude Code

@steilerDev steilerDev closed this Apr 29, 2026
@steilerDev steilerDev force-pushed the fix/vat-cherry-pick-beta branch from b1b5d6a to 30b6b2e Compare April 29, 2026 10:23
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.

1 participant