1 / 42

Claiming procedure, financial report

Financial Reporting Procedure Lead Partner Seminar 14th November 2012 City Hotel, Londonderry/Derry, Northern Ireland, UK Gustaf Forsberg. Claiming procedure, financial report. Document retention.

fala
Download Presentation

Claiming procedure, financial report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Financial Reporting ProcedureLead Partner Seminar14th November 2012City Hotel, Londonderry/Derry, Northern Ireland, UKGustaf Forsberg

  2. Claiming procedure, financial report

  3. Document retention NOTE: In case of an audit, all project partners must preserve copies of ALL supporting documents until three years have passed after Programme closure. We recommend that supporting documentation is preserved at least until year 2021. Lead Partner and Partners must also consider national legislation regarding preservation of accounting material.

  4. General information 1 (3) • Two types of budgets in an application • Project specific cost budget • Common cost budget When claiming and distributing common cost throughout the project partnership: • Certification of Common cost has to be done by the holder of the common cost First Level Controller (FLC). • A specific template for Common Cost certification has to be filled in by the FLC • The holder of the common cost will include the total common cost in the SoE for the reporting period when the cost was originally occurred. • Distribution of common cost is made by an invoice between the different partners, the invoice should be supported by documentation that common cost have been certified by the holders First Level Controller.

  5. General information 2 (3) When claiming and distributing common cost throughout the project partnership: • The partners will include their share of the common costs in the SoE for the reporting period when the common cost were paid and put into their accounts. • The holder will report the common cost payments from other partners in the SoE, most likely in a specific budget line, for the reporting period when the payments were received and registered in the accounts. The payment will reduce the common cost to a net cost for common activities in the Lead Partner SoE, and not be reported as a revenue.

  6. General information 3 (3)

  7. Explanation of National Controllers 1 (3) • The use of National Controllers is a new feature within the European Co-operation. • National Controllers have one main task, to ensure that a reliable and functional national control system is in place in its nation. • National Controllers are responsible for OLAF reporting, in case of any irregularities • National Controllers designate First Level Controllers (FLC’s) to perform the check. • Only costs certified by the FLC’s can be eligible for ERDF or ERDF equivalent funding • Different systems in different countries • Current list of National Controllers and First Level Controllers are available on our website and annexed to our Programme Manual

  8. Explanation of National Controllers 2 (3) Example; National Controller Finland “Decentralised system”: Finnish Ministry of the Interior Department for Development of Regions and Public Administration Regional Development Unit P.O.Box 26, FI-00023 Government (From 1.1.2008: Ministry of Employment and Economy, details to be specified) • Finnish system • Note that the Ministry of Employment will not carry out the control. It will only be the responsible authority.

  9. Explanation of National Controllers 3 (3) Example; National Controller Sweden “Centralised system”: County Administrative Board of Västerbotten Industry and Commerce Department 901 86 Umeå Tel: +46 90 10 70 00 Fax:+46 90 10 71 00 vasterbotten@lansstyrelsen.se Mr Håkan Törnström Head of Unit +46 90 10 71 31 hakan.tornstrom@lansstyrelsen.se • Swedish system • Note that listed person is the person responsible for the unit of Industry and Commerce at CAV. • A desk officer / FLC responsible for the task of certififying expenditure will be appointed • Currently no fee will be charged for Swedish partners to get their expenditure certified.

  10. Supporting Documents to National Controllers • National Controllers will most likely require the following documents in order to complete a first level of control: • Statement of Expenditure (signed by authorized person) • Ledger for the current reporting period (every partner should keep separate project accounts) • Time sheets (for part time employees) • Copies of all invoices and receipts • Employment contracts (for full time employees) • Model to show the office costs distributed proportional + supporting documentation (when applicable) • Transaction list • Partner activity report • Other relevant documentation Note: It is up to each programme partner country to establish what documentation they will require. This is only an indicative list of required documentation for the first level control provided by the NPP 2007-2013

  11. Statement of Expenditure by MS Partners to National Controller 1 (5)

  12. Statement of Expenditure by MS Partners to National Controller 2 (5)

  13. Statement of Expenditure by Partners to National Controller 3 (5)

  14. Statement of Expenditure by Partners to National Controller 4 (5)

  15. Statement of Expenditure by Partners to National Controller 5 (5)

  16. Supporting document to Statement of expenditure • Currency conversion sheet All project partners have to state their expenditure in Euro, only programme partner countries using Euro are Finland and Ireland. All other partners except for Finnish and Irish partners have to convert their currency into Euros. This is made by applying the Currency conversion sheet, and its principles: Currency conversion sheet (for non Euro partners) The currency used in the Northern Periphery Programme 2007-2013 is Euro (EUR). Consequently all non Euro partners must convert their expenses from national currency into Euro. All costs should be converted using the monthly Commission rate for the last month in the current reporting period. The Commission exchange rates is found on the official website: http://ec.europa.eu/budget/inforeuro/index.cfm?fuseaction=countries&Language=en

  17. Currency Conversion Sheet 1 (2)

  18. Currency Conversion Sheet 2 (2)

  19. Supporting documents from National Controllers • National/First Level Controllers will send two main document to the project partner: • Certificate of Expenditure • Checklist of First Level Control

  20. Certificate of Expenditure 1 (4)

  21. Certificate of Expenditure 2 (4)

  22. Certificate of Expenditure 3 (4)

  23. Certificate of Expenditure 4 (4)

  24. Common errors • Copies of Certificate of Expenditure and First Level Control checklists • Missing Blue-ink signatures, First Level Control and Lead Partner • Certificate of Expenditure missing pages • Whole or part of document • Missing First Level Control checklist • Whole or part of document • Old template for the Certificate of Expenditure • Template from previous programme period • Not the latest version, i.e. missing budget lines 10 and/or 11 • Statement of Expenditure instead of Certificate of Expenditure

  25. Documents from Partner to Lead Partner • All partners have to sumbit the following documents to the Lead Partner: • Certificate of Expenditure (blue ink version) • Additional documents which may be part of the Partnership Agreement: • Partner Activity Report (as part of the aggregated activity report) • FLC checklist • Transaction list of all expenditures • Other documents agreed within the project partnership

  26. Lead Partner Principle • Role Lead Partner: • Be the policeman of the project, ensure that all certified costs can be connected to eligible/approved project activities (Letter distributed) Northern Periphery Programme recommends that all partner Certificates of Expenditures (CoEs) to the LP are supported by a partner activity report, clearly outlining the individual partner activities, and a transaction list to demonstrate which costs are related to what activities. AND It is vital that the Lead Partner can extract the individual partner activities from the overall Work Package activity plan, potentially outline individual partner activities in the partnership agreement.

  27. Lead Partner Principle • Role Lead Partner: • Note The NPP does not require the first level controller of the Lead Partner to check the complete claim. This is instead done by the Managing Authority something we believe saves time in the payment process. However, according to EC guidelines this is within the scope of the Lead Partner’s FLC.

  28. Lead Partner Principle • Role Lead Partner: • Acting as link between the project partners and the programme • Submitting the project progress report • Overall responsibility for project coordination • Formal beneficiary of ERDF and ERDF equivalent funding • Lead Partner has the responsibility to distribute the funding received from the NPP 2007-2013 among the project partnership in accordance with the spending by the partners. The complete Lead Partner responsibilities are stipulated in Regulation: (EC) 1080/2006, Art 20

  29. Documents from Lead Partner to the Secretariat • In order to make a complete progress report the Lead Partner has to submitt the following documents to the Secretariat: • Activity Report • Project claim • Summary of Certificates of Expenditure • Certificate of Expenditure (blue ink version) from all partners • FLC checklists from all partners • Note that the Activity Report and COE have to be submitted both in blue ink version, by post, as well as an electronic version by e-mail.

  30. Project Claim 1 (4) Project Claim is the formal decleration of spending by the Lead Partner in order to receive ERDF or ERDF equivalent co-financing, 2 page document:

  31. Project Claim 2 (4)

  32. Summary of Certificates of Expenditures 3 (4) Summary of CoE is the ”calculator” to ensure that the project claim has been compiled correctly: Fill in the reported period for the project, and the claim number

  33. Project Claim 4 (4) NOTE: Self generated table after completing the Summary of Certificates of Expenditures

  34. Desk check errors • Wrong expense period on Payment claim • In relation to decision • In relation to Certificate of Expenditures • Wrong bank information, IBAN / BIC • In relation to application/decision • In relation to latest supplied information • Claim signed by person not authorized to sign for the organisation • In relation to enclosure 2 of decision • In relation to latest supplied information • Faulty Summary of CoE:s page • Partner listed on wrong funding source compared to the decision, mostly of the 20% flexibility area • Expenditure amounts entered in Summary of CoE:s not corresponding with Partner CoE. • Faulty 2nd page of project claim due to mistakes in Summary of CoE:s page • Match funding amounts entered in Summary of CoE:s not corresponding with Partner CoE:s • Costs certified in budget lines that has nothing budgeted for.

  35. Desk check errors • Invalid Certificate of Expenditure • First Level Controller not approved by National Controller • Wrong expense period, expenses approved beyond the claim period • Deductions missing from page 3 of CoE • Wrong expenditure and match fundin • Amounts in current CoE versus previous CoE, doesn’t correspond. • Insufficient First Level Control Check list • All answers not ticked • Answers on questions 8-12 “Not checked” or “Not applicable”, without specifying reason why.

  36. Project changes • Changes in project implementation • All changes in project implementation have to be communicated to the Secretariat and need preapproval before becoming eligible (this includes changes in project end date, budget changes and changes in the activity plan). The degree of the change (major or minor) will be determined by the Secretariat: • Rule of thumb: • Please describe the change in the budget, activity plan, partnership, project co-ordinator staff, project time period, indicators or other changes to the Secretariat in an e-mail. • Justify the need for change • Describe the impact on project implementation. • Maximum number requests two per year.

  37. Project changes • Changes in project implementation • Minor changes are: • A change with no major impact on project implementation and less than 40 000 Euro increase in one project budgetline • A change of a minor impact is approved in regular correspondence between the Lead Partner and the Secretariat, i.e request and answer by e-mail. • All changes are to be listed in the project activity report and should confirm the picture that the changes are of a minor degree when being described in its full context. • Major changes are: • A change with a major impact on the projects implementation or more than 40 000 Euro increase in one project budgetline • A change with a major impact normally requires a formal request in a specific template and the Secretariat will provide information on how to make that request. • Different bodies can be responsible for approving the change (Managing Authority and Programme Monitoring Committee) • Major changes on the overall project can normally only be allowed once during the project lifetime.

  38. Budget changes template

  39. What happens after your project submission

More Related