Agresso Support
Finance Division
[email protected]
Ext 55010
Project Code Set-up Notes
A. Project Code – Enter the code that you wish to create; this should be four letters followed by two or
four numbers. The first and second letter should represent the relevant cost centre, the third should
denote the code type and the fourth is up to you, but is often used to group codes. The numbers are
usually sequential. E.G. Finance (FI), Admin (A) might be FIAA01.
B. Description – Enter the name/title of the project code.
C. Project Manager – Enter the name of the primary budget authoriser for this project. Any requisitions
raised on this project will go to this person. If the Project Manager is not currently an Agresso User,
they must complete an Agresso User form in order to be trained and set-up on the system.
D. RESNO – Enter the Resno (Resource/Personnel Number) of the Project Manager.
E. Email Addresses – You can enter up to two email addresses to receive reports for this project if
necessary.
F. SAP – Select YES or NO to indicate if the project should be made available on SAP for expenses and
payroll transactions.
G. VAT Matrix – Select YES or NO to indicate if the project will be used for commercial VAT standard rated
supplies only (Normally only for commercial projects – third letter C, where not for
education/conferences). Selecting YES will ensure that the project is added to the VAT Matrix,
meaning that its default tax code for expenditure (requisitions etc.) will be overridden with PR (POP 20% Commercial). For these kinds of supplies, VAT is recoverable.
H. Funds Checking – Select SPECIFIC or GENERAL to indicate the level of funds checking to be carried out
for this project. SPECIFIC means that it will be checked at project code level, GENERAL means that it
will be checked at cost centre & type level E.G. For FIAA01; specific = FIAA01, general = FIA.
I.
Trading Type – Select PRIMARY or NON PRIMARY to indicate the type of trading that the project will be
used for. This relates to the University’s annual corporation tax computation, where our trading
activities are divided between Primary and Non Primary. Our Primary trading type is education, so Non
Primary would apply to any project code not related to education. In the main, Non Primary projects
will be commercial (third character “C”) or commercial research. More detailed guidance is available
on the Finance Intranet Site.
J.
HESA1 Relation – Enter the relevant HESA1 relation(s) for the project. If multiple HESA1 relations are
to be used, please enter the values and their respective percentages in the fields to the right.
K. PRJ1 Relation – Enter the relevant PRJ1 relation for the project.
L. FRS102 Relation - Enter the relevant FRS102 relation for the project. Further notes are available on the
Finance Intranet.
Matt Blundell
1
Version 3.0
Updated: February 2017
Agresso Support
Finance Division
[email protected]
Ext 55010
M. Research and KTP Projects Only
i.
ii.
iii.
iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.
xiv.
xv.
Matt Blundell
2
Customer ID – Enter the Agresso customer ID relating to this project.
Customer Ref – Enter the reference number you have with the customer if applicable.
Investigator Name – Enter the name of the project investigator.
Investigator Resno – Enter the project investigator’s resno.
Sponsor – Enter the sponsor name if applicable.
College – Enter the code of the relevant College.
School – Enter the code of the relevant School.
PR Contact – Enter the number denoting the relevant PR Contact.
Res Type – Enter Y or N to indicate if the research type is Generic or Not Generic respectively.
Project Type – Enter the relevant Project type code.
Contract Start Date – Enter the project’s start date.
Contract End Date – Enter the project’s end date.
Valid From Date – Enter the date that the project should be available to use from.
Euro grants; Original documentation required – Select whether original receipts etc. will be
required for transactions on this project.
Account Relation(s) – Enter a list of any specific account codes that should be linked to the
project for use when inputting transactions, e.g. Research income/Payments to Partners
expenditure.
Version 3.0
Updated: February 2017