Who this is for: Businesses starting or delivering an investment supported by an Italian funding scheme.
Collecting every invoice at the end is not the same as preparing a grant report. A business needs to explain what was purchased or completed, why it belongs to the project and what evidence supports its progress. Organising that information as work happens is more effective than reconstructing it months later.
Requirements vary between schemes. The structure below helps coordinate technical and financial teams, but must be adapted to the official instructions and the award conditions applying to the particular investment.
Establish the reporting basis before organising the evidence
Keep the call, award decision, relevant manuals and formal clarifications together. Identify which expense categories, outputs and deadlines need to be demonstrated. Assign an owner to each requirement: the person creating a document may not be the person responsible for checking it or submitting it.
Grants do not all use the same mechanism. The cited Invitalia guidance addresses expenditure and progress in R&D projects; Horizon Europe may instead use lump sums linked to completion of work packages. Evidence preparation should reflect the actual funding basis rather than an assumed universal invoice checklist.
References: Invitalia — Contratti di sviluppo, linee guida di rendicontazione R&S · European Commission — Lump-sum funding in Horizon Europe
Connect evidence across the life of each expense
For a purchase reported on an actual-cost basis, build a readable connection between commitment, delivery, invoice and payment. Add technical evidence explaining the result, such as an acceptance record, report or produced file. Check separately which documents the scheme actually requires and which simply help internal control.
Scroll horizontally to see every column.
| Stage | Question to answer | Evidence to organise |
|---|---|---|
| Commitment | What was ordered? | Accepted quotation and order |
| Delivery | What was received or performed? | Delivery and activity records |
| Expense | What is being charged? | Invoice connected to the supply |
| Payment | How was the expense settled? | Relevant financial evidence |
| Outcome | Which project activity is complete? | Test record, report or technical output |
Make the archive understandable to someone else
Organise records by project and cost item, using names that include an identifier, document type and date. Distinguish originals, working copies and approved versions. Avoid leaving the only explanation of a change in a technician's personal inbox or in an informal message to the purchasing team.
Maintain a compact register beside the archive: amount, supplier, project item, delivery status, payment status and missing evidence. The register exposes gaps while the folders preserve the documents. A full directory without clear connections can be as difficult to review as one with information missing.
Reconcile technical progress and expenditure regularly
Agree a review frequency proportionate to the project. Compare work completed, documents received and expenses recorded. Look for ordinary inconsistencies: vague descriptions, amounts differing from the order, unreconciled partial payments or a delivery that does not yet cover the agreed technical result.
Give each discrepancy an owner and a traceable resolution. Do not rewrite a description to make the activity appear different from what took place. Where supporting information is needed, request it from the document's issuer and preserve the connection with the previous version so the record remains understandable.
Address changes before the final submission
A different supplier, configuration or date may affect the approved project. Record what changes, why and its technical and financial consequences. Then check whether notification or authorisation is required. A technically equivalent solution should not automatically be treated as administratively interchangeable under a funding scheme.
Studio Dinamico connects technical progress with funding documentation. Regular coordination helps produce a final account describing the work actually performed, alongside expenditure information that can be followed and checked. It also identifies missing evidence while the people and suppliers involved can still provide useful clarification.
Before preparing a payment request
- Confirm the instructions, version and deadline applying to the project.
- Connect each declared item to the evidence required by the scheme.
- Reconcile amounts and payments where the funding basis requires it.
- Check that changes followed the relevant procedure.
- Have someone other than the document collector review the assembled file.
Common questions
Do invoices also prove technical completion?
Not always. An invoice records an expense, whereas testing, delivery records or reports may be needed to establish the result. Check the scheme's instructions for the evidence required.
Can one document checklist be used for every grant?
An internal filing structure can be reused, but the same documents may not be sufficient. Cost categories, deadlines, funding bases and payment procedures can differ between programmes.
Sources and further reading
Apply this to your project.
Is the project starting or already underway? We can help connect progress, expenditure and the evidence to prepare.
Request an investment eligibility review