Post Award Handbook

6. Project Closure

Key Users

Central Research Finance team
Departmental Hub teams
Departmental & Finance Administrators

At a glance

This section explains what is required to bring projects to a formal close. It focuses on completing financial requirements, meeting funder expectations, and ensuring all necessary actions are taken to properly conclude the award.

Print this content

A pending closure review takes place once a project has finished, before it is formally closed in the finance system. The purpose is to confirm that all project activity has been completed and that the financial position is accurate. This includes checking that all expenditure and adjustments have been posted, any outstanding income has been received, and any final reports, claims or invoices have been submitted. The review helps ensure that the project can be closed with no outstanding financial activity.

Process Toolbank FAQs

6.2 Locking Codes

Overview

Locking a project code in SAP prevents any further financial transactions from being posted to the project. This usually takes place once the project has passed its end date, helping ensure that costs are not charged outside the approved funding period. Locking the code acts as a financial control while final checks and closure activities are completed, supporting accurate project records before the project is formally closed.

Process Toolbank FAQs

6.3 Closing Codes

Overview

Closing a project code in SAP is the final step in the project lifecycle. It takes place once all project activity has been completed, including the posting of final costs, submission of any required claims or invoices, and any outstanding income or refunds have been settled. This formally marks the project as complete in the University’s financial system.

Process Toolbank FAQs

Finance Office

Post Award Handbook

6. Project Closure

Key Users

At a glance

Print this content

Contents: