github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #2679] [Feature] Explicitly ask when reconciling transactions on manual import #50183

New Issue
Closed
opened 2026-04-30 13:30:00 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-30 13:30:00 -05:00
Owner
Copy Link

Originally created by @dugite-code on GitHub (Apr 29, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2679

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?

Raised in #2668 (And by the looks of it in #2420) The Reconciliation function run on CSV manual import can cause unrelated transactions to be merged together if:

  1. The transactions are within about week of each other.
  2. The transaction dollar amount matches.

Some examples of regular transactions that may be caught by this:

  • Go to the same cafe for the same coffee in the morning.
  • Weekly rent payments
  • Mortgage payments

This is done transparently and can cause confusion when account balances cannot be balanced correctly.

Describe your ideal solution to this problem

Data shouldn't be transparently modified or destroyed without user interaction.

As the Reconciliation function is actively useful the changes should be clearly exposed to users during the import cycle possibly with a second model dialogue.

Mock up:
image

As you can see in the above mock up the imported transaction, RETAIL PURCHASE for 16.39, is shown merging with the existing
transaction CORNER GROCERIES with the note Weekday shopping and the category of groceries.

Teaching and learning

This should open during CSV import workflow if any transactions merging will cause a data change (Date, payee ect.)

Originally created by @dugite-code on GitHub (Apr 29, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2679 ### 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? Raised in #2668 (And by the looks of it in #2420) The Reconciliation function run on ~~CSV~~ manual import can cause unrelated transactions to be merged together if: 1. The transactions are within about week of each other. 2. The transaction dollar amount matches. Some examples of regular transactions that may be caught by this: - Go to the same cafe for the same coffee in the morning. - Weekly rent payments - Mortgage payments This is done transparently and can cause confusion when account balances cannot be balanced correctly. ### Describe your ideal solution to this problem Data shouldn't be transparently modified or destroyed without user interaction. As the Reconciliation function is actively useful the changes should be clearly exposed to users during the import cycle possibly with a second model dialogue. Mock up: ![image](https://github.com/actualbudget/actual/assets/12742064/f1fa1622-481b-481d-9f7b-a47e0c1f1243) As you can see in the above mock up the imported transaction, RETAIL PURCHASE for 16.39, is shown merging with the existing transaction CORNER GROCERIES with the note Weekday shopping and the category of groceries. ### Teaching and learning This should open during CSV import workflow if any transactions merging will cause a data change (Date, payee ect.)
GiteaMirror added the feature label 2026-04-30 13:30:01 -05:00
GiteaMirror commented 2026-04-30 13:30:14 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 29, 2024):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. 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 👍!

<!-- gh-comment-id:2081788973 --> @github-actions[bot] commented on GitHub (Apr 29, 2024): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. 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-04-30 13:30:16 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 9, 2024):

🎉 This feature has been implemented in #2717 and will be released in the next version. Thanks for sharing your idea! 🎉

<!-- gh-comment-id:2217775582 --> @github-actions[bot] commented on GitHub (Jul 9, 2024): :tada: This feature has been implemented in #2717 and will be released in the next version. Thanks for sharing your idea! :tada: <!-- feature-implemented-comment -->
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
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#50183
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?