A Begin Accrual Date is used by storage accounts. On this date, the accrual in each storage and diversion account is reset to zero. In addition, this date is used by the carryover methods on the account.

A rent return date can be configured for the entire accounting system. Currently, this value is not used anywhere.

An accounting run, like a simulation run, has a period of dates for which accounts solve. The Begin Accounting Period is where the users sets the time range of the accounting system. The date can be before the initial simulation timestep but cannot be after the initial simulation timestep.

The End Accounting Period is where the user sets the timestep where the accounting system ends. The end timestep can be after the last simulation timestep but cannot be before it. In other words, the accounting system must cover the entire simulation time but can extend beyond it in either direction.

As a model evolves, you might change the run times (start, finish, timestep size) with the Run Control (Control, then Run Control). Objects created before the changed run times will differ from objects created after the changed run times. Similarly, accounts created before the run time change will differ from those create after the run-time change with respect to their slots’ time ranges and timestep sizes. RiverWare copies the run time information from the run controller to the accounting system so that it knows if there is a possibility that accounts are not synchronized with the run control information.

As with the physical system, slots in the accounting system can be set many times in a run. The accounting system configuration allows you to put a limit on the number of times that any accounting slot can be set; if that limit is exceeded, the run aborts with an error message. Be careful to set this limit high enough for the solve-into-the-future behavior of some accounts.

This toggle controls whether the accounting system will allow accounts to have priority dates that are the same, or if each account’s priority date must be unique. Priority dates are used to allocate water in rules functions.

Define Water Owners, Water Types, Release Types and Destination Types by selecting the icon. Delete using the icon.

Each account can have a water owner which is used to classify the account. The Water Owners area allows the user to create the set of water owners available to the accounts.

Each account can have a water type associated with it. The Water Types area allows the user to create the set of water types available to accounts.

Release Types are used to classify supplies. The Release Types area allows the user to create the set of release types available to supplies. For example, the user can specify that there are Fish and Irrigation Release types. The release type applies to a supply, this is the water coming out of or going into an account. We will not add release types at this time.

Destination Types are also used to classify supplies. The Destination Types area allows the user to create a set of Destination Types available to supplies. Both Destination Types and Release types become very useful when using the rule controller to define how much and from where water is released.

Prior to version 6.3, you configured accounting specific units in the Accounting System Configuration. Now units are specified in the active Unit Scheme; see Unit Schemes in User Interface for details. See Slots for information specific to accounting units.