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 #4230] [Feature] add ability to approve new transactions #8729

New Issue
Closed
opened 2026-04-10 19:01:12 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-10 19:01:12 -05:00
Owner
Copy Link

Originally created by @e13h on GitHub (Jan 23, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4230

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?

One feature I liked in YNAB was the ability to approve or reject transactions that were imported via bank sync. I liked that I could acknowledge that I’ve seen and reviewed a transaction and that the category is correct.

My workflow in Actual is to just add a tag #flag to new transactions so that I can quickly come back to them later for further review. But this is error prone, sometimes I forget to add the tag.

Describe your ideal solution to this problem

It would be nice if there was an “approve” mechanism for transactions imported by SimpleFIN in Actual so that I can have peace of mind that whatever transactions get imported won’t sneak in with an incorrect category.

Teaching and learning

No response

Originally created by @e13h on GitHub (Jan 23, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4230 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [x] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? One feature I liked in YNAB was the ability to approve or reject transactions that were imported via bank sync. I liked that I could acknowledge that I’ve seen and reviewed a transaction and that the category is correct. My workflow in Actual is to just add a tag `#flag` to new transactions so that I can quickly come back to them later for further review. But this is error prone, sometimes I forget to add the tag. ### Describe your ideal solution to this problem It would be nice if there was an “approve” mechanism for transactions imported by SimpleFIN in Actual so that I can have peace of mind that whatever transactions get imported won’t sneak in with an incorrect category. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-04-10 19:01:12 -05:00
GiteaMirror commented 2026-04-10 19:01:13 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 23, 2025):

✨ 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:2611197768 --> @github-actions[bot] commented on GitHub (Jan 23, 2025): :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-10 19:01:13 -05:00
Author
Owner
Copy Link

@sexyskinnybitch commented on GitHub (Jan 31, 2025):

I am surprised that this was not a feature in Actual. Imported transactions just appear in the list, which makes it hard to verify accuracy of transactions and look for possible fraud. Unless you are looking for them, you'll easily miss them.

<!-- gh-comment-id:2627630658 --> @sexyskinnybitch commented on GitHub (Jan 31, 2025): I am surprised that this was not a feature in Actual. Imported transactions just appear in the list, which makes it hard to verify accuracy of transactions and look for possible fraud. Unless you are looking for them, you'll easily miss them.
GiteaMirror commented 2026-04-10 19:01:14 -05:00
Author
Owner
Copy Link

@kopach commented on GitHub (Apr 22, 2025):

I believe it should be a general mechanism for all auto-imported transactions. Not only for SimpleFIN provider, but for any other (like GoCardless, etc)

<!-- gh-comment-id:2820710679 --> @kopach commented on GitHub (Apr 22, 2025): I believe it should be a general mechanism for all auto-imported transactions. Not only for SimpleFIN provider, but for any other (like GoCardless, etc)
GiteaMirror commented 2026-04-10 19:01:14 -05:00
Author
Owner
Copy Link

@thromer commented on GitHub (Sep 17, 2025):

I'd also like approve/reject as a first-class feature -- like @e13h I want to confirm the category of new transactions.

For @e13h's workaround: I would think you could create a rule that prepends #flag or whatever tag you like so you don't have to worry about forgetting.

<!-- gh-comment-id:3303791537 --> @thromer commented on GitHub (Sep 17, 2025): I'd also like approve/reject as a first-class feature -- like @e13h I want to confirm the category of new transactions. For @e13h's workaround: I would think you could create a rule that prepends `#flag` or whatever tag you like so you don't have to worry about forgetting.
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#8729
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?