Budget Checking in PeopleSoft Billing

The Budget Checking process processes only those accounting entries that are created by the Load GL Interface process with a budget checking header status of N (not budget checked). It determines the fiscal year and period from the budget date of the accounting line entry and checks the accounting entry against the recognized revenue budget for that fiscal year and period.

Note:

Deposit (DEP), Deposit Applied (DAPP), Deposit Refund (DREF), and Payment with Corporate Voucher (PYXES) lines are not truly revenue accounts, although they are assigned to a revenue account type. To avoid budget checking these lines, the system sets the budget checking header status to V.

Deposit Refund Fees (DRFF) lines are true revenue lines; the system treats them normally.

The Budget Checking process determines if the budget allotted is sufficient. If you select Control in the Commitment Control Option field on the Source Transaction Definition - Options page, the system assigns a status of E (error) to transactions that do not pass budget checking. If you elect to track transactions with a budget, the system assigns a status of W (warning) to transactions that do not match the budget allotment.

If the accounting entry successfully passes budget checking, the Budget Checking process increases the recognized revenue ledger by the transaction amount, updates the offset ledger balance to maintain balanced commitment control ledgers, and updates the PeopleSoft General Ledger distribution status to N (none). Transactions that pass budget checking, those with a PeopleSoft General Ledger distribution status of N, will be processed the next time that you run the Journal Generator Process (FS_JGEN).

Note:

When using both Chartfield Inheritance and Budget Checking, run the Load GL (BILDGL01) process and Budget Checking (FS_BP) process prior to running the Load AR (BILDAR01) process.