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

[GH-ISSUE #2361] [Feature] Option to not include future transactions when syncing bank accounts using GoCardless #70669

New Issue
Closed
opened 2026-05-16 08:58:38 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-16 08:58:38 -05:00
Owner
Copy Link

Originally created by @Waseh on GitHub (Feb 15, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2361

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

When syncing my bank accounts to Actual using the GoCardless integration transactions up to (about) 60 days in the future gets pulled into Actual. This results in the balance of the accounts in Actual not matching what is in fact the current real balance of the account as well as cluttering the transactions list with many future transactions.

While writing this feature request i also tested what would happen if I then deleted a future transaction in my bank and then synced with Actual. In my testing, deleting the future transaction in my bank and then syncing does not remove the transaction from Actual meaning that the accounts actually become out of sync and then having to remove the future transaction manually from Actual to restore parity between Actual and my bank account.

Describe your ideal solution to this problem

I would like the ability to choose not to import transactions in the future when using integrations that pull data directly from banks.
Some relevant discussion has been going on in #2354

Teaching and learning

I guess this option could be presented when setting up the bank synchronization.

Originally created by @Waseh on GitHub (Feb 15, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2361 ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? When syncing my bank accounts to Actual using the GoCardless integration transactions up to (about) 60 days in the future gets pulled into Actual. This results in the balance of the accounts in Actual not matching what is in fact the current real balance of the account as well as cluttering the transactions list with many future transactions. While writing this feature request i also tested what would happen if I then deleted a future transaction in my bank and then synced with Actual. In my testing, deleting the future transaction in my bank and then syncing does not remove the transaction from Actual meaning that the accounts actually become out of sync and then having to remove the future transaction manually from Actual to restore parity between Actual and my bank account. ### Describe your ideal solution to this problem I would like the ability to choose not to import transactions in the future when using integrations that pull data directly from banks. Some relevant discussion has been going on in #2354 ### Teaching and learning I guess this option could be presented when setting up the bank synchronization.
GiteaMirror added the needs votesfeature labels 2026-05-16 08:58:38 -05:00
GiteaMirror commented 2026-05-16 08:58:41 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 15, 2024):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

<!-- gh-comment-id:1945643031 --> @github-actions[bot] commented on GitHub (Feb 15, 2024): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
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 feature needs votes
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#70669
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?