Description of the decision to be made
The payroll legacy payroll process creates VP4 documents that post the salary disencumbrance transactions to DEFINE and this process will not have many changes. For example, these items will remain the same:
- Rolling up the transactions to the account level on a VP4 document
- Creating these transactions in each of the 3 (on-cycle) payroll runs each month.
- Including service dates on the transactions
- Not using DEFINE codes.
- Using object code 0100
- Running an annual process (AQJG0702) to disencumber any remaining encumbrances
The primary differences will be:
- Currently, the amount for the salary disencumbrance transactions are calculated by adding up the amounts paid out via the salary transactions on the VP4 document for the account. Going forward, we will not be calculating the amounts. Instead, we will use the amounts provided by Workday which will not be based upon the amount of the salary transactions (example: 1/12 of the annual encumbrance amount). (Note: How the amounts are calculated is a function of Workday and is not attributable to bridging.)
- Currently, both the salary and salary disencumbrance transactions are all on the same VP4 document. Because the salary disencumbrance amounts will not be based upon the salary transaction amounts, the salary disencumbrance transactions will be on a separate document from the salary transactions.
Concerns/Feedback/Outstanding from subcommittee
None.
Recommendation from subcommittee
Move forward with the processing the Salary Disencumbrance Transactions as explained herein.
Timeframe
Present at the November 15, 2017 steering committee meeting.
Recommended decision maker
Workday Steering Committee based on recommendation from Workday Bridging Subcommittee
Recommended Campus Stakeholders to Engage
ASMP Bridging Team (includes payroll, accounting, budget, sponsored projects), ASMP Bridging Subcommittee
