Budget Checking PeopleSoft Payroll Transactions

You can interface payroll encumbrance data to Commitment Control by running the Encumbrance GL Interface process (PAYGL03.sqr) ).

Use the Actuals GL Interface process (PAYGL02.sqr) to send actual payroll expenditure transactions to General Ledger.

You budget check encumbrance and expenditure transactions in General Ledger after receiving them from Payroll.

The source transactions from the Actuals GL Interface process (PAYGL02.sqr) liquidate the transactions from the Encumbrance GL Interface process (PAYGL03.sqr).

After General Ledger and Commitment Control receive the source transactions, run the Budget Processor from the Budget Check HR Payroll page in Commitment Control to update the control budgets.

If there are any error exceptions when you budget check from Commitment Control, the Budget Processor automatically overrides the entire transaction and generates a warning exception. You can receive warning exceptions for payroll transactions using the HR Payroll Exceptions component.

Run the Journal Generator process after running the Budget Processor. You run Budget Processor directly against the payroll accounting table. Journal Generator creates journals out of the same payroll accounting table; however, it marks the journals with Skip Commitment Control so that the items are not budget checked again by the budget processor from the resulting journals.