[Feature] Add way to see if a transaction was matched / imported via bank sync or file import #2593

Closed
opened 2026-02-28 20:20:35 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @Crosis47 on GitHub (Nov 4, 2025).

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?

It is nice when using imports and bank sync to be able to see which transactions have been matched to a transaction from bank sync or imported from a file. I switched to Actual from Quicken and this was something I could do by just right-clicking a transaction in the register. It would show me the original description / notes of the transaction and give me the option to revert to it. This was very nice to have when verifying transactions were not duplicated or mis-entered. Here is an example screenshot from Quicken:

Image

In Quicken, this choice was used to undo the rename rule and revert to the imported values.

Describe your ideal solution to this problem

This could be implemented on a read-only level by either adding a single "Synced" column to the register or a pop-up on hover. The column could just use a few symbols to show 3 statuses:
1.) Manually entered (no symbol shown) - Transaction has not been seen on a bank sync or file import.
2.) Matched - Transaction merged with imported transaction.
3.) Imported - Transaction is new. Did not exist prior to import / bank sync.

If the pop-up were implemented, it would be nice to have it show the original imported notes or payee.

Teaching and learning

A screenshot and small write-up on the change notes and wiki showing the new column / popup would suffice.

Originally created by @Crosis47 on GitHub (Nov 4, 2025). ### 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? It is nice when using imports and bank sync to be able to see which transactions have been matched to a transaction from bank sync or imported from a file. I switched to Actual from Quicken and this was something I could do by just right-clicking a transaction in the register. It would show me the original description / notes of the transaction and give me the option to revert to it. This was very nice to have when verifying transactions were not duplicated or mis-entered. Here is an example screenshot from Quicken: <img width="551" height="204" alt="Image" src="https://github.com/user-attachments/assets/c3aeef94-2947-4d7a-81c9-c8338f17dd3e" /> In Quicken, this choice was used to undo the rename rule and revert to the imported values. ### Describe your ideal solution to this problem This could be implemented on a read-only level by either adding a single "Synced" column to the register or a pop-up on hover. The column could just use a few symbols to show 3 statuses: 1.) Manually entered (no symbol shown) - Transaction has not been seen on a bank sync or file import. 2.) Matched - Transaction merged with imported transaction. 3.) Imported - Transaction is new. Did not exist prior to import / bank sync. If the pop-up were implemented, it would be nice to have it show the original imported notes or payee. ### Teaching and learning A screenshot and small write-up on the change notes and wiki showing the new column / popup would suffice.
GiteaMirror added the featureneeds votes labels 2026-02-28 20:20:35 -06:00
Author
Owner

@coderabbitai[bot] commented on GitHub (Nov 4, 2025):

Caution

The CodeRabbit agent's plans did not produce any file changes.

@coderabbitai[bot] commented on GitHub (Nov 4, 2025): <!-- This is an auto-generated issue plan by CodeRabbit --> > [!CAUTION] > The CodeRabbit agent's plans did not produce any file changes.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 4, 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 👍!

@github-actions[bot] commented on GitHub (Nov 4, 2025): :sparkles: Thanks for sharing your idea! :sparkles: 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 👍! <!-- feature-auto-close-comment -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2593