|
Posted by Tom P. on July 2, 2008, 10:20 am
Please log in for more thread options > Andrew wrote:
> > Tom P. wrote:
> >> ...
> >> A sturdy Cash Flow Forecast and editing a single occurrence
> >> of a
> >> scheduled transaction are the only thing that are keeping me
> >> from
> >> really enjoying this product.
> > FWIW, I don't use the formal "Cash Flow". I simply enter ALL
> > my
> > transactions (mostly scheduled) ahead of time, about one month
> > out
> > (including anticipated paychecks) and simply use the register
> > to
> > ensure that my 'cash flow' covers all my anticipated expenses.
> > As
> > long as there are no negative balances in my checkbook (this
> > includes
> > transfers to savings, tax escrow accounts, and equity/IRA
> > purchase -
> > everything!) I am happy. =A0Works for me. =A0Just a thought of
> > another
> > technique you might wish to consider. YMMV.
>
> I've never found any use for a long-term cash flow projection
> (and when I try to test Quicken's Cash Flow Forecast, I usually
> run into an error message that says I have too many scheduled
> bills and deposits), so I can't even provide much useful comment
> on the feature.
Wow, am I the only person that uses this? Why does no one else find
the use in knowing if you are going broke any time soon? It makes me
wonder if I am doing this right. When so many people don't use this, I
have to wonder if I'm doing something wrong.
>
> [I do think you can manually enter transactions in the forecast
> that will only affect the forecast, but I'm not 100% certain of
> that.]
>
> =A0But for short-term cash flow projections, you don't need to
> enter scheduled transactions into your register. =A0The "Scheduled
> Bills & Deposits" display available for user-created Home views,
> has a nice bar graph that is pretty clear about cash flow (you
> select the account, or accounts, to include in the graph) ...
> but displays only one month at a time. =A0[If you have the
> patience, you can use that graph to look a long way into the
> future.]
Yeah, but it's a month at a time and that makes it hard to notice
financial boundaries and such.
>
> > And about the comment of editing a single occurrence of a
> > scheduled
> > transaction - I must be missing something. =A0Once the scheduled
> > transaction hits the register, you most certainly can edit
> > that
> > single occurrence without affecting all the others past as
> > well as
> > those in the future that haven't been recorded yet. =A0What am I
> > missing?
>
> The op wants to modify selected future paycheck transactions to
> reflect that fact that they will span a holiday or vacation day.
> Then when those modified scheduled transactions appear in
> cash-flow forecasts, they will (correctly) forecast a lower
> inflow of cash for that period because the op does not get paid
> for holidays. =A0By the time the scheduled transaction hits the
> register, it will have no long-term forecasting ability ...
> unless op wants to enter all scheduled transactions for many
> months into the future ... which he has said he doesn't want to
> do.
Exactly. I'm a contractor and, for example the 4th of July is comming
up. I know the check that includes is going to be short. I'd like to
be able to note that in the forcast so the forcast stays moderately
correct. But, since I can't get the forcast to be correct in any case,
it kindof becomes a moot point.
Still looking for a financial package that works correctly...
Tom P.
|