Introduction
If you’ve been preparing Horizon Europe proposals recently, you’ve probably seen more and more calls labelled as “Lump Sum.”
Many organisations assume this means:
“Less financial reporting. Less risk. Easier projects.”
But that’s only partially true. To really understand lump sum, you need to understand how payments actually work.
What Is a Lump Sum?
A lump sum is a fixed amount of money agreed in advance for completing a defined piece of work.
You are not reimbursed based on what you spend.
You are paid based on whether the agreed work is completed.
That’s the core concept.
How Payments Work in a Lump Sum Project
A common misunderstanding is that you are only paid at the very end of the project.
That’s not correct. In most lump sum Horizon Europe projects:
- You receive a prefinancing payment at the start.
- Then, at each reporting period, the Commission evaluates which work packages have been completed.
- Payment is released for the work packages that are validated as completed.
So payments are periodic — but they are linked to completed work, not to declared costs.
A Simple Example
Imagine your project includes:
- WP1 – €120,000
- WP2 – €200,000
- WP3 – €80,000
Your organisation is responsible for WP2.
You begin execution:
- You pay salaries.
- You pay subcontractors.
- You use internal resources.
But the €200,000 linked to WP2 will only be paid once WP2 is officially validated as completed.
If WP2 is delayed by six months, the payment is also delayed. The Commission does not analyse how much you spent. They assess whether the work is done.
How Do Organisations Cover Costs in the Meantime?
This is where lump sum changes the financial dynamic.
Organisations must:
- Finance execution internally until validation.
- Manage their own cashflow carefully.
- Absorb delays if validation is postponed.
If a work package cannot be closed, the payment tied to it is not released.
That means liquidity planning becomes critical.
What Happens If a Partner Is Late?
In lump sum projects, work packages are often interconnected.
If your WP depends on input from another partner and that partner delays:
- The WP cannot be formally completed.
- Validation is postponed.
- Payment may be blocked.
This is what many coordinators call the “domino effect.” Financial simplicity does not eliminate dependency risk. It shifts it to execution and coordination.
How Is This Different from the Traditional Model?
In traditional (actual cost) projects:
- You declare real costs periodically.
- Even if technical delays occur, you may still declare eligible costs incurred.
In lump sum projects:
- Spending money does not trigger payment.
- Completion of agreed work triggers payment.
The logic moves from cost-based reimbursement to performance-based validation.
Is Lump Sum Less Risky?
It removes one type of risk: cost ineligibility.
But it increases another: execution and cashflow risk.
Traditional model = control of costs.
Lump sum model = control of delivery and coordination.
Understanding that shift is essential before preparing or managing a lump sum Horizon Europe project.
Final Thought
A lump sum project means you are paid for results, not for expenses. Payments are linked to completed work packages, not to actual spending. Financial reporting may be simpler, but execution discipline and cashflow planning become more critical.
Lump sum doesn’t remove risk. It changes where the risk lives.
Horizon Europe Reporting: A Practical Guide to Grant Agreement Article 20
Article 6 in Horizon Europe: Practical Tips for Eligible and Ineligible Costs
