CASRAI Dictionary

Tag: grant funding agreement

  • Horizon Europe Financial Reporting Field Guide

    Horizon Europe financial reporting is the process by which every beneficiary in a funded consortium declares its incurred eligible costs to the European Commission at the end of each reporting period, via a financial statement lodged on the Funding & Tenders Portal. A periodic financial report is the beneficiary-level cost declaration — covering personnel, subcontracting, purchase and indirect costs — that accompanies the technical report, triggers EU reimbursement, and (above a EUR 430,000 cumulative threshold) requires independent audit sign-off.

    For grant and research administrators, the financial statement is where compliance is won or lost. Cost-category misallocation, missing evidence and audit-threshold miscalculation are the recurring causes of rejected or queried claims. This field guide sets out the reporting cycle, the cost-category breakdown, the Certificate on Financial Statements (CFS) threshold, and the specific errors that trigger Commission pushback.

    What is the Horizon Europe periodic reporting cycle?

    A Horizon Europe periodic report combines a technical/scientific report with a financial report made up of each beneficiary’s financial statement. Accounting periods in Horizon Europe projects usually cover 18 months, and the coordinator must submit the complete periodic report within 60 days of the period’s end, per the Model Grant Agreement’s standard reporting terms.

    Each beneficiary prepares its own financial statement, has it electronically signed by a designated financial signatory, and submits it to the coordinator, who consolidates all statements before submission to the Commission via the Funding & Tenders Portal. From the second reporting period onward, a beneficiary can adjust a prior period’s declared costs — for example, correcting under- or over-declared amounts — which then flows through to the current period’s requested contribution.

    Missing the 60-day deadline does not usually void the claim outright, but it can defer the beneficiary’s costs into the following reporting period, delaying reimbursement. Deadline extensions are generally only available for the final reporting period.

    What cost categories must appear in the financial statement?

    The Horizon Europe financial statement, set out in Annex 4 of the Model Grant Agreement, requires beneficiaries to declare actually incurred, eligible costs against a fixed set of categories. Indirect costs are not itemised: they are calculated automatically as a flat rate of 25% of eligible direct costs (excluding subcontracting, financial support to third parties, and unit-cost volunteer time), under Article 6 of the Model Grant Agreement.

    Category What it covers Key reporting rule
    A. Personnel costs Employees, natural persons under direct contract, seconded staff, SME-owner/natural-person beneficiary time Daily-rate method; capped at 215 declarable day-equivalents per person per calendar year across all EU/Euratom grants
    B. Subcontracting Tasks outsourced to a third party under the beneficiary’s usual purchasing practices Must follow best-value-for-money procurement; ideally listed in Annex 1
    C. Purchase costs Travel and subsistence; equipment (usually depreciation-only); other goods, works and services Itemised explanation required once purchase costs exceed 15% of declared personnel costs
    D. Other direct costs Financial support to third parties (if permitted by the call); internally invoiced goods and services Same 15%-of-personnel-costs itemisation trigger as Category C
    Indirect costs Overheads not directly attributable to the action Flat rate of 25% of eligible direct costs, calculated automatically — no separate evidence required

    The “Use of Resources” itemisation rule is a common trip point: once Category C or D spend exceeds 15% of a beneficiary’s declared personnel costs for the period, the portal requires a detailed breakdown of major cost items down to that threshold, starting with the highest-value items first.

    When does a Certificate on Financial Statements (CFS) apply?

    A Certificate on Financial Statements is an independent auditor’s report — or, for public bodies, a report from a competent independent public officer — that verifies the eligibility and accuracy of a beneficiary’s declared costs. Under Article 24.2 of the Horizon Europe Annotated Model Grant Agreement, and as set out in Data Sheet Point 4.3 of the Grant Agreement, a CFS is mandatory once a beneficiary’s cumulative EU contribution requested for costs reaches EUR 430,000 over the life of the grant.

    • The threshold is assessed per beneficiary, not per consortium or per project — each partner is evaluated individually.
    • It applies to the EU contribution actually requested for costs, not the total project budget.
    • A CFS is typically required at final payment, though a Grant Agreement’s Data Sheet can also require one at an interim reporting period.
    • Costs already audited by the granting authority do not need to be re-included in the CFS and do not count toward the threshold.

    Some older guidance in circulation still cites a EUR 325,000 threshold, which was the figure attached to the original wave of Horizon Europe Model Grant Agreements. Administrators relying on legacy templates or older third-party summaries should check their own Grant Agreement’s Data Sheet Point 4.3 directly, since the currently applicable AMGA text sets the CFS trigger at EUR 430,000 per beneficiary.

    Why do financial statements get queried or rejected?

    Cost rejection at review or audit stage is rarely arbitrary — it follows a predictable pattern of documentation and classification failures. The most frequent causes are:

    • Misclassified costs — for example, subcontracted work declared as personnel costs, or purchase costs booked under the wrong sub-category.
    • Insufficient supporting documentation — missing invoices, timesheets, employment contracts, or delivery confirmations that an auditor or the Commission cannot trace back to the accounting system.
    • Personnel cost calculation errors — daily-rate miscalculations, timesheet-to-payroll mismatches, or exceeding the 215 day-equivalent annual cap across combined EU and Euratom projects.
    • Ineligible costs — expenditure incurred outside the eligible period, disallowed hospitality costs, or items not connected to the action described in Annex 1.
    • Non-compliant subcontracting — subcontracts awarded without following the beneficiary’s usual best-value-for-money purchasing practices.
    • Technical/financial inconsistency — a financial statement that does not match the effort or progress described in the accompanying technical report, such as unexplained over- or under-spending against person-months.

    Most of these are preventable with real-time cost tracking rather than end-of-period reconstruction. Reconciling declared costs against the general ledger before submission, and keeping personnel time records current throughout the period, removes the majority of documentation-based rejections before they reach the Commission.

    Common questions on Horizon Europe financial reporting

    What is the reporting period for Horizon Europe?

    Horizon Europe accounting periods typically run for 18 months, and the consortium coordinator must submit the full periodic report — technical and financial — within 60 days of the period’s end. The final reporting period may be shorter, and deadline extensions are generally only available for that last period.

    What is the audit threshold for Horizon Europe?

    A Certificate on Financial Statements becomes mandatory once a beneficiary’s cumulative EU contribution requested for costs reaches EUR 430,000 over the grant’s duration. The threshold is assessed per beneficiary under Article 24.2 of the Annotated Model Grant Agreement, not against the consortium’s combined budget.

    What this means for research administrators

    Horizon Europe financial reporting rewards continuous cost tracking over end-of-period reconstruction. Institutions running multiple Horizon Europe grants should monitor each beneficiary’s cumulative requested EU contribution against the EUR 430,000 CFS threshold from the outset, since crossing it late in a project leaves little time to engage a qualified independent auditor. Equally, personnel time recording against the 215 day-equivalent annual ceiling needs to be checked across all EU and Euratom grants a researcher is involved in, not project by project in isolation.

    For institutional research administration teams, the practical takeaway is procedural: reconcile the financial statement against the general ledger before locking it for review, confirm the CFS requirement against the specific Grant Agreement’s Data Sheet Point 4.3 rather than generic guidance, and treat the technical report and financial statement as a single, cross-checked submission rather than two separate exercises. As reporting cycles repeat every 18 months for the life of a project, the administrative overhead compounds — building the tracking discipline into normal project operations, rather than into a pre-deadline scramble, is what keeps periodic reports moving through the Commission without dispute.

  • Grant Funding Agreement: A Research Administrator’s Guide

    A grant funding agreement is the binding document that sets out what a funder will pay for, what the recipient must do, and how that spending will be checked. It fixes the scope of eligible costs, the reporting schedule, ownership of intellectual property, and the conditions under which the funder can suspend, recover or terminate the award. For research administrators, the practical task is not learning the legal theory but knowing exactly which clauses to check — obligations, reporting, IP and cost eligibility — before an authorised signatory signs.

    A grant funding agreement can be defined precisely: it is a legal instrument of financial assistance, distinct from a procurement contract, under which a funder transfers money to a recipient to carry out an approved activity in the public or funder’s interest, subject to defined terms and conditions rather than a specified deliverable.

    What is a grant funding agreement?

    A grant funding agreement records the terms on which a funder — a government department, a research council, a foundation or a funding agency — provides money to a recipient organisation to deliver an approved project. Unlike an invoice-triggered purchase, the funder is not buying a specific product; it is supporting an activity that serves its own objectives, under conditions the recipient must meet to keep the money.

    In the UK, the Cabinet Office’s Model Grant Funding Agreement (MGFA) is the reference template for central government departments and their arm’s-length bodies. The long-form MGFA (version 1.3, published 1 December 2025 on GOV.UK) runs to 63 pages and is designed for basic, complex and high-risk awards; a short-form version applies to grants up to £100,000. Government Functional Standard GovS 015 — Minimum Requirement Six: Grant Agreements (updated 21 May 2026) states that “all government general grants shall be awarded through robust grant agreements … which reflect the Grants Functional Standard.”

    Every properly drafted grant funding agreement should set out, at minimum: the scheme’s purpose and objectives; eligible and ineligible expenditure categories; a data protection policy; counter-fraud and audit provisions; delivery milestones and reporting obligations; breach and recovery clauses; and a payment schedule.

    How does a grant funding agreement differ from a contract?

    The distinction turns on control and deliverables, not the document’s title. A research contract or sponsored research agreement is a procurement instrument: the funder specifies a defined output, retains significant direction over the work, and can treat non-delivery as a breach. A grant funding agreement supports a broader activity, gives the recipient substantially more autonomy over method, and treats failure to hit every milestone — provided funds were used as intended — as a monitoring issue rather than automatically a breach.

    Feature Grant funding agreement Research/sponsored contract
    Primary purpose Support a public-interest or mission-aligned activity Procure a specific research service or product
    Funder control Limited — monitoring and assurance only Significant — direction over scope and method
    Recipient autonomy Substantial, within eligible-expenditure terms Constrained to agreed deliverables and schedule
    Non-delivery consequence Usually treated as a delivery/monitoring issue Can constitute a breach with legal remedy
    Typical IP position Recipient usually retains IP, subject to funder terms Funder may claim ownership or exploitation rights

    A hybrid instrument, the cooperative agreement, also exists where the funder provides financial assistance but takes on substantial, ongoing involvement in delivery — a middle ground between a grant and a contract. Administrators should assess the actual clauses — degree of funder control, specificity of deliverables, breach remedies — rather than the label, since a document titled “grant” can carry contract-like obligations if it locks in specific outputs and heavy funder direction.

    What do the UK and EU model grant agreements cover?

    Research administrators working across UK and EU-linked funding streams will encounter several distinct model agreement families, each with its own conventions on cost eligibility, reporting and IP.

    • UK Cabinet Office MGFA — the default template for UK government general grants, cleared by the Government Legal Department, tailored per scheme, covering eligible/ineligible expenditure, subsidy control compliance and a Statement of Grant Usage requirement.
    • FP7 Model Grant Agreement — used for projects funded under the EU’s Seventh Framework Programme (2007–2013); costs and obligations were set out in Annex II general conditions attached to the core agreement.
    • H2020 Model Grant Agreement — the template for Horizon 2020 (2014–2020) awards, accompanied by the European Commission’s Annotated Grant Agreement (AGA), a clause-by-clause interpretive guide widely used by EU grant offices.
    • Horizon Europe Model Grant Agreement — the current EU framework programme (2021–2027) template, which carried forward the H2020 structure with updated open-access, data-management and lump-sum funding provisions.
    • ERC Model Grant Agreement — a variant used by the European Research Council for frontier-research grants, typically single-beneficiary and structured around the Principal Investigator rather than a consortium.

    Across all of these, the recurring checkpoints are the same: which costs are eligible (direct, indirect/overhead, in-kind), what reporting cadence applies (technical and financial), how IP and results ownership is allocated between beneficiaries, and what triggers suspension or recovery of funds. Professional bodies such as EARMA (European Association of Research Managers and Administrators), ARMA and NCURA publish practical guidance for administrators reconciling these model-agreement conventions with institutional policy.

    What should administrators check before signature?

    Before an authorised signatory executes a grant funding agreement, institutional research offices should verify the following against the specific award terms, not a generic checklist assumption:

    • Eligible expenditure categories — confirm which direct and indirect costs qualify, and whether any category (for example, VAT recovery or contributions in kind) is expressly excluded.
    • Reporting obligations — check the required frequency and format of financial and delivery reports, and whether a Statement of Grant Usage or equivalent independent assurance is mandated.
    • Intellectual property and results — establish who owns outputs, what publication rights apply, and whether the funder retains any licence or access rights.
    • Breach and recovery clauses — identify the performance tolerances that trigger payment suspension, clawback or termination.
    • Subsidy control and compliance — for UK public-sector grants, confirm the agreement addresses UK subsidy control rules; for EU-linked awards, confirm Horizon Europe or equivalent state-aid provisions are reflected.
    • Amendment route — confirm the agreement specifies a formal addendum or variation process for scope, budget or timeline changes agreed after signature.

    Any listed clause that is genuinely absent from a draft agreement should be flagged and justified in the institution’s business case or governance sign-off, not silently accepted.

    Common questions, answered

    What is a grant funding agreement?

    A grant funding agreement is a legal instrument under which a funder provides financial assistance to a recipient to deliver an approved activity. It sets out eligible expenditure, reporting obligations, IP terms and the conditions for suspension, recovery or termination of funding.

    What does “grant agreement” mean in practice?

    In practice it means the recipient has accepted defined terms and conditions attached to the funding offer — covering purpose, budget, milestones and assurance requirements — that both parties, funder and recipient, are contractually bound to follow for the life of the award.

    How does a funding agreement work?

    Once signed, funds are released against a payment schedule, usually linked to satisfactory financial and delivery returns rather than paid entirely upfront. The funder monitors compliance through periodic reporting and, where required, an independent accountant’s assurance report.

    What is the purpose of grant funding?

    Grant funding exists to support activity that serves a public or mission-aligned objective — research, service delivery or innovation — that the funder could not or would not procure directly, while retaining enough oversight to ensure funds are used as intended.

    What this means for institutional grant administration

    Grant funding agreements are converging in structure across jurisdictions — UK government schemes, Horizon Europe, and major foundations all now specify eligible expenditure, reporting cadence, IP terms and breach remedies as standard clauses, even though the labels and templates differ. The practical discipline is the same regardless of funder: read the model agreement’s clause-by-clause guidance (the AGA for Horizon Europe, the MGFA’s completion notes for UK grants), map every eligibility and reporting requirement against the institution’s own finance and compliance systems, and confirm the amendment route before, not after, a variation is needed. Institutions that build this check into pre-signature governance reduce the two most common post-award failure points: disallowed costs at final reconciliation, and disputed IP ownership at publication. This pre-signature discipline sits within the wider practice of research administration, where standardised checks reduce compliance risk across a funding portfolio.