FINANCIAL APPROVERS: Design Beth A. Meiser

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

subDelegated signature authority How/what are we delegating? Is delegation PU specific or across the university? Beyond PU, are there other subdelegations to track?

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

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.

Questions? Insert Text and Contact Information