Each year a series of compliance updates and documentation revitalisation / updates are needed within the University’s finance systems.

Compliance Updates

To ensure that the University meets its financial compliance obligations a yearly proposal is submitted to hold a pot of days which will be drawn upon through the year.

Examples of compliance updates from previous years and potential updates for future years include;

•             PCIDSS compliance work

•             eFin login password changes raised from security concerns

•             Fraud protection patches

•             International bank validation

•             Patches driven by browser updates

•             Essential updates to cSeries

•             Supplier self-service patch

It is proposed these compliance updates are managed and reported on using the

Project Services processes and tools i.e.  JIRA and PM webpages.   These

changes are expected to be sizeable pieces of work (i.e. 5 or more days of work). Application Management may undertake this work however it would be coded to a project.

Document Revitalisation / Updates

There is a need to gather the required changes from across the finance teams and the Project Management to coordinate the input from Finance, ABS and IS Applications Production support.