mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 15:14:02 -05:00
Closed
opened 2026-04-26 02:24:58 -05:00 by GiteaMirror
·
3 comments
No Branch/Tag Specified
master
claude/verify-migration-guardrails-i82c8m
cross-version-sync-stage2
api-browser-custom-data-dir
dependabot/npm_and_yarn/npm_and_yarn-cd62b4b37a
tabedzki/feat/replacing-month-picker-with-day-picker
delay-initial-sync-until-loaded
jfdoming/mobile-app-build
cross-version-sync-compat
jfdoming/api-tokens-part-1
jfdoming/api-tokens-part-2
jfdoming/api-tokens-part-3
jfdoming/mobile-app-updates
claude/budget-version-migration-compat-151jlr
claude/worker-error-serialization-9iqtl7
claude/react-table-library-research-afx83z
claude/issue-8401-regression-test-9nw9l3
jfdoming/mobile-app-foundation-part-1
jfdoming/mobile-app-scaffold
release
ai-fix-cleanup-def-8290
claude/relaxed-shannon-jusywa
claude/fervent-keller-s6f2fq
claude/determined-feynman-st1y9z
claude/wizardly-einstein-vi2wce
claude/sweet-albattani-7nseio
feat/bank-sync-per-budget-file
claude/affectionate-cannon-y0kc82
claude/dependabot-findings-m9pgmb
claude/mac-app-ios-publish-zjs1lz
claude/vigilant-tesla-aiiyos
depot-migrate-secrets-1781296330308
claude/quirky-cerf-v5qck7
claude/animation-removal-alternative-2etfh1
claude/netlify-preview-comments-consolidate-9XPYa
osc/7391-error-boundaries-reports
claude/pensive-dijkstra-7DYui
claude/server-app-version-mismatch-HTCGv
claude/pr-8027-review-feedback-mELuO
claude/zealous-wozniak-e5pO0
claude/intelligent-heisenberg-BSHJq
claude/translation-download-refactor-jFRsO
claude/mobile-performance-ideas-G9PAO
claude/github-issue-7988-5A5ly
blacksmith-migration-ff70d2d
claude/great-mayer-KRvOk
claude/react-native-ios-compilation-fcJh5
claude/serene-goldberg-58xv0
claude/kind-euler-LVG3K
release-automation/edge-nightly
7710-bundle-migrations
claude/fix-docker-build-error-WMfed
claude/llm-compatible-release-notes-t20Nr
7710-tests-tdd
cursor/transaction-table-rewrite-f077
claude/plan-ci-secure-context-OtEe1
claude/fix-issue-7667-DPXi3
cursor/resolve-pr-7449-ee11
claude/fix-typescript-build-error-JPtZ5
copilot/add-repository-configs-to-packages
worktree-compressed-drifting-ritchie
claude/api-consumer-verification-kfz1K
pr-7454
claude/fix-issue-7410-LLLQ4
revert-7281-generate-icons
react-query-useSchedules
copilot/sub-pr-6140
package-upgrades
v26.7.0
v26.6.0
v26.5.2
v26.5.1
v26.5.0
v26.4.0
v26.3.0
v26.2.1
v26.2.0
v26.1.0
v25.12.0
v25.11.0
v25.10.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.1
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.1
v25.2.0
v25.1.0
v24.12.0
v24.11.0
v24.10.1
v24.10.0
v24.9.0
v24.8.0
v24.7.0
v24.6.0
v24.5.0
v24.4.0
v24.3.0
v24.2.0
v24.1.0
v23.12.0
v23.11.0
v23.10.0
v23.9.0
v23.8.1
v23.8.0
v23.7.2
v23.7.1
v23.7.0
v23.6.0
v23.5.0
v23.4.2
v23.4.1
v23.4.0
v23.3.2
v23.3.0
v23.2.9
v23.2.5
v23.1.12
v22.12.9
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
Mirrored from GitHub Pull Request
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#42526
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mk-french on GitHub (Jan 10, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2210
Verified issue does not already exist?
What happened?
Is it just me or do the summary values make little sense when a category has rollover spend enabled in the 'Report budget'?
No rollover enabled - summary values are correct.

Rollover enabled on 'Food' and summary values are misleading?

I would expect the summary to show exactly what happened that month, as is shown in the group summary. I.e. What was spent = SUM of all category spends for that month. I can see how we get to -850 (250 + -1,100), it's offsetting the spend in the current month with the rollover balance, which to me doesn't really make sense.
Following that, the summary figures in Feb are also odd... $250 budgeted, $250 rolled over, $500 spent = balance of $0 (okay) but spend = $0 of $250?
I see this is because rollover is also enabled for Feb and the 0 floor is preventing the $-250 from summing up:
return carryover ? Math.max(0, safeNumber(number(budgeted) + number(sumAmount))) : sumAmount;Removing the rollover in Feb results in a more correct summary:

But the January rollover is excluded...
So where should the rollover be included? As a deduction on the spend in the subsequent month or an increase to the budget? Or perhaps neither - should it just remain in the balance column and not affect the summaries at all?
Thoughts?
What error did you receive?
No response
Where are you hosting Actual?
None
What browsers are you seeing the problem on?
No response
Operating System
None
@youngcw commented on GitHub (Jan 10, 2024):
In my opinion rollover should be disabled in report budget. The docs do say that this will happen, but it's still really confusing.
@mk-french commented on GitHub (Jan 19, 2024):
Ah yes! Is this what you're referring to @youngcw?:
Here's the effect on the summary expense (and therefore the saved amount) when rolling over:
Category Overspent - Entire expense is ignored in summary
Category Underspent - Expenses are decreased by the amount budgeted for that category
In both cases the balance is carried onto the balance of the next month, but does not affect the next month summary in any way...
Is this true to the docs? And more importantly, does it make sense to anyone?
I take your point that rollover in report budgeting is confusing but I do find it handy in some instances! It gives the ability to track a budget over a few months when the transactions are a bit more inconsistent.
Personally, in the summary I would like to see the expenses as it was in the month and any rollover just be carried onto the next months balance for that category. That makes the most sense to me... This way the summary is still accurate for that month and rollover affects only the rolling balance for that category.
@youngcw commented on GitHub (Oct 18, 2024):
Closing for now. I may add a ticket in the docs to make this more clear why the math is strange.