Stealing from the future
When I import my bank transactions into YNAB, occasionally there will be a transaction that I want to initially import into "to be budgeted" and then juggle things around on the budget page to cover. However, instead of causing this months TBB to go red it causes next months to go red instead.
I've done some searching around and this seems to be called "stealing from the future".
It means that every time I use YNAB I have to click forward into next month just to check it's still green. Searching through the forums, this seems to be an issue 2+ years old.
Is there really no other fix than manually checking or installing a third party browser addon which may/may not be respecting my privacy? Surely with a subscription based model and a yearly cost of $85 we should expect issues like this to be fixed quicker than 2 years+?
Apologies if I'm missing something - would love to know how to stop this happening if it has already been addressed! Thanks.
Thanks Superbone . I see the toolkit is open source so I'll give it a look. The reasoning behind my privacy comment is that I have to trust YNAB will respect my privacy (I pay them for that expectation and they stake their reputation on it). But I don't have that relationship with the extension developers. However, given that it's open source I have to hope their community respects privacy and doesn't do anything with my data.
Still, I'd prefer a first-party solution direct from YNAB. I don't use any of their training or support so I really only pay for the software.
One alternative that also works, which some prefer, (I use it) and others prefer not to, is instead of actually budgeting money into future months, to create a category called "Income for Next Month" (INM) where you place all of your income that isn't planned to be used this month into. Then at the end of the month, you release the funds from that category back into TBB, and you budget it into the new month.
This has at least 2 great benefits. 1. you don't have to mess with switching months every time you get paid, and 2. Even if you aren't a month ahead yet on your income (still on paycheck to paycheck mode) you can work toward getting an entire month's worth of budgeting into your INM and in one fell swoop you get the entire next month's budget done after your final income of the month comes in.
Hot Pink Cup said:
When I import my bank transactions into YNAB, occasionally there will be a transaction that I want to initially import into "to be budgeted" and then juggle things around on the budget page to cover.
I know your overall question is about SFTF, but I'm curious about this part of your workflow, because I don't understand your purpose in categorizing any outflow transaction as "Inflow: TBB" instead of to the correct spending category.
My preference is the INM category for many reasons, but leaving $1 in TBB is an effective workaround if you wish to budget directly to the future every time income arrives. Outside of overspending, a future TBB will never be less than a positive current TBB.
Others who wish to budget all the way to $0 rely exclusively on the Move Money or Cover Overspending dialogs when TBB is $0. (Click on the category Available value to access.) This ensures offsetting budget entries within the same month.
Hi Hot Pink Cup !
Yes, once you budget in the future the most up-to-date To be Budgeted figure is in that future month. Our team is looking at ways to make Stealing From The Future more prominent, and know that we can improve here.
Our CPO, Todd, recently did an AMA on Reddit that touched on this. A version was beta tested in the past, but it wasn't quite where we'd like it to be. The solution has been a tricky one, but we're not giving up! You can let our development team know your thoughts here.
While not specifically a SFTF fix, we have a few changes in the pipeline that I personally feel will help make it less likely. Though, it's a hunch and time will tell!