mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-09 11:42:54 -05:00
[Bug]: Creating a new Linked Account does not always create a Starting Balance #2356
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2356
Reference in New Issue
Block 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 @atgrey24 on GitHub (Aug 5, 2025).
Verified issue does not already exist?
What happened?
In the discord, multiple users have been asking for help when their account balances to not match reality. The solution is usually that they do not have a Starting Balance transaction.
The workflow for creating a linked account never prompts the user for a start date or starting balance, and relies on the bank sync provider to handle this properly. The workflow should be updated to prompt the user for this information.
How can we reproduce the issue?
Bug #3218 seems related and describes one case where SimpleFIN fails to create a starting balance.
However, many users experiencing this issue use GoCardless, so there are other cases when this can happen.
Where are you hosting Actual?
Pikapods
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
Operating System
Windows 10
@youngcw commented on GitHub (Aug 5, 2025):
This seems like two separate things. A bug that needs a replication process, and then a feature request. Are there replication steps for the starting balance not getting created?
Can make a feature request for configurable starting dates if there isn't one already?
@atgrey24 commented on GitHub (Aug 5, 2025):
Sorry if this was the wrong place for it. I wasn't sure if gaps in the process were considered a bug or a new feature request. I don't have any replications steps other than that linked bug, as I haven't seen it myself and I don't have access to GoCardless. I've just seen a couple people in the discord get tripped up where it turns out they didn't have one.
I'll create this as a feature request instead
@matt-fidd commented on GitHub (Aug 6, 2025):
Maybe a different approach here would be to look for an existing "Starting Balance" transaction instead of just checking if an account is empty, it would fix the linked bug as well. Though, that would of course break if users changed the payee of the default transaction.
Maybe we should focus on the documentation instead. Adding a clear step to check the balance against your bank and add a starting balance transaction if needed might help to stem the issues in Discord.
@youngcw commented on GitHub (Aug 6, 2025):
I think that at some point we should rework the new account flow. It would be nice if the starting date could be set to something other than the current day. The starting balance could be set even if the user is connecting to a sync provider. Maybe if connecting to a sync provider the user only adds in the start date and the linking sets the starting balance.
@matt-fidd commented on GitHub (Aug 6, 2025):
True, there's a lot of work to do on the bank sync side. I keep meaning to set aside a week or two to refactor the whole lot, but I've been hoping plugins came first to make it a bit easier.
I like the idea of setting a start date. The 90 day limit is carried over from GoCardless too I believe, I don't think it's a problem for SimpleFIN and Pluggy.ai so there's scope to extend that too.
@youngcw commented on GitHub (Aug 6, 2025):
Waiting on plugins would make sense for a lot of that, but setting the start date would probably be fine to add now and it can get carried over to a plugin.
@atgrey24 commented on GitHub (Aug 6, 2025):
I included something like that as a possible solution in the feature request I made to replace this bug #5490. Feel free to close or remove this bug as you deem appropriate.
Not enough people actually read the documentation, at least not until after they have encountered a problem. Its probably still worth adding, but would be best to prevent the issue in the first place.