github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #1628] [Feature] Bank Sync - Recognise transfers between accounts #7554

New Issue
Closed
opened 2026-04-10 17:26:15 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-10 17:26:15 -05:00
Owner
Copy Link

Originally created by @daniel-tp on GitHub (Sep 1, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1628

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?

I have set up bank sync via GoCardless for 2 accounts. I quite often do transfers between these accounts but when syncing these accounts to Actual, they are not recognised as transfers and have to be manually changed into transfers (Which usually creates a mess of duplicates as well).

It is possible to create rules that make certain payees into transfers, but this usually still doesn't connect transfers together.

This was initially proposed in https://github.com/actualbudget/actual/issues/724#issue-1609683346 but that was closed with the main bank sync feature was completed.

There was also a PR created but never merged: https://github.com/actualbudget/actual/pull/766

Describe your ideal solution to this problem

I would propose functionality to automatically recognise transfers going between accounts (Same amount, similar date) and connect them together. I realise this can't always be perfect but it would be better than having nothing.

Teaching and learning

Hopefully this would be automatic, and just makes the Actual bank sync feature more seamless. Perhaps documentation on what to do when matching up transfers fails and possibly makes duplicates?

Originally created by @daniel-tp on GitHub (Sep 1, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1628 ### 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? I have set up bank sync via GoCardless for 2 accounts. I quite often do transfers between these accounts but when syncing these accounts to Actual, they are not recognised as transfers and have to be manually changed into transfers (Which usually creates a mess of duplicates as well). It is possible to create rules that make certain payees into transfers, but this usually still doesn't connect transfers together. This was initially proposed in https://github.com/actualbudget/actual/issues/724#issue-1609683346 but that was closed with the main bank sync feature was completed. There was also a PR created but never merged: https://github.com/actualbudget/actual/pull/766 ### Describe your ideal solution to this problem I would propose functionality to automatically recognise transfers going between accounts (Same amount, similar date) and connect them together. I realise this can't always be perfect but it would be better than having nothing. ### Teaching and learning Hopefully this would be automatic, and just makes the Actual bank sync feature more seamless. Perhaps documentation on what to do when matching up transfers fails and possibly makes duplicates?
GiteaMirror added the needs votesfeature labels 2026-04-10 17:26:15 -05:00
GiteaMirror commented 2026-04-10 17:26:16 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 1, 2023):

✨ 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:1702561160 --> @github-actions[bot] commented on GitHub (Sep 1, 2023): :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 -->
GiteaMirror commented 2026-04-10 17:26:16 -05:00
Author
Owner
Copy Link

@M123-dev commented on GitHub (Feb 18, 2024):

For me this is a core feature, not only normal transfers but also payments like

Main Bank Accout -> Paypal -> Outgoing

It would be nice if they were combined.

Here some interesting information about transactions merging #669

<!-- gh-comment-id:1951321962 --> @M123-dev commented on GitHub (Feb 18, 2024): For me this is a core feature, not only normal transfers but also payments like ```Main Bank Accout -> Paypal -> Outgoing``` It would be nice if they were combined. ------- Here some interesting information about transactions merging #669
GiteaMirror commented 2026-04-10 17:26:17 -05:00
Author
Owner
Copy Link

@lucharo commented on GitHub (Feb 19, 2024):

For me this a core feature too. Duplicate transfer transactions between accounts are very cumbersome to handle manually and prone to error.

<!-- gh-comment-id:1951538964 --> @lucharo commented on GitHub (Feb 19, 2024): For me this a core feature too. Duplicate transfer transactions between accounts are very cumbersome to handle manually and prone to error.
GiteaMirror commented 2026-04-10 17:26:18 -05:00
Author
Owner
Copy Link

@darianf01 commented on GitHub (Feb 20, 2024):

I would add to this wish another point. Some transfers are charging fees, but the fee is not added as separate transaction. For example, paying from source AccountA 102cocos (2cocos for transfer fees) but depositing in the destination AccountB 100cocos. The payment appears as 102cocos in AccountA. Would be nice if such transfers can still be automatically matched.

<!-- gh-comment-id:1954311853 --> @darianf01 commented on GitHub (Feb 20, 2024): I would add to this wish another point. Some transfers are charging fees, but the fee is not added as separate transaction. For example, paying from source AccountA 102cocos (2cocos for transfer fees) but depositing in the destination AccountB 100cocos. The payment appears as 102cocos in AccountA. Would be nice if such transfers can still be automatically matched.
GiteaMirror commented 2026-04-10 17:26:19 -05:00
Author
Owner
Copy Link

@CelestialStreamer commented on GitHub (Mar 20, 2024):

I have about a dozen automatic transfers a month, and I usually make at least another dozen more a month manually transferring (usually paying off credit card). I'm new to using Actual and found it tedious to make sure all my accounts (25+) were all correct (reconciled). I haven't even re-synced with SimpleFIN for fear of making a lot of work for me to do.

<!-- gh-comment-id:2008925703 --> @CelestialStreamer commented on GitHub (Mar 20, 2024): I have about a dozen automatic transfers a month, and I usually make at least another dozen more a month manually transferring (usually paying off credit card). I'm new to using Actual and found it tedious to make sure all my accounts (25+) were all correct (reconciled). I haven't even re-synced with SimpleFIN for fear of making a lot of work for me to do.
GiteaMirror commented 2026-04-10 17:26:20 -05:00
Author
Owner
Copy Link

@musicaldesigner commented on GitHub (May 6, 2025):

In YNAB, if I change a transaction to a transfer, it automatically recognizes the duplicate in the other account and merges them, so that could be an alternative or additional solution which is only partially automatic.

I transfer between my accounts daily. Actual is almost unusable for me until this is implemented since I have so many transfers in my accounts.

<!-- gh-comment-id:2853360902 --> @musicaldesigner commented on GitHub (May 6, 2025): In YNAB, if I change a transaction to a transfer, it automatically recognizes the duplicate in the other account and merges them, so that could be an alternative or additional solution which is only partially automatic. I transfer between my accounts daily. Actual is almost unusable for me until this is implemented since I have so many transfers in my accounts.
GiteaMirror commented 2026-04-10 17:26:21 -05:00
Author
Owner
Copy Link

@KonPaw commented on GitHub (Mar 20, 2026):

Fyi as a workaround you can add rules that do this. On one account I set Actualbudget to change it to transfer. And on the receiving one I set a rule to delete transactions from that source.

<!-- gh-comment-id:4098154575 --> @KonPaw commented on GitHub (Mar 20, 2026): Fyi as a workaround you can add rules that do this. On one account I set Actualbudget to change it to transfer. And on the receiving one I set a rule to delete transactions from that source.
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#7554
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?