github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 11:42:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Use date from manual transaction instead of imported transaction #416

New Issue
Closed
opened 2026-02-28 19:03:14 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-02-28 19:03:14 -06:00
Owner
Copy Link

Originally created by @neilguertin on GitHub (May 29, 2023).

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?

My bank reports incorrect dates on transactions, usually the posted date, and transactions on the weekend are always delayed until Monday. This means that transactions are often several days off. When I import the transactions, they overwrite the existing manually entered transactions or previously corrected transactions with the incorrect date.

This sometimes even moves transactions to a different month, causing chaos in my budget.

The Import Transactions documentation says

It will always favor the imported transaction. It if matches a manually-entered transaction, it will update the date to match the imported transaction. Keeping dates in sync with your bank is important as it allows you compare the balance at any point in time with your bank.

I consider my budget a better source of truth than my bank and so I don't think it makes sense to put incorrect information in the budget just to match my bank statement which I never look at anyways.

Describe your ideal solution to this problem

This could be controlled with either a global setting or an option on the import confirmation page.

Teaching and learning

No response

Originally created by @neilguertin on GitHub (May 29, 2023). ### 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? My bank reports incorrect dates on transactions, usually the posted date, and transactions on the weekend are always delayed until Monday. This means that transactions are often several days off. When I import the transactions, they overwrite the existing manually entered transactions or previously corrected transactions with the incorrect date. This sometimes even moves transactions to a different month, causing chaos in my budget. The [Import Transactions documentation](https://actualbudget.github.io/docs/Accounts/Transactions/importing-trans/) says > It will always favor the imported transaction. It if matches a manually-entered transaction, it will update the date to match the imported transaction. Keeping dates in sync with your bank is important as it allows you compare the balance at any point in time with your bank. I consider my budget a better source of truth than my bank and so I don't think it makes sense to put incorrect information in the budget just to match my bank statement which I never look at anyways. ### Describe your ideal solution to this problem This could be controlled with either a global setting or an option on the import confirmation page. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 19:03:14 -06:00
GiteaMirror commented 2026-02-28 19:03:15 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 29, 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=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (May 29, 2023): :sparkles: Thanks for sharing your idea! :sparkles: 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=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-02-28 19:03:16 -06:00
Author
Owner
Copy Link

@axelson commented on GitHub (Jan 5, 2025):

I wonder if another solution to this is to keep a separate posted date that can be different from the transaction date.

@axelson commented on GitHub (Jan 5, 2025): I wonder if another solution to this is to keep a separate posted date that can be different from the transaction date.
GiteaMirror commented 2026-02-28 19:03:16 -06:00
Author
Owner
Copy Link

@mcalligator commented on GitHub (Apr 20, 2025):

I wonder if another solution to this is to keep a separate posted date that can be different from the transaction date.

I think that's quite a good idea, as it preserves the integrity of data imported from one's bank, whilst enabling one's budget to be the authoritative source of truth for the transaction date if preferred.

@mcalligator commented on GitHub (Apr 20, 2025): > I wonder if another solution to this is to keep a separate posted date that can be different from the transaction date. I think that's quite a good idea, as it preserves the integrity of data imported from one's bank, whilst enabling one's budget to be the authoritative source of truth for the transaction date if preferred.
GiteaMirror commented 2026-02-28 19:03:16 -06:00
Author
Owner
Copy Link

@TorC8 commented on GitHub (Aug 12, 2025):

It looks to me there can be only one transaction post date, and the only sensible date for that is when the transaction posts to the account.  Given that, AB's method would be correct.

A field in the transaction record for budget withdrawal date, defaulting to manually entered transaction date if different from account posted date, would be a good option.

@TorC8 commented on GitHub (Aug 12, 2025): It looks to me there can be only one transaction post date, and the only sensible date for that is when the transaction posts to the account.  Given that, AB's method would be correct. A field in the transaction record for budget withdrawal date, defaulting to manually entered transaction date if different from account posted date, would be a good option.
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#416
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?