mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 07:04:23 -05:00
[GH-ISSUE #661] [Feature] Allow different transfer dates #70011
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#70011
Reference in New Issue
Block a user
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?
Originally created by @garygreen on GitHub (Feb 15, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/661
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
Currently when creating a transfer when you change the "Date" value it will also change the date on receiving account.
This can be problematic because there are cases where the date a transfer was sent is different to the date it's actually received in the payees account (maybe it takes a few days to clear, and then the receiving account date is different)
My suggestion here is to (somehow) allow for the date to not be kept "in sync" and allow for different dates for the transfer. Hope that makes sense.
Describe your ideal solution to this problem
No response
Teaching and learning
No response
@winklevos commented on GitHub (Mar 26, 2023):
I think this expands beyond just the date.
A transfer between two accounts should be considered two distinct transactions that are linked. Inbound, and outbound.
In data terms these are different, and could have different properties, transaction date, transaction id, description. The amount I would expect remains the same. Though there may be some case in specific accounts where its currency conversion or fee subtracted. (I think we can exclude).
This would also need to be considered when deleting one of the pair of transactions. As you should be able to delete one but not the other. https://github.com/actualbudget/actual/issues/814
@github-actions[bot] commented on GitHub (May 1, 2023):
✨ Thanks for sharing your idea! ✨
This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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=is%3Aissue+label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc
Don’t forget to upvote the top comment with 👍!
@Nyanino commented on GitHub (Sep 17, 2025):
Really feeling the need for this feature right now. I use the running balances feature to reconcile against statements I receive. The linked transactions can have different dates for two accounts ruining the usefulness of the running balances feature as it can only favor one account but not both.
In addition, it would be great to reorder transactions like #1165
@kcollett commented on GitHub (May 5, 2026):
One way I've run into this is in relation to the ability to use drag and drop to reorder transactions with the same date. I had a scenario where I wanted to use this to shift the position of the transfer match that in the statement of the receiving account. To do this, I had to change the date on the transfer to be the posting date in the receiving account, but of course that meant the date of the transfer in the sending account was now incorrect.
@github-actions[bot] commented on GitHub (May 12, 2026):
🎉 This feature has been implemented in #7722 and will be released in the next version. Thanks for sharing your idea! 🎉