|
agMIS Managing budgets, plans and forecasts |
[
Home ] [
Back ] [
Next ]![]() This budgeted expense, entered in January, is forecast to be due in August. It will reflect in planned cash forecast reports in the meantime, as well as in the expected unit cost of producing 'Soybeans'. And after that, it provides a basis for selective 'budget vs. actual' analyses, when or if that's useful. |
Perhaps you didn't notice at the
previous 'cash and taxes' screen, but a payment record with blanks in the
bank and check number spaces, is a 'payable' item in agMIS --
until the user adds payment information. It's the first level of
budgeting and planning in agMIS. (It's also a measure of
agMIS system efficiency. Compare this one-record method,
to the number of transactions required to move a 'payable' record to a
checkbook and tax entry, in accounting programs.) But agMIS forward planning features don't stop there. Some forward transaction estimates need 'budget vs. actual' research later, and instead of account-level budget aggregates, agMIS provides transaction-level budget entries, like the one shown here. Note how it's alike -- and how it's different -- from the 'actual' expenditure on the first screen, particularly the absence of bank and tax code spaces. It's an agMIS assurance that, even by mistake, an inattentive user can't corrupt his or her bank or tax records -- even accidentally! |
|
(c) Copyright 1998-2008 -- T. Murphy Associates |