mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-10 20:23:07 -05:00
[Bug]: Merging transactions does not prevent reimport as duplicate #2827
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2827
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 @junalmeida on GitHub (Jan 16, 2026).
Verified issue does not already exist?
What happened?
If I have a duplicated transaction imported via Actual API, given one of them is already marked as a transfer, if I merge the duplicated with the transfer one, once I reimport it duplicates again.
It seems like Actual does not save the
imported_idwhen a merge operation happens, allowing it to come back.How can we reproduce the issue?
Simulating a day 1 import: have a transaction imported with
imported_idset to1234.On the UI, mark it as a transfer to another account.
On day 2, have the same transaction above reimported now with
imported_id=12345, with the same amount. Date posted could be different.See the duplicated transaction on the UI, merge it with the first one that is already a transfer.
Import the day 2 again - same transaction with
imported_id=12345See the duplicated transaction coming back instead of being ignored because it was merged.
test-day1.txt
test-day2.txt
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Chrome
Operating System
Linux
@totallynotjon commented on GitHub (Jan 17, 2026):
I am encountering a similar issue, which I would venture is related. Occasionally, using bank sync, tranfers won't properly deduplicate when changing payees with rules . Merging the transfers won't stick and the import/resync will recreate the duplicate. I am going to take a looksy and will update if I think I can make the merge stick
@totallynotjon commented on GitHub (Jan 17, 2026):
@junalmeida, as a workaround, you can likely disable the setting "Reimport deleted transactions" within bank sync settings, if you are close to reconciled.
Since the merged item is "deleted", if you do this then on re-sync or reimport the item shouldn't be brought in again. This approach also fixed my issue.
Though I do see this as a potential issue with local accounts that do not have a bank sync.
For a local account, I was able to link a bank sync to an unrelated account, toggle the setting, and then unlink the account. After this the preference to not Reimport deleted transactions stuck for file import.
This is cumbersome, and there should probably be some change to make this easier to manage for local accounts.
Separately, while this workaround address this issue for me. I can see the upside in having a separate mechanism to track merged transactions beyond standard delete 'tombstone' column. As surely some people won't want no-reimport enabled for bank sync accounts, and will want their merges to stick.
@junalmeida commented on GitHub (Jan 20, 2026):
@totallynotjon I'm not using bank sync, I don't have it to enable this UI I guess
@totallynotjon commented on GitHub (Feb 10, 2026):
@junalmeida try out the pr I linked and let me know if that doesn't address your issue.
@junalmeida commented on GitHub (Feb 20, 2026):
@totallynotjon I just tested the DEMO of your PR and it seems the setting in the import dialog box works as expected.