eExpenses information for approvers

The approvals hierarchy will be set up within SAP Concur.  Departments, UAS sections and participating colleges will provide details of the individuals who will be approvers for their projects and cost centres to ensure each claim is forwarded to the appropriate person for checking and approval. The approval levels within SAP Concur are as follows:

  1. Budget holder review (approval limit is zero): budget holder (for example the task manager, PI, supervisor or other manager) for the GL (optional) or project code (mandatory) checks and approves the claim to progress through the system to the next level 
    [In some instances this approval level might not be required]
  2. Approval level 1 (approval limit is 1 pence): finance officer (or equivalent) checks and approves the claim to progress to the next level (mandatory)
  3. Approval level 2 (approval limit up to £5000): finance manager (or equivalent) checks and approves all claims.  Provides final approval for claims of up to £5000 and approves claims of more than £5000 to progress to the next level (mandatory)
  4. Approval level 3 (approval limit up to £10,000): senior departmental approver or Divisional Financial Controller checks and provides final approval for claims of more than £5000, up to £10,000 (mandatory)
  5. Once all relevant approvals have been obtained, the Central Finance Division payments team make any required checks and process claims for payment via Oracle 

Expense claims for very senior staff follow a specific workflow as outlined in the University expenses policy (PDF).  For example, final approval of Heads of Department claims will be by the appropriate Head of Division, Divisional Secretary or Divisional Finance Controller.

Approver responsibilities

BUDGET HOLDER

  • Confirms that the activity has taken place and is legitimate to charge to their budget
  • Considers any relevant restrictions (for example, funder, donation, trust fund or any departmental terms and conditions)

APPROVER LEVEL 1

  • Checks that the expense is in line with the expenses principles as outlined in the University expenses policy (PDF). Checks include confirming receipts are correct and explanations are reasonable. [Many checks will be built into SAP Concur, for example do the numbers add up, is the claim signed?]
  • Confirms the claim is coded appropriately
  • Considers any relevant restrictions (or example, funder, donation, trust fund or any departmental terms and conditions)

APPROVER LEVEL 2

  • Confirms compliance with the expenses principles as outlined in the University expenses policy (PDF), taking assurance from the claimant and the budget-holder declarations that the costs are legitimate business expenses
  • Takes overall responsibility for confirming this is a legitimate expense to be refunded
  • Authorised signatory for claims of up to £5000

APPROVER LEVEL 3

  • Confirms compliance with the expenses principles as outlined in the University expenses policy (PDF), taking assurance from the claimant and the budget-holder declarations that the costs are legitimate business expenses
  • Takes overall responsibility for confirming this is a legitimate expense to be refunded
  • Authorised signatory for claims of up to £10,000

 

Frequently asked questions (FAQs)

Expand All

No.  SAP Concur does not allow for 'self approval' so there are rules in place so that someone who submits an expense claim is then not in the approval chain for that claim

Some fields will be automatically populated in SAP Concur, which means checking of individual expense claims by the Central Payments team within Finance Division will be significantly reduced.  This will free up their time to investigate problems or queries, and to undertake post payment analysis of claims using the SAP Concur reporting capability

  • The individual expense items will be routed to the appropriate approver
  • The claim will only move forward to the next approval level when all the relevant project or GL code items have been approved

Funder rules will not be checked automatically by the system.  However, we have built rules into SAP Concur to display messages and guide behaviour for claimants and approvers

  • The claimant will need to enter the coding for GL or project codes in order to create their claim
  • However, as an approver you can correct errors on a claim (for example, use of the wrong GL cost centre or project code) but it is recommended that you try to educate claimants to get this information right first time
  • As an aid, the most recently used cost codes are visible at the top of the drop down boxes
  • You can reject it by selecting the 'Return to Employee' button which means it will be sent back to the claimant for further explanation, with a message explaining why it has been sent back to them 
  • If you want another approver's opinion, you can use the 'Approve and Forward' button and select the appropriate person
  • No, not as such. As an budget-holder approver, you can add delegate approvers. This is useful to cover absences 
  • The delegate would act in lieu of the default approver, rather than as an additional step in the process
  • A 'master account' can be set up as the approver and then individuals must be assigned as delegates to perform the checks/approvals.  This way, the checking/approving tasks can be shared between members of a team
  • It is also possible to use the 'Approve and Forward' functionality if you want to add someone to the approvals process
  • Additional steps cannot be built into SAP Concur at this stage
  • There is an 'Approve and Forward' function that can be used to help with this
  • Otherwise, we will help make it work for your department

Yes, by email. You can switch these email notifications off but would then need to check SAP Concur regularly to ensure you action submitted claims

Yes, the claim and receipts can be printed if required.  The printed claim shows all the information held on the system and receipts can be printed individually

  • Yes, the claim name will be loaded to R12
  • Additionally, a Claim Key will also be loaded to R12, so there will be more than one way of locating the claim in both systems
    [The Claim Key is a system generated number, unique to the University]

Initially there will be improved reporting available from Oracle.  We are exploring what SAP Concur reporting can deliver

An approver (and their delegates) can view and access all the claims they have approved