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

[Feature] automatic transfers on bank-sync based on matching amount/date #2763

New Issue
Closed
opened 2026-02-28 20:27:03 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 20:27:03 -06:00
Owner
Copy Link

Originally created by @enewbury on GitHub (Jan 2, 2026).

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?

My problem:
I have multiple credit cards from Chase. When I make a payment to any of the chase cards, the entry in my checking account is identical for each card. There is no way for me to identify which credit card account I am transferring to based on the transaction itself, so I cannot use the method described here to setup automatic transfers.

Describe your ideal solution to this problem

Ideally this would automatically detect the corresponding transaction in another account based on the amount and a date range, rather than having to explicitly know which account it should match with.

From what I can tell, this is the strategy used in the section to Identify and Apply Historical Transfers. Perhaps this algorithm could be the basis for a first class feature for smarter transfers outside of the rules engine.

Bonus idea: perhaps there could be a special category of something like "Pending Transfer" for transactions that we know (or have rules defining) will be a transfer but the corresponding transaction hasn't come through yet. This special category would also be excluded from reports and budgets.

Teaching and learning

No response

Originally created by @enewbury on GitHub (Jan 2, 2026). ### 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? My problem: I have multiple credit cards from Chase. When I make a payment to any of the chase cards, the entry in my checking account is identical for each card. There is no way for me to identify which credit card account I am transferring to based on the transaction itself, so I cannot use the method described [here](https://actualbudget.org/docs/budgeting/rules/custom/#q-i-use-bank-sync-how-do-i-create-transfers-and-not-make-duplicates) to setup automatic transfers. ### Describe your ideal solution to this problem Ideally this would automatically detect the corresponding transaction in another account based on the amount and a date range, rather than having to explicitly know which account it should match with. From what I can tell, this is the strategy used in the section to [Identify and Apply Historical Transfers](https://actualbudget.org/docs/advanced/scripts/modify-transfers). Perhaps this algorithm could be the basis for a first class feature for smarter transfers outside of the rules engine. Bonus idea: perhaps there could be a special category of something like "Pending Transfer" for transactions that we know (or have rules defining) will be a transfer but the corresponding transaction hasn't come through yet. This special category would also be excluded from reports and budgets. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 20:27:04 -06:00
GiteaMirror commented 2026-02-28 20:27:05 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 2, 2026):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 👍!

@github-actions[bot] commented on GitHub (Jan 2, 2026): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 -->
GiteaMirror commented 2026-02-28 20:27:05 -06:00
Author
Owner
Copy Link

@totti4ever commented on GitHub (Feb 27, 2026):

How does this differ from #1628?

@totti4ever commented on GitHub (Feb 27, 2026): How does this differ from #1628?
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 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#2763
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?