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

[Bug]: Splitting a future Scheduled transaction via Rules will cause it to be double-counted in Running Balance #1446

New Issue
Closed
opened 2026-02-28 19:43:46 -06:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-02-28 19:43:46 -06:00
Owner
Copy Link

Originally created by @ToniCipriani on GitHub (Sep 26, 2024).

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

If a future transaction is being split by a rule, it will cause it to be double-counted in the running balance display.
image
image
image

In this transaction, the Payment amount is subtracted twice from the running balance. In the above example, It should be 10000 - 752.22 = 9247.78, not 8495.56 = (10000 - 752.22 x 2).

To reproduce the issue:

  1. Create a scheduled future transaction
  2. Add a rule to pick up the said transaction to perform a split
  3. Enable the Running Balance

Test budget attached:
2024-09-25-Test Budget.zip

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome, Microsoft Edge

Operating System

Windows 10

Originally created by @ToniCipriani on GitHub (Sep 26, 2024). ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? If a future transaction is being split by a rule, it will cause it to be double-counted in the running balance display. ![image](https://github.com/user-attachments/assets/c838e648-fd9b-43dc-9de3-7b9eba32e3cd) ![image](https://github.com/user-attachments/assets/ca2e2183-198e-42fa-8302-e0ffaa3c4cde) ![image](https://github.com/user-attachments/assets/528e3033-462a-4a86-bb39-eaa97ce23adf) In this transaction, the Payment amount is subtracted twice from the running balance. In the above example, It should be 10000 - 752.22 = 9247.78, not 8495.56 = (10000 - 752.22 x 2). To reproduce the issue: 1. Create a scheduled future transaction 2. Add a rule to pick up the said transaction to perform a split 3. Enable the Running Balance Test budget attached: [2024-09-25-Test Budget.zip](https://github.com/user-attachments/files/17140824/2024-09-25-Test.Budget.zip) ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome, Microsoft Edge ### Operating System Windows 10
GiteaMirror added the split transactionsbug labels 2026-02-28 19:43:46 -06:00
GiteaMirror commented 2026-02-28 19:43:47 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Dec 7, 2024):

Can this be closed?

@youngcw commented on GitHub (Dec 7, 2024): Can this be closed?
GiteaMirror commented 2026-02-28 19:43:47 -06:00
Author
Owner
Copy Link

@ToniCipriani commented on GitHub (Dec 7, 2024):

Not fixed yet as of 24.12.0.

image

Running Balance should be 7743.34 if including the future transaction.

Or is this only fixed on Edge?

@ToniCipriani commented on GitHub (Dec 7, 2024): Not fixed yet as of 24.12.0. ![image](https://github.com/user-attachments/assets/9c218441-4ecd-4164-9564-09ee66081b15) Running Balance should be 7743.34 if including the future transaction. Or is this only fixed on Edge?
GiteaMirror commented 2026-02-28 19:43:48 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Dec 7, 2024):

Oh, I missunderstood the comments in the other ticket. I think there is an open PR still that should help.

@youngcw commented on GitHub (Dec 7, 2024): Oh, I missunderstood the comments in the other ticket. I think there is an open PR still that should help.
GiteaMirror commented 2026-02-28 19:43:48 -06:00
Author
Owner
Copy Link

@kcollett commented on GitHub (Jan 16, 2025):

I'm seeing this issue with v25.1.0. This bug is irritating because it ruins the ability to have an idea of what future balances will be in the relevant account.

@kcollett commented on GitHub (Jan 16, 2025): I'm seeing this issue with v25.1.0. This bug is irritating because it ruins the ability to have an idea of what future balances will be in the relevant account.
GiteaMirror commented 2026-02-28 19:43:48 -06:00
Author
Owner
Copy Link

@ToniCipriani commented on GitHub (Jan 16, 2025):

The fix seemingly didn't make it into the 25.1 release for some reason.

PR is #3897 but I don't see it in the release notes. Perhaps next month?

@ToniCipriani commented on GitHub (Jan 16, 2025): The fix seemingly didn't make it into the 25.1 release for some reason. PR is #3897 but I don't see it in the release notes. Perhaps next month?
GiteaMirror commented 2026-02-28 19:43:48 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jan 16, 2025):

The fix seemingly didn't make it into the 25.1 release for some reason.

PR is #3897 but I don't see it in the release notes. Perhaps next month?

Thats a bug report not a PR

@youngcw commented on GitHub (Jan 16, 2025): > The fix seemingly didn't make it into the 25.1 release for some reason. > > PR is [#3897](https://github.com/actualbudget/actual/issues/3897) but I don't see it in the release notes. Perhaps next month? Thats a bug report not a PR
GiteaMirror commented 2026-02-28 19:43:49 -06:00
Author
Owner
Copy Link

@ToniCipriani commented on GitHub (Jan 20, 2025):

My mistake, I misread.

@ToniCipriani commented on GitHub (Jan 20, 2025): My mistake, I misread.
GiteaMirror commented 2026-02-28 19:43:49 -06:00
Author
Owner
Copy Link

@kcollett commented on GitHub (Feb 1, 2025):

Oh, I missunderstood the comments in the other ticket. I think there is an open PR still that should help.

So what is the open PR? (I did a couple of searches but could not find anything obvious.)

@kcollett commented on GitHub (Feb 1, 2025): > Oh, I missunderstood the comments in the other ticket. I think there is an open PR still that should help. So what is the open PR? (I did a couple of searches but could not find anything obvious.)
GiteaMirror commented 2026-02-28 19:43:49 -06:00
Author
Owner
Copy Link

@atopley commented on GitHub (Feb 10, 2025):

Apologies for the confusion - bug report #3897 that @ToniCipriani referred to was raised by me as an unintentional duplicate of this bug report #3508.

The outstanding PR that contains the fix for this issue is #3708.

@atopley commented on GitHub (Feb 10, 2025): Apologies for the confusion - bug report #3897 that @ToniCipriani referred to was raised by me as an unintentional duplicate of this bug report #3508. The outstanding PR that contains the fix for this issue is #3708.
GiteaMirror commented 2026-02-28 19:43:50 -06:00
Author
Owner
Copy Link

@kcollett commented on GitHub (May 11, 2025):

I'm pleased to report that this appears to be fixed in 25.5.0.

@kcollett commented on GitHub (May 11, 2025): I'm pleased to report that this appears to be fixed in 25.5.0.
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 split 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#1446
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?