"Dick Watson" <littlegreengecko[at]mind-enufalready-spring.com> wrote in
message news:eB6SLph9FHA.3360[at]TK2MSFTNGP11.phx.gbl...
- quote -

I am unaware of any problems in Forecast Cash Flow caused by deleting them,
but entering stop dates for existing scheduled deposits/bills does
accurately affect it.

I meant FCF. I must have let spell check change that to FACT. I agree that
there are BP issues. I just am not aware of any FCF issues. Correct me if
you are.

"Chris Cowles" <NoSpam[at]For.me> wrote in message
news:%23Eglr%23c9FHA.3660[at]TK2MSFTNGP09.phx.gbl...
- quote -

Comments inline

"Dick Watson" <littlegreengecko[at]mind-enufalready-spring.com> wrote in
message news:edBbAuX9FHA.808[at]TK2MSFTNGP09.phx.gbl...
- quote -

Yes. In the edit budget screens, they appear averaged per month
(annualized/12), but in the 'review my budget' screen, and in the annual
report, they're month-specific. The same is true for amounts entered
manually in the budget using a 'custom' schedule. The month-specific budget
is what applies, in the end.

- quote -

I've had several episodes where a paycheck model I deleted from the bill
scheduler does not disappear from the budget. And, because I deleted it, I
can't edit it. Catch-22. Bill Boyd and others have corroborated the problem.
They're an entry on the MSKB describing it.

When you edit a paycheck (or any scheduled bill/deposit, for that matter),
the budget effects are retrospective to the first date it was ever
scheduled. If you want the effects to apply to your budget only in the
future, enter a stop date on the current bill and create a new one with a
future start date. Unfortunately, the stop date you enter has to allow one
more event. You can't enter 0 more events. It has to be 1, at a minimum. If
you don't know about the bill/deposit change in advance, the budget will be
wrong for that one event.

My reference was to the way BP assumes that all scheduled transactions must
be in Budget. In this case, the series may not be terminated--the OPs 10 of
12 months case without having to go to gyrations to note the missing
occurrences--but it should still be possible to tell BP what's real for its
purposes. But you can't. It assumes that whatever it gets from scheduled
items is gospel and in budget. I frequently schedule items--almost always
Only Once items--that I would NEVER budget for. Not with BP you wouldn't.
You scheduled it. BP says it's in budget. Drives me nuts.

The last time I was messing with this it completely ignored the first date
of a series. It was counting all possible IRA contributions from each series
that had a start date and a limited number of occurrences over the next
seven years as occurring in the current year. I haven't revisited that in
several years. Basically I pretty much gave up on doing serious analysis
using BP because of all of the ways it was mangling the data it had. Maybe I
should go back and revisit it--perhaps they fixed it.

Are you saying that you are getting different budgets in different months as
a function of start and stop dates for scheduled transactions, not the
yearly total and monthly average amount?

Why does putting in explicit stop dates on series before deleting them do
anything for FACT? I've never had any issues there. But it does screw up one
element--counting it two to six times--of my paycheck EVERY WEEK until I
edit the series, touch that element, and enter the "edited" series. It's
been that way for many versions now.

"Chris Cowles" <NoSpam[at]For.me> wrote in message
news:%23OtMJBX9FHA.3664[at]TK2MSFTNGP10.phx.gbl...
- quote -

"Dick Watson" <littlegreengecko[at]mind-enufalready-spring.com> wrote in
message news:ONKRgtV9FHA.3660[at]TK2MSFTNGP09.phx.gbl...
- quote -

This works perfectly well for me if you have a series of deposits or bills
with future stop dates, and other deposits or bills starting after that. The
key is that they cannot overlap. One must have an explicit stop date that
ends before the start date of the other. In my case I use it to model
predictable significant changes in my paycheck, that are sustained after the
change.

E.g:

Paycheck 1, every 2 weeks, start 12/2/05, stop 1/13/06
Paycheck 2, every 2 weeks, start 1/27/06, no end date.

When I learn of another predictable change, I enter a stop date on paycheck
2 and create paycheck 3.

I've learned that entering stop dates on all scheduled bills, before
deleting them, is critical. It's a pain, but necessary. When you do that,
not only do you avoid ghost bills in the budget, your budget and cash flow
forecast are more accurate.
--
Chris Cowles
Gainesville, FL

"SteveM" <SteveM[at]discussions.microsoft.com> wrote in message
news:A3FB7966-25F7-4F2C-BD48-802B70B1DA5C[at]microsoft.com...
- quote -

Create the paycheck for September through the last payment of the current
series. Enter a stop date. Enter another paycheck for the beginning the
subsequent series. If you have wishful thinking, you may want to inflate the
second one by expected COLA increases.

While editing the budget it may look wacky, but if you look at the annual
budget report it will look correct, as will the cash flow forecast.

Do NOT just delete a paycheck model without entering a stop date first.
You'll never get rid of it.
--
Chris Cowles
Gainesville, FL

This is precisely the kind of situation where Money's assumption that
scheduled items are, by definition, in the budget is just plain infuriating.

Here's what I would play around with:

- Setup the scheduled paycheck and tuition as if they occur 12 months/year.
- Setup two scheduled items for the 11th and 12th months that are the exact
opposites of the paycheck and tuition scheduled items. Well, not the exact
opposites. Money will not let you schedule a negative paycheck no matter
what you do. You can enter one in the register. You just can't schedule it
that way. (Another infuriating design choice...) So you'd have to do this as
a Bill, not a Paycheck. You could list all the same--but opposing--income
and expense items, just not with the tabs. You can set these items for
whatever frequency is appropriate, just set the number of occurrences before
the series ends to cover the 10th and 11th months as required.

With any kind of luck Money will now base the budget on 10/12 of the amount.

I'm not sure it will work well for you for a number of reasons. One, last
time I played with this, Money ignored start and end date for a scheduled
series when it wrapped this stuff up into BP. Two, you probably think your
budget should vary from month to month to match reality. Money just plain
refuses to work that way. Many people find BP only really useful over an
annual cycle for this reason: some expenses and incomes are, by definition,
NOT constant month-to-month, so trying to manage to targets as though they
were just doesn't work well. Three, it would probably cause side effects on
Tax Estimator.

Sorry I don't have a better answer. I wouldn't expect much of M07 in this
area. There is every reason to believe that M07 will be just very minor
polishing of M06--which was very minor polishing of M05--based on past
experience. (We might call this "turd polishing" in my business. You can
shine it all you want, but it's still a ...) Besides, whatever it's going to
be is probably just weeks away from a cutoff of functional changes. Maybe
M08? Of course, if there is going to be a standalone M08 application, it's
probably only a matter of months away from the same kind of milestone. The
features in it were probably pretty well defined a year ago or so. Sad, but
that's kinda how it goes. Software is hard.

"SteveM" <SteveM[at]discussions.microsoft.com> wrote in message
news:A3FB7966-25F7-4F2C-BD48-802B70B1DA5C[at]microsoft.com...
- quote -

Any suggestions as to how to set up irregular paychecks and payments in a
budget in Money 2006? My spouse is a teacher and gets paid ten months per
year and our son's tuition is paid ten months per year. I have these set up
in Bills but when I try to use Autobudget it enters data for twelve months,
not ten. I know you can enter budget information manualy but this seems to
defeat the purpose of Bills and Autobudget. I don't think there is a solution
but I'd be glad to find out I'm wrong. Maybe this should be an enhancement
for Money 2007.