github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #8105] [Bug]: Incorrect starting balance when using bank sync with custom starting date #117671

New Issue
Open
opened 2026-06-11 13:07:18 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-06-11 13:07:18 -05:00
Owner
Copy Link

Originally created by @ItsThatDude on GitHub (Jun 5, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/8105

What happened?

When creating a new account via the link bank sync modal, if you select a custom start date from the drop down and leave the custom starting balance as the default (0), the starting balance will be incorrect

Expected: Selecting a starting date should not force the user to select a custom starting balance when linking via bank account - either we should pre-fill the starting balance field some how, or there should be a way to ignore this field when selecting a custom start date, with a checkbox or making it possible to remove the value instead of defaulting to 0.00 (or make it more obvious of this behavior if this is the desired functionality)

Actual: If the user doesn't enter a custom starting balance along with a custom starting date, the balance will be out of sync with what the bank reports

How can we reproduce the issue?

The below steps reproduce the issue:

  1. Go to Add Account, Set up bank sync
  2. Click Link bank account
  3. On a bank account, click Set up bank sync and choose Create new account
  4. In the starting date, select a different date to the default, but leave starting balance alone
  5. Click Link Accounts
  6. When the Actual syncs with the bank provider, the balance will be wrong

However it works correctly with the below steps:

  1. Go to Add Account, Set up bank sync
  2. Click Link bank account
  3. On a bank account, click Set up bank sync and choose Create new account
  4. Leave both custom starting date and starting balance alone
  5. Click Link Accounts
  6. When the Actual syncs with the bank provider, the balance will be correct

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @ItsThatDude on GitHub (Jun 5, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/8105 ### What happened? When creating a new account via the link bank sync modal, if you select a custom start date from the drop down and leave the custom starting balance as the default (0), the starting balance will be incorrect Expected: Selecting a starting date should not force the user to select a custom starting balance when linking via bank account - either we should pre-fill the starting balance field some how, or there should be a way to ignore this field when selecting a custom start date, with a checkbox or making it possible to remove the value instead of defaulting to 0.00 (or make it more obvious of this behavior if this is the desired functionality) Actual: If the user doesn't enter a custom starting balance along with a custom starting date, the balance will be out of sync with what the bank reports ### How can we reproduce the issue? The below steps reproduce the issue: 1. Go to Add Account, Set up bank sync 2. Click Link bank account 3. On a bank account, click Set up bank sync and choose Create new account 4. In the starting date, select a different date to the default, but leave starting balance alone 5. Click Link Accounts 6. When the Actual syncs with the bank provider, the balance will be wrong However it works correctly with the below steps: 1. Go to Add Account, Set up bank sync 2. Click Link bank account 3. On a bank account, click Set up bank sync and choose Create new account 4. Leave both custom starting date and starting balance alone 5. Click Link Accounts 6. When the Actual syncs with the bank provider, the balance will be correct ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the bugneeds info labels 2026-06-11 13:07:19 -05:00
GiteaMirror commented 2026-06-11 13:07:19 -05:00
Author
Owner
Copy Link

@coderabbitai[bot] commented on GitHub (Jun 5, 2026):

🔗 Related PRs

actualbudget/actual#7930 - [AI] Fix off by one error in enable banking [merged]
actualbudget/actual#8006 - [AI] Fix bug when linking accounts [merged]

📝 Issue Planner

Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

  • Create Plan
🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

<!-- gh-comment-id:4636468166 --> @coderabbitai[bot] commented on GitHub (Jun 5, 2026): <!-- This is an auto-generated issue plan by CodeRabbit --> <details> <summary>🔗 Related PRs</summary> actualbudget/actual#7930 - [AI] Fix off by one error in enable banking [merged] actualbudget/actual#8006 - [AI] Fix bug when linking accounts [merged] </details> --- <details> <summary>📝 Issue Planner</summary> <sub>Check the box below or use the `@coderabbitai plan` command to generate an implementation plan and prompts that you can use with your favorite coding assistant.</sub> - [ ] <!-- {"checkboxId": "8d4f2b9c-3e1a-4f7c-a9b2-d5e8f1c4a7b9"} --> Create Plan </details> --- <details> <summary> 🧪 Issue enrichment is currently in open beta.</summary> You can configure auto-planning by selecting labels in the issue_enrichment configuration. To disable automatic issue enrichment, add the following to your `.coderabbit.yaml`: ```yaml issue_enrichment: auto_enrich: enabled: false ``` </details> 💬 Have feedback or questions? Drop into our [discord](https://discord.gg/coderabbit)!
GiteaMirror commented 2026-06-11 13:07:20 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jun 6, 2026):

👋 Is this for Enable Banking? Gocardless? Simplefin? ..

<!-- gh-comment-id:4639253591 --> @MatissJanis commented on GitHub (Jun 6, 2026): 👋 Is this for Enable Banking? Gocardless? Simplefin? ..
GiteaMirror commented 2026-06-11 13:07:20 -05:00
Author
Owner
Copy Link

@DanniJuhl commented on GitHub (Jun 8, 2026):

👋 Is this for Enable Banking? Gocardless? Simplefin? ..

This was the case for me using Enable Banking, originally thought it was due to some rounding as I'm using a different currency however this issue lead me straight to it.
Reproduced it using the steps above.

<!-- gh-comment-id:4651139084 --> @DanniJuhl commented on GitHub (Jun 8, 2026): > 👋 Is this for Enable Banking? Gocardless? Simplefin? .. This was the case for me using Enable Banking, originally thought it was due to some rounding as I'm using a different currency however this issue lead me straight to it. Reproduced it using the steps above.
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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug needs info
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#117671
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?