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

[Bug]: Starting Balance not created if other accounts create transfers #1312

New Issue
Open
opened 2026-02-28 19:40:07 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 19:40:07 -06:00
Owner
Copy Link

Originally created by @DaAwesomeP on GitHub (Aug 8, 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?

When syncing with SimpleFIN (and possibly others but not tested), the "Starting Balance" item is not created in an empty account if rules from other accounts create transfers to/from the empty account

Possible resolution: When syncing an account, the Starting Balance item should be created if all of the items in an account are transfers that originated to/from other accounts' items (or the account is otherwise empty).

To reproduce:

  1. Create some accounts with SimpleFIN (or possibly other sync/import methods I did not test)
  2. Rename them to Account 1 and Account 2 (this affects the order that they sync)
  3. Create a rule to mark an item in Account 1 as a transfer to Account 2 (rule is pre, match account 1, set payee to account 2)
  4. Delete all of the items in both accounts
  5. Click the sync all accounts button from the "All Accounts" page to add back all of the items
  6. Account 1 will sync fine and will have a Starting Balance. The rule will create transfers in the otherwise empty Account 2.
  7. After Account 1 finishes syncing, Account 2 will begin to sync and will not create the Starting Balance item because it already contains some items (the transfers from Account 1).

I discovered this while initially setting up my Actual installation. I syncing all of my accounts, then created a bunch of rules to mark all of the transfers, and then deleted everything so that when I synced again all of the duplicates would be resolved. The duplicates would only resolve if I first deleted everything before syncing.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @DaAwesomeP on GitHub (Aug 8, 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? When syncing with SimpleFIN (and possibly others but not tested), the "Starting Balance" item is not created in an empty account if rules from other accounts create transfers to/from the empty account Possible resolution: When syncing an account, the Starting Balance item should be created if all of the items in an account are transfers that originated to/from other accounts' items (or the account is otherwise empty). To reproduce: 1. Create some accounts with SimpleFIN (or possibly other sync/import methods I did not test) 2. Rename them to Account 1 and Account 2 (this affects the order that they sync) 3. Create a rule to mark an item in Account 1 as a transfer to Account 2 (rule is pre, match account 1, set payee to account 2) 4. Delete all of the items in both accounts 5. Click the sync all accounts button from the "All Accounts" page to add back all of the items 6. Account 1 will sync fine and will have a Starting Balance. The rule will create transfers in the otherwise empty Account 2. 7. After Account 1 finishes syncing, Account 2 will begin to sync and will not create the Starting Balance item because it already contains some items (the transfers from Account 1). I discovered this while initially setting up my Actual installation. I syncing all of my accounts, then created a bunch of rules to mark all of the transfers, and then deleted everything so that when I synced again all of the duplicates would be resolved. The duplicates would only resolve if I first deleted everything before syncing. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the bank syncbug labels 2026-02-28 19:40:08 -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 bank sync bug
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#1312
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?