Dates are extremely important for processing and reporting on transactions. Please use special care when entering and approving transactions to ensure use of the correct dates. A new "Transaction Dates in Workday that Drive Accounting" guide is available in the Administrative Resource Center (ARC). This document outlines which transaction dates drive operational accounting entries in Workday. Using the quick guide should help prevent operational journal errors from occurring.
New training modules on Adaptive Planning are now available in BuckeyeLearn . The modules listed below are recommended for Ohio State employees needing to use Adaptive Planning for the Spring 2023 planning cycle.
Policies owned by Business and Finance will no longer be hosted on the B&F website. Instead, they will be hosted by the University Policy Office at policies.osu.edu . The B&F website information will continue be available as usual since the document links will be changed to point to the new host. However, any personal browser bookmarks will need to be updated. The website work should be completed by Friday, January 27 .
Effective Friday, January 20 , Position Restriction costing allocations can use grants. Any new positions that are grant funded can now be set up at the Create Position step. Cost Center Managers are not required to update the previously recorded costing allocations to accommodate the new functionality.
The Controller's Office is currently unable to run payroll encumbrance adjustments due to an error within Workday. Workday plans to deliver a fix the weekend of February 4 . Therefore, all payroll encumbrance balances represent approved activity through January 3 . Any changes to hires, terminations, funding, FTE, or pay rates after January 3 will not be reflected in the General Ledger or in the "Positions for Plan" reporting until the issue is resolved. We apologize for any inconvenience. The payroll encumbrances will be updated as soon as possible.
The "Workers on Leave for Cost Center Managers" report is being enhanced to return workers on leave that have "active" leave on or after the date the report is run through the end of the fiscal year. This will allow units to see future dated leaves that may impact their fiscal year encumbrances. The change will be migrated into production the week of January 23 .
To provide additional reporting attributes, fields for "Fiscal Year," "Fiscal Period," and "Job Code" will be added to the "Find Journal Lines – OSU Payroll Detail" report output on Tuesday, January 24 .
In addition, a new "Pay Component/Fringe Basis" report prompt will be added. The new prompt is a freeform field that can be used to return all rows associated with an earning. This change will help show fringe rates associated with an earning code.
The "Find Spend Authorization Summary – OSU" report has been enhanced to provide additional flexibility and insight into tracking the completion of the International Travel Acknowledgement of Understanding (AOU).
The fields listed below have been added to the report output.
"International AOU Required" - Shows "yes" if the Spend Authorization requires completion of the AOU questionnaire. "International Travel AOU Acknowledgement Date" - Shows the date selected on the questionnaire if completed. If the questionnaire has not yet been completed, this will be blank.
In addition, a checkbox has been added to the prompt (Spend Authorizations with International AOU Only), that when selected will only return results in the report that include an International Travel AOU questionnaire. To view only "in-process" Spend Authorizations, it is also recommended to use the status prompt filter as well.
Please be aware that the HR team has been completing a clean-up on positions retroactively, involving changes between staffing models (position management to job management, or vice versa). This may cause financial users to see unmapped fringe benefits on reports. Unfortunately, there have been cases where this has affected sponsor billing as well. The Enterprise Business Solutions (EBS) team is aware of the issue and is actively working to investigate the impact so that a central correction can be completed. There is no other fix right now unless it is completed centrally, and end users are being made aware that a resolution is in the works.
