github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 12:28:57 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #7237] [Feature] Merge/link transfers manually #52141

New Issue
Closed
opened 2026-04-30 20:19:26 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-30 20:19:26 -05:00
Owner
Copy Link

Originally created by @krugerjac on GitHub (Mar 19, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7237

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 account 10010 and account 20020 in the bank. In Actual I renamed them to abc and def to make it easier to manage.
When importing ofx files from multiple accounts, the program does not see that $100 transferred from account 10010 (abc) on 01/01/2026 matches the $100 transferred to account 20020 (def) on 01/01/2026. So abc will show $100 transferred to 10010 and def will show $100 received from 20020.
Maybe it is because the accounts were renamed? So I configured a rule to rename 10010 to abc and 20020 to def which works, until I import 20020 ofx file and now it shows 2 entries for $100 in def. One entry for $100 from abc and another $100 from 10010.
Removing the rule shows it as a budged category as it does not recognize 10010 or 20020 as accounts. Changing the entry to transfer to abc or def caused an extra entry to appear.

Is it possible to select the 2 entries and merge them manually like YNAB did? This will also help with when you transfer on 01/Jan/2026 and the other bank account only receive it on 04/jan/2026.

Thanks for the great work done so far.

Describe your ideal solution to this problem

No response

Teaching and learning

No response

Originally created by @krugerjac on GitHub (Mar 19, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7237 ### 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 account 10010 and account 20020 in the bank. In Actual I renamed them to abc and def to make it easier to manage. When importing ofx files from multiple accounts, the program does not see that $100 transferred from account 10010 (abc) on 01/01/2026 matches the $100 transferred to account 20020 (def) on 01/01/2026. So abc will show $100 transferred to 10010 and def will show $100 received from 20020. Maybe it is because the accounts were renamed? So I configured a rule to rename 10010 to abc and 20020 to def which works, until I import 20020 ofx file and now it shows 2 entries for $100 in def. One entry for $100 from abc and another $100 from 10010. Removing the rule shows it as a budged category as it does not recognize 10010 or 20020 as accounts. Changing the entry to transfer to abc or def caused an extra entry to appear. Is it possible to select the 2 entries and merge them manually like YNAB did? This will also help with when you transfer on 01/Jan/2026 and the other bank account only receive it on 04/jan/2026. Thanks for the great work done so far. ### Describe your ideal solution to this problem _No response_ ### Teaching and learning _No response_
GiteaMirror commented 2026-04-30 20:19:27 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 19, 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 👍!

<!-- gh-comment-id:4088415114 --> @github-actions[bot] commented on GitHub (Mar 19, 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-04-30 20:19:28 -05:00
Author
Owner
Copy Link

@krugerjac commented on GitHub (Mar 19, 2026):

This is a Feature so why was it auto closed before anyone can vote?

<!-- gh-comment-id:4088442893 --> @krugerjac commented on GitHub (Mar 19, 2026): This is a Feature so why was it auto closed before anyone can vote?
GiteaMirror commented 2026-04-30 20:19:28 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Mar 19, 2026):

You can manually merge transactions and link transactions as a transfer already.

<!-- gh-comment-id:4090052965 --> @youngcw commented on GitHub (Mar 19, 2026): You can manually merge transactions and link transactions as a transfer already.
GiteaMirror commented 2026-04-30 20:19:29 -05:00
Author
Owner
Copy Link

@db-src commented on GitHub (Mar 19, 2026):

i.e. on desktop mode, select two txns, then in the "2 selected" drop-down menu click to "Make Transfer".

And as the autoreply says, feature requests are intentionally closed and then voted on via 👍🏻s

<!-- gh-comment-id:4092484774 --> @db-src commented on GitHub (Mar 19, 2026): i.e. on desktop mode, select two txns, then in the "2 selected" drop-down menu click to "Make Transfer". And as the autoreply says, feature requests are intentionally closed and then voted on via 👍🏻s
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
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#52141
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?