github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #2470] [Feature] Transaction Id / Check Number / basically, a nullable identifier #50110

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

Originally created by @fref on GitHub (Mar 16, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2470

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 banks do not provide OFX style export files, barely a CSV. Besides that, the payee can be absent or have a different name than the one I use in my budget. Therefore, I tend to do manual reconciliation. This is greatly helped by entering the transaction number (usually YY/### or YY/#### but it could be arbitrary). Ynab4 has a field for that which it calls "check number", which I use a lot.

Describe your ideal solution to this problem

  • Add this field to the transaction type
  • Possibly, make some fields toggle-able on/off in the display

Teaching and learning

No response

Originally created by @fref on GitHub (Mar 16, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2470 ### 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 banks do not provide OFX style export files, barely a CSV. Besides that, the payee can be absent or have a different name than the one I use in my budget. Therefore, I tend to do manual reconciliation. This is greatly helped by entering the transaction number (usually YY/### or YY/#### but it could be arbitrary). Ynab4 has a field for that which it calls "check number", which I use a lot. ### Describe your ideal solution to this problem - Add this field to the transaction type - Possibly, make some fields toggle-able on/off in the display ### Teaching and learning _No response_
GiteaMirror added the feature label 2026-04-30 13:12:08 -05:00
GiteaMirror commented 2026-04-30 13:12:55 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 16, 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:2002046160 --> @github-actions[bot] commented on GitHub (Mar 16, 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:12:55 -05:00
Author
Owner
Copy Link

@fref commented on GitHub (Mar 16, 2024):

Actually a duplicate of #1852 , this lodash-style issue management got me confused when searching for issues

<!-- gh-comment-id:2002125536 --> @fref commented on GitHub (Mar 16, 2024): Actually a duplicate of #1852 , this lodash-style issue management got me confused when searching for issues
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
tech-support
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#50110
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?