A grant is not won when the decision arrives. It is won when the last report is approved, the payment is made — and none of it is reclaimed later. The part in between, rarely considered while writing the application, is reporting and the audit trail.
What the funder actually checks
- Were the activities carried out as promised? And if something changed, was the change approved?
- Are the costs eligible and evidenced? Every euro has to connect to an activity and a document.
- Were the results and indicators achieved? And is that supported by anything other than words?
Most trouble arises at the second point — not because money was spent wrongly, but because the connection cannot be demonstrated afterwards.
The audit trail: every euro must reach an activity
An audit trail is an unbroken chain from application to bank statement. In practice, every cost must allow this path to be walked:
| Step | Document |
|---|---|
| Why the cost was incurred | The activity and budget line in the application |
| How the supplier was chosen | Quotations, justification, procurement documents |
| What was ordered | Contract or purchase order |
| What was received | Acceptance note, work report, photo, the deliverable itself |
| What was invoiced | Invoice referencing the project |
| Whether it was paid | Payment order or bank statement |
| How it was booked | Separately in accounting under a project code |
If one link is missing, the cost is not evidenced — even if it was entirely legitimate. That is how most clawbacks are born.
The most common mistakes
- Personnel costs without timesheets. If someone works on the project part-time, there must be a record of what they did and when.
- Unapproved change. An activity done differently, or a cost moved between budget lines without the funder's consent.
- Cost outside the period. The invoice date or payment date falls outside the eligibility period.
- Weak procurement. One quotation where three were required.
- Publicity requirement ignored. The funder's logo or reference missing from materials where it was mandatory.
- Unevidenced indicator. "We trained 40 people" without an attendance list is a claim, not proof.
The interim report is not a formality
The interim report is where mistakes are still cheap. If the cost line structure or the documentation does not fit, you can fix it for the rest of the project. If the same mistake is found only in the final report, it applies to the whole project volume.
So make the first report as early and as precise as you can — it is effectively a free audit.
A routine that keeps reporting painless
- Open separate accounting for the project. Cost lines under a project code from day one.
- File the document immediately. Contract, acceptance note and the link to the activity next to the invoice — not three months later when nobody remembers.
- Keep timesheets as you go. A table filled in retroactively is the most visible red flag there is.
- Collect evidence during the activity. Attendance list, photo, agenda, output — you cannot create them afterwards.
- Get changes approved before, not after. One email to the funder is cheaper than a clawback.
- Retain documents for the required period. An inspection can arrive years after the project ends.
How Projektiassistent helps
In Projektiassistent, activities, cost lines and decisions belong to the same project, so the "cost → activity → result" link is not manufactured while writing the report — it exists all along. The decision log and change log show what changed, when and why: exactly what an inspector asks for. The cost line view keeps spend and free balance visible throughout. See also: eligible costs and co-financing.
Summary
A clawback usually comes from a missing document, not from fraud. Build the audit trail at the start of the project rather than at the end: separate accounting, documents filed with the cost, timesheets kept as you go, evidence gathered during the activity, and every change approved. Then the final report is a summary, not a rescue operation.
If you want activities, costs and decisions in one place from day one, start here: projekt2.projektiassistent.ee.