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

Add Transaction window should have some data validation #32

New Issue
Closed
opened 2026-02-28 18:46:10 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-02-28 18:46:10 -06:00
Owner
Copy Link

Originally created by @Deguello on GitHub (Dec 17, 2021).

After bringing up the New Transaction window, you can immediately press Add Transaction, which will add an essentially blank transaction to the selected account. There's no validation on Payee or Category and there should be, imo. I suppose a $0 amount might be an edge case that could be allowed but, even then, some sort of confirmation dialog might be called for.

Originally created by @Deguello on GitHub (Dec 17, 2021). After bringing up the New Transaction window, you can immediately press Add Transaction, which will add an essentially blank transaction to the selected account. There's no validation on Payee or Category and there should be, imo. I suppose a $0 amount might be an edge case that could be allowed but, even then, some sort of confirmation dialog might be called for.
GiteaMirror commented 2026-02-28 18:46:11 -06:00
Author
Owner
Copy Link

@bpaulien commented on GitHub (Dec 17, 2021):

just putting in my $.02... I agree that probably a completely empty transaction shouldn't be allowed, but I'd like to say also that I don't want it locked down so completely tight that you have to fill everything in before you are able to add the transaction. Maybe force one of payee, notes, or category to be filled? Just something to indicate that you intentionally made the transaction. And yeah, I can see a reason for leaving amounts empty or $0.00, so don't necessarily force that.

@bpaulien commented on GitHub (Dec 17, 2021): just putting in my $.02... I agree that probably a completely empty transaction shouldn't be allowed, but I'd like to say also that I don't want it locked down so completely tight that you have to fill everything in before you are able to add the transaction. Maybe force one of payee, notes, or category to be filled? Just something to indicate that you intentionally made the transaction. And yeah, I can see a reason for leaving amounts empty or $0.00, so don't necessarily force that.
GiteaMirror commented 2026-02-28 18:46:11 -06:00
Author
Owner
Copy Link

@esharden commented on GitHub (Dec 17, 2021):

Offering my own 2 cents here. I’d much prefer that empty transactions be allowed rather than being forced to completely fill out all three fields. It’s not something I do every day but often enough that it would severely limit the software’s functionality and usefulness if I couldn’t enter a transaction missing any two of the 3 major fields (payee, category, or amount).

Sometimes I don’t know the payee or it’s completely insignificant (tiny bodega I’ll never visit again or some rando from Craigslist).

Sometimes I’ll leave the category blank because I don’t know yet how I want to categorize. Or because I want to “flag” it, as it were, & have it catch my attention later. Or because it’s a new type of expense and since you can’t create a new category on the fly in Actual, I need to finish entering the details as a placeholder and then circle back and finish it after I create a new category.

And speaking of placeholders, sometimes I leave the amount empty because I don’t know the final total but I need to document that the transaction did happen or is scheduled to happen and I need to finish the transaction later when I know he amount.

@esharden commented on GitHub (Dec 17, 2021): Offering my own 2 cents here. I’d much prefer that empty transactions be allowed rather than being forced to completely fill out all three fields. It’s not something I do every day but often enough that it would severely limit the software’s functionality and usefulness if I couldn’t enter a transaction missing any two of the 3 major fields (payee, category, or amount). Sometimes I don’t know the payee or it’s completely insignificant (tiny bodega I’ll never visit again or some rando from Craigslist). Sometimes I’ll leave the category blank because I don’t know yet how I want to categorize. Or because I want to “flag” it, as it were, & have it catch my attention later. Or because it’s a new type of expense and since you can’t create a new category on the fly in Actual, I need to finish entering the details as a placeholder and then circle back and finish it after I create a new category. And speaking of placeholders, sometimes I leave the amount empty because I don’t know the final total but I need to document that the transaction did happen or is scheduled to happen and I need to finish the transaction later when I know he amount.
GiteaMirror commented 2026-02-28 18:46:11 -06:00
Author
Owner
Copy Link

@sapphirebound commented on GitHub (Dec 18, 2021):

Maybe we can consider having at least the transaction amount field to be filled as validation? I understand @esharden 's reasoning. However, can't think of a use case for leaving the amount empty.

@sapphirebound commented on GitHub (Dec 18, 2021): Maybe we can consider having at least the transaction amount field to be filled as validation? I understand @esharden 's reasoning. However, can't think of a use case for leaving the amount empty.
GiteaMirror commented 2026-02-28 18:46:11 -06:00
Author
Owner
Copy Link

@samschr commented on GitHub (Dec 18, 2021):

Maybe we can consider having at least the transaction amount field to be filled as validation? I understand @esharden 's reasoning. However, can't think of a use case for leaving the amount empty.

I have several use cases for empty transactions. I used to use reconciliation in YNAB, so I "reconcile" each account with an empty transaction (amount zero) when I cross check it with my bank. I also occasionally use empty transactions as account-specific notes.

With that said, I agree with @bpaulien 's suggestion that at least one of the fields has to have data before allowing the transactions.

@samschr commented on GitHub (Dec 18, 2021): > Maybe we can consider having at least the transaction amount field to be filled as validation? I understand @esharden 's reasoning. However, can't think of a use case for leaving the amount empty. I have several use cases for empty transactions. I used to use reconciliation in YNAB, so I "reconcile" each account with an empty transaction (amount zero) when I cross check it with my bank. I also occasionally use empty transactions as account-specific notes. With that said, I agree with @bpaulien 's suggestion that at least one of the fields has to have data before allowing the transactions.
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
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#32
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?