The Load GL Interface Process and Budget Checking

Budget dates determine against which budget period the transaction data is checked. If a budget date exists from bill entry at the bill line distribution level, the Load GL process (BILDGL01) carries that date forward. If you do not provide a budget date at the bill line distribution level in bill entry, the Load GL process populates the budget date with the accounting date that is on the bill header. The Finalization process (BIIVC000) determines invoice dates and accounting dates. It populates the invoice date with the current date if it is not provided in bill entry, and it populates the accounting date with the invoice date if the accounting date is not provided at bill entry. Because you run the Load GL process after the Finalization process, the accounting date is populated by the Finalization process on the bill header, even if you do not provide one at bill entry.

The system creates accounting entry types that are not involved in budget checking with a blank budget date. The system creates future accounting period entries for realized revenue and realized discounts or surcharges with a budget date value that is derived from the future period accounting date option that you define on the Installation Options - Billing - Integration Options page, which is either the first or last day of the accounting period.

The system checks multiple process status flags throughout bill processing to ensure that a bill is ready to be picked up by downstream processes.

The Load GL process sets the budget checking header status to N if you selected the Commitment Control option for PeopleSoft Billing on the Enable Commitment Control page. This is done for revenue, distribution and surcharge, InterUnit expense, and statistical distribution accounts only. Otherwise, the Load GL process sets the budget checking header status to V. The system sets the budget checking line status to the same value as that of the header status.

The Load GL interface creates accounting entries with an initial PeopleSoft General Ledger distribution status of H (hold) for those transactions with a budget checking header status of N.

The Journal Generator process does not pick up accounting entries with a PeopleSoft General Ledger distribution status of H until they pass the Budget Checking process and their PeopleSoft General Ledger distribution status is changed to N (none).

If commitment control is enabled at the installation level on the Enable Commitment Control page:

Load GL Sets Budget Checking Header Status to	Budget Checking Line Status	Accounting Entry GL Distribution Status	Can Be Processed by Budget Checking Process?	Can Be Processed by Journal Generator Process?
N (not budget checked).	N (not budget checked).	H (hold)	Yes	No

Status values after successful Budget Checking process:

Budget Checking Process Sets Budget Checking Header Status to	Budget Checking Line Status	Accounting Entry GL Distribution Status	Can Be Processed by Budget Checking Process?	Can Be Processed by Journal Generator Process?
V (valid budget check).	V (valid budget check).	N (none)	No	Yes

Status values after unsuccessful Budget Checking process:

Budget Checking Process Sets Budget Checking Header Status to	Budget Checking Line Status	Accounting Entry GL Distribution Status	Can Be Processed by Budget Checking Process?	Selected by Journal Generator Process?
E (error in budget check).	E (error in budget check).	H (hold)	Yes	No

The Load GL - Contract Asset process (BIACCRUE) creates accounting entries with a budget header status of V, enabling the Budget Checking process to bypass unbilled revenue accounting entries. Unbilled revenue accounting entries do not need to go through the Budget Checking process because these entries are automatically reversed during the next accounting period, and each bill is eventually invoiced and booked to the recognized revenue accounts.