Thanks Matt I agree that it would be nice to separate the expense type of buckets. I have several buckets that accumulate like your Auto Insurance example and want to make sure that the money is there when needed. The monthly rollover works but the user (me) has to be careful to not spend the money on other expenses (or savings). I like the idea of an identifier in the name (fill limit or warning indicator) since this keeps with the current design and application operation. Also moving the buckets around to de-emphasize them also is a good idea.
One idea if it is not currently in MoneyWell (I don't see the ability) is to have an option on the graph that will allow the future display of the spending plan. I have all the non-recurring budget amounts in the plan and if I could visually see the cash flow based on the plan, then this would help. Future recurring transaction show on the graph but I don't see the ability to see the plan. On Dec 14, 2:53 pm, Matt Armstrong <[email protected]> wrote: > Hi Dan, > > Sounds like you are primarily motivated by a desire to separate > accrual buckets from regular every-day expense buckets so you aren't > tempted to spend from them. > > Today, I have an "Auto Insurance" bucket which accrues 1/6th of my 6 > month premium every month. This works. I'm not tempted to spend from > this bucket because I know I'll just be short when the bill comes. > > In the past, for for more variable and nebulous stuff, like > landscaping, I've named the bucket with, in MoneyWell terms, might be > called a "fill limit" (or, in your terms, an "accrual limit"). E.g. > "Landscaping ($200)". If the bucket grows larger than that, I know it > is "safe" to transfer out for other spending. This simple convention > proved to be enough of a cue. > > Moneywell has other ways to de-emphasize buckets. I put less > frequently used buckets at the bottom. You could also hide them so > the money doesn't feel "readily available." > > On Dec 13, 8:34 am, Dan Harrison <[email protected]> wrote: > > > I have used MoneyWell for the past five months and really like the > > design and cash flow concepts. Great work Kevin! > > > I have one area where I would like your (or the user community) advice > > and this deals with an area I call accruals. The concept is that we > > all have expenses that do not occur regularly but need to be in our > > budget. Examples would be automobile, landscaping, medical, and other > > expenses. I initially defined a monthly amount in my spending plan > > that flowed to the appropriate expense bucket. This works and the flow > > of non-used expense money to the next month would handle the so called > > accrual. What I found dangerous was the temptation to move this money > > to other buckets which would not leave enough money when the actual > > expense occurred. > > > My second attempt was to create income buckets where I would then > > allocate the accrual amounts leaving the expense accounts for the > > actual expenses when they occurred. I would transfer money from the > > income accrual to pay the expense. This works well but I had to > > create split transactions for all the accrual accounts when income was > > deposited in the bank. I defined my income transaction as repeating > > every month but it doesn't look like the application wants to repeat > > split transactions (only the master transaction amount). Is it > > possible to repeat split transactions? > > > Do you (or anyone in the community) have an approach for allocating > > income into a holding bucket (accrual) and then transfer this to an > > actual expense when the expense occurs? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "No Thirst Software User Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/no-thirst-software?hl=en -~----------~----~----~----~------~----~------~--~---
