github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: Mobile running balance is incorrectly calculated on large accounts #2614

New Issue
Closed
opened 2026-02-28 20:21:34 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 20:21:34 -06:00
Owner
Copy Link

Originally created by @youngcw on GitHub (Nov 12, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

If an account has more than 500 transactions the running balance is incorrectly calculated on mobile. The issue is that the balance is calculated starting at the oldest transaction in the batch which may not be the first transaction in the account. The useTransactions hook has an option to calculate running balance from the top down, but that function is not used anywhere currently.

In the image below you can see that the balance at the top does not match the running balance for the most recent non-schedule transaction.

Image

@joel-jeremy

How can we reproduce the issue?

Enable running balance on an account with >500 transactions. View that account in the mobile view and see that the running balance for the most recent transaction doesn't match the account balance.

Where are you hosting Actual?

None

What browsers are you seeing the problem on?

No response

Operating System

None

Originally created by @youngcw on GitHub (Nov 12, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? If an account has more than 500 transactions the running balance is incorrectly calculated on mobile. The issue is that the balance is calculated starting at the oldest transaction in the batch which may not be the first transaction in the account. The `useTransactions` hook has an option to calculate running balance from the top down, but that function is not used anywhere currently. In the image below you can see that the balance at the top does not match the running balance for the most recent non-schedule transaction. <img width="430" height="315" alt="Image" src="https://github.com/user-attachments/assets/c822e350-fd9f-4369-a1d6-484f717745c3" /> @joel-jeremy ### How can we reproduce the issue? Enable running balance on an account with >500 transactions. View that account in the mobile view and see that the running balance for the most recent transaction doesn't match the account balance. ### Where are you hosting Actual? None ### What browsers are you seeing the problem on? _No response_ ### Operating System None
GiteaMirror added the transactionsbug labels 2026-02-28 20:21:34 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug transactions
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2614
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?