Specify the ID of the user responsible for administration of the budget. This field defaults to the current user, but you can modify this value.

The user you specify receives e-mails when budget amounts are overrun if you have selected the option to send e-mails on errors and warnings.

The system sends the e-mail to the address defined in User Maintenance (36.3.1) for the user specified in the Login field. See User Guide: QAD Security and Controls for details on user settings and User Guide: QAD System Administration for details on setting up e-mail.

Specify a budget currency. The field defaults to the base currency for the domain, but you can modify this value.

If you specify a currency other than the base currency, the system uses a specific budget exchange rate type to convert between the budget currency and the base currency. If a budget exchange rate for the two currencies is not defined, the system uses the current accounting exchange rate.

See Exchange Rate Types for more information on exchange rate types.

Choose whether the system validates if a reporting period is open when a transaction is posted for that period.

No Action: The system lets users enter transactions in closed/reported periods.

Warning: The system warns the user that the period is closed/reported, but lets the user save the transaction.

Error: The system warns the user that the period is closed/reported, and prevents the user from saving the transaction.

Reporting periods for budgets are set up in Report Period Create. See Budget Report Periods.

Select to budget using quantities, such as machine hours, kilowatt hours, or other quantifiable values. You can then link GL accounts defined to accept units of measure to the budget.

The Budget daemon compares the quantities entered for the GL account to the budgeted quantities. For example, a budget structure can include accounts for tracking kilowatt hours. The daemon updates the budget with the kilowatt hours entered for the account.

Choose how the system responds if the budget amounts from the start of the budget period to date, for the entire budget, or for a particular budget period are overrun. In each field, the options are No Action, Warning, or Error.

No Action: The system allows the user to enter transactions that cause overruns.

Warning: The system warns the user that the budget is overrun, but allows the user to save the transaction.

Error: The system prevents the user from saving a transaction that overruns the budget figure.

Select the field to enable the online budget check.

Each time a linked budget account is specified in banking entry, journal entry, customer and supplier invoices, open item adjustment, or petty cash activities, the system determines if the new transaction causes the budget amounts to be overrun.

In addition, if you choose Warning or Error in the Overrun (YTD), Total Overrun, or GL Period Overrun fields, the system displays a warning or error if a transaction causes a budget overrun for the corresponding time frame.

Select the relevant field to send an e-mail to the budget administrator if an overrun error or warning occurs. The system sends the e-mail to the address defined in User Maintenance (36.3.1) for the user specified in the Budget Administrator field.

The system generates errors or warnings when the budget is overrun and if Error or Warning is selected in one or more of the Overrun (YTD), Total Overrun, or GL Period Overrun fields.

Specify the entities that update actuals for the budget. A budget can link to one or more entities that share the same COA shared sets used in the budget structure. The entities can be in the same or different domains.

The Budget daemon only links actuals postings to budget topics if the postings originate in one of the entities specified in this field.

If you specify more than one entity, the system updates and compares actuals from all entities in the list to the budget amounts.