Newsletter
Cost allocation is one of the most sensitive financial areas in European projects. Even when costs are real and necessary, poor allocation logic or weak documentation can lead to ineligible costs, reductions, or audit observations.
This article focuses on the most common cost allocation pitfalls we see in Horizon Europe (actual cost and lump sum), LIFE, and I3 projects, with practical examples and clear prevention strategies.
What cost allocation really means in EU-funded projects
Across Horizon Europe, LIFE and I3, cost allocation is not about “splitting costs fairly” — it is about demonstrating a clear, auditable link between a cost and the action described.
A cost must be:
If allocation logic is unclear, the cost is at risk — regardless of the programme.
1. Arbitrary splitting of shared costs
What goes wrong
Shared costs (staff, software, equipment, services) are split across projects using rough percentages (“around 30%”, “estimated use”) without a measurable driver.
Why this is risky
Auditors do not accept “reasonable estimates” unless they are backed by objective allocation keys.
How to avoid it
Always define a cost driver and document it. Examples by programme:
- Horizon Europe (actual cost): A data scientist works on two HEU projects. Allocation must be based on timesheets with real hours per project, not estimated monthly percentages.
- LIFE: A monitoring tool is used for biodiversity tracking in one LIFE project and water analysis in another. Allocation should be based on number of measurements, field days, or monitored sites, not equal splitting.
- I3: A consultant supports several innovation pilots. Allocation can be based on hours per pilot, deliverables produced, or SMEs supported, clearly recorded.
2. Weak link to the description of the Action
What goes wrong
Costs are charged because they are “project-related”, but the beneficiary cannot point to a specific task or deliverable requiring them.
How to avoid it
Every cost should answer one simple question: Was the cost necessary for the action?
Good practice
- Add a Task / Work Package reference to every cost internally.
- For unforeseen costs make sure they are correctly linked to the action.
Programme example
Under Horizon Europe lump sum and LIFE, costs must match the actual work delivered: wrong cost allocation can reduce the lump sum, and LIFE communication, monitoring, and replication costs must be explicitly tied to mandatory activities in the work plan.
3. Incorrect allocation of personnel costs
Personnel costs are the most frequently corrected cost category.
Typical issues
- Generic or incomplete timesheets
- Staff without clear task attribution
- Management or coordination time not justified
- Inconsistent calculation methods
How to avoid it
- Timesheets must be project-specific and task-aware
- Allocation must reflect real time spent
- The same calculation method must be applied consistently
Programme examples
Across Horizon Europe (actual cost), LIFE, and I3, staff time must be tracked and allocated accurately by project and task: project managers should record hours per WP/task, field technicians must split time correctly between monitoring, implementation, and dissemination, and business development roles must clearly separate project-specific support from general organisational work.
4. Double funding through overlapping allocations
What goes wrong
The same cost is charged to:
- Two EU projects, or
- An EU project and another public grant, or
- A project and internal operating budget
Why it matters
Double funding is strictly forbidden, even if unintentional.
How to avoid it
- Maintain a central register of shared costs
- Clearly identify funding sources in accounting records
- Cross-check allocations before submission
5. Misuse of indirect costs and internal services
Common problems
- Incorrect application of indirect cost rates
- Internally invoiced services including profit
- Lack of cost breakdown for internal charges
Practical note on utilities (water, electricity)
In most cases, water and electricity are treated as part of indirect costs/overheads (i.e., covered by the indirect cost method applied in the programme).
However, they may be charged as “Other Goods & Services (OG&S)” only if you can:
- Explicitly separate the consumption attributable to the project (e.g., dedicated meter, clearly defined facility area/time, equipment-level measurement, or another objective method), and
- Demonstrate that 100% of the charged amount relates to the project (so you’re not double counting overheads), and
- Keep clear evidence supporting the calculation and the allocation key (invoices, meter readings, internal methodology, and traceable accounting entries).
If those conditions cannot be met, utilities should remain under indirect costs to avoid eligibility risk.
6. Treating procurement as normal purchasing
What goes wrong
Costs are allocated correctly, but procurement rules are not respected:
- Insufficient market comparison
- Missing justification of best value for money
- Incomplete documentation
Key rule
A well-allocated cost is still ineligible if procurement is non-compliant.
Example
In LIFE, external monitoring services must be transparently selected and clearly cost-justified, while in Horizon Europe and I3, subcontracting must align with Annex 1 descriptions and follow fair procurement practices.
7. A practical cost allocation checklist (all programmes)
Before submitting any financial report, ask:
- Is the cost clearly linked to the action?
- Is the allocation based on an objective driver?
- Is documentation complete and retrievable?
- Is there any risk of double funding?
- Does it follow usual accounting practice?
- Is the cost reasonable and necessary?
If any answer is “no”, the cost is at risk.
Cost allocation is a project-wide responsibility
Most allocation issues are not finance errors — they start with:
• Unclear task definitions
• Lack of internal guidance
• Weak coordination between technical and financial teams
Strong cost allocation systems reduce risk, simplify audits and protect project funding across Horizon Europe, LIFE and I3.