-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
understanding account balances #40
Comments
Bagels is designed for daily input - so it assumes you won't input something for the future - only when actually it is incurred. This design is also why you can't press right on today to go to tomorrow when selecting date in home. But automating recurring transactions is on the todo list! |
Got it and it makes sense! What I mean by planning is that I know a payment is coming out this Friday for 900ish, so I’ll add it in the future. My account balance goes down into the negatives (say, -200), so I know I need to make sure I put at least that amount in my account so it won't actually go negative on Friday. This is a fantastic feature to have, imho. But like I said, it makes reconciliation harder. It would be nice to see if you used both lines of the accounts for two balances. Line one could show the current balance up to and including today, while line two could show the balance for the entire ledger, like it does now. For what its worth, your software has actually caused me to discover a bug in my banking app; so keep up the good work! |
That's a great idea! I think I'll implement this as a 'scheduled transaction' feature, where records added in future timestamps must be marked 'paid' for it to affect the balance, but it can also show the affected balance when needed! Coming in 0.3.x |
I noticed that if I schedule a transaction in the future, it updates my balance today. Is that by design or a bug? I actually like it for if I am trying to plan things out, but it makes it harder to reconcile later (does my actual account balance match what is on the screen).
The text was updated successfully, but these errors were encountered: