mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-10 21:44:08 -05:00
[Feature]: Option for strict date checking in transaction import modal #2420
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2420
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 @cromelex on GitHub (Aug 25, 2025).
Verified issue does not already exist?
What happened?
One of my savings accounts pays daily interest, and isn't automatically synced.
I usually import a csv statement once a month, but Actual always skips entries. This has genuinely happened for the last 4 or 5 months in a row.
When I do a second import, I can see that the skipped transactions are marked as "already imported", despite that not being the case.
Ie, in the current month the inflow entries from the 3rd to the 7th were skipped for no apparent reason.
The amounts are always very similar (because it's daily interest), and daily, and I am not sure if something is causing Actual to ignore the date as a primary identifying element?
How can we reproduce the issue?
I've attached a sanitized sample CSV, not sure if trying to import this can be used reliably to reproduce, but at least it's something.
savings.csv
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Other, Firefox
Operating System
Linux
@joel-jeremy commented on GitHub (Aug 25, 2025):
Actual employs some loose matching to de-duplicate transactions when importing. It looks for the same transaction within a 14 day period (7 days before and 7 days after the transaction being imported), and if it finds something with the same amount, the transaction being imported will be marked as already existing.
You can override this by click on the the "-" icon to import the matched transaction again.
@cromelex commented on GitHub (Aug 25, 2025):
Thanks for the quick reply.
That logic probably makes sense, for most scenarios.
The issue for me is that between transfers from my main account and previous transactions, sometimes it's not immediately obvious if a transaction is being skipped correctly or not.
And because my bank pays interest daily I end up with up to 31 transactions a month, and because they're often of the same value, sometimes it's actually tricky to spot and reconcile.
Is there scope to add something like the option (a checkbox?) to enforce a strict date check when importing via file?
@matt-fidd commented on GitHub (Sep 20, 2025):
You can disable deduplication entirely by unticking "merge with existing transactions"
I'll move this to a feature request for strict date checking, I can see it being useful in these cases if implemented
@github-actions[bot] commented on GitHub (Sep 20, 2025):
✨ 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 👍!