mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 22:54:03 -05:00
[Feature] Schedule templates rollover #1603
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#1603
Reference in New Issue
Block a user
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?
Originally created by @soloam on GitHub (Nov 20, 2024).
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
When I make a budget to a schedule, It's implied that it should be respected, it's bill... If not payed this month, I will need to pay it next month! So in the next month the budget should be the month template, plus the unmet bill from the previews month.
Describe your ideal solution to this problem
Exemple:
Bills Category:
#template schedule Gas Bill #template schedule Light BillSchedules:
Gas Bill: 50
Light Bill: 100
October:
Bills Category Budget: 150
Payed 100
November
Bills Category Budget: 150 + 50 (From October)
To avoid breaking changes, we could add a "important" tag for exemple to the template to say that the template MUST be met, or it will be added to the budget in the next month
Teaching and learning
No response
@github-actions[bot] commented on GitHub (Nov 20, 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 👍!
@matt-fidd commented on GitHub (Nov 20, 2024):
The rollover should take care of this for you already - there will be 50 remaining in the bills category that will be rolled over to the next month.
Template used:
#template schedule {schedule name}(scheduled as -100)Month 1 (50 paid):
Month 2 - shows 150 budgeted:
@soloam commented on GitHub (Nov 20, 2024):
I see my problem... I think this is not a Feature But a Bug... Look at my exemple:
I have a bill that only applies to December, so I have this template:
#template schedule Bill Month
#template schedule full Bill December
this is my November:
Both Bills are 12 Euros.
In December the template should generate 24.
When I start December I see this:
The 12 Euros ate there from November... But when I generate the template:
It only generates the amount to fill 24...
I would expect the budget to be 24 (both bills) and the total be 36 (Both bills plus the October one)
@matt-fidd commented on GitHub (Nov 20, 2024):
@youngcw - could you have a look at this please? I'm not sure on the inner workings of schedule based templates
My first instinct is that the 12 that was rolled over was marked against the "full" template, which is now fully funded. Another 12 is then added for the normal regular one, "using up" the rolled over amount from the previous month.
@soloam commented on GitHub (Nov 20, 2024):
If that's the case it could be a bug! if needed I can fill a bug issue, since this is marked as "Feature" and its closed
@youngcw commented on GitHub (Nov 20, 2024):
Calculating the schedules is really complicated with all the edge cases, so my real recommendation is to not use multiple schedules on top of each other if the schedules don't get auto payed and the months the money comes out isn't consistent. The other option maybe is to use 'full' on both of them.
@soloam commented on GitHub (Nov 20, 2024):
I tested out with full in both and the result is the same! Not using staked schedules, for me, would not be manageable, I would need a category for each schedule, and I use it in other categories, for exemple Bills, Streaming services etc... All works ok if all is payed on the previews month...The problem is when it fails a payment and is transferred to the next month.
@youngcw commented on GitHub (Nov 20, 2024):
If the schedule is consistent amounts and monthly then you could probably use a
#template 50kind of thing and stack those.@soloam commented on GitHub (Nov 20, 2024):
Probably that's what I'll end up doing... but that is a "hack" to what end's up on being a bug!
@soloam commented on GitHub (Nov 20, 2024):
But now that I think about this... This would not solve the extra bill on December! I would still need to stack the anual template to be processed in December! Because the bill is 12 every month and a extra one in December!
@soloam commented on GitHub (Nov 20, 2024):
Ok I did a extra test and this only seems to be related when you stack a month and a yearly bill! If both schedules are daily or both are yearly... it works ok.
Test 1
Test1 - Montly 12 Euro
Test2 - Montly 12 Euro
November
OK
December
Ok
Test 2
Test1 - Yeatly 12 Euro In November
Test2 - Yearly 12 Euro in December
November:
Ok
December
Ok
@soloam commented on GitHub (Nov 20, 2024):
So, I still think this is a bug, but since its when I mix yearly and monthly on the same category... I can bypass this spliting both into 2 different categories! If you find the time to solve this it would be great... if not... its not the end of the world