Financial Approvers System Objectives and Delegated Authority Overview
Explore the design, system objectives, subdelegated signature authority, approvals, activity codes, and questions related to financial approvers. Learn about developing tools for Planning Units, establishing approval limits, and more. Discover how delegation works within the university setting and track various approvals efficiently.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
FINANCIAL APPROVERS: DESIGN Beth A. Meiser 1
SYSTEM OBJECTIVES Develop a tool that Planning Units (PU) can use to maintain/update: Planning Unit data and authorization to use tool Establish approvals and approval limits Define PU specific Activity Code descriptions 2
SUBDELEGATED SIGNATURE AUTHORITY How/what are we delegating? Is delegation PU specific or across the university? Beyond PU, are there other subdelegations to track? 3
APPROVALS Can use to define a number of types of approvals Concur based on organization and $$ limit SciQuest based on organization and $$ limit GL journal approval based on $$ limit Potentially other uses in the future? Authority can cascade from PU to dept to individual organizations Example: Could define CFAO authority at PU level and indicate that it applies to all orgs under the planning unit Mass change functionality for employee changes 4
ACTIVITY CODES PUs potentially would be able to change the description of their activity codes Update would be transferred to Oracle Alternatively, maintenance could be performed centrally. 5
QUESTIONS? Insert Text and Contact Information 6
