Business Finland

Preparing for a Business Finland R&D audit

What a Business Finland R&D audit checks, what triggers one, and the documentation and habits that let a funded company pass it without stress.

An audit is not an accusation. Public funding comes with the reasonable condition that the money went where you said it did, and audits are how that’s verified. Companies that treat the possibility of an audit as a design constraint from day one find it a non-event. Companies that don’t can face disallowed costs and repayment demands for a project that was, in substance, fine — they simply couldn’t prove it.

Audit scope and procedures follow your funding decision and current Business Finland rules. This is the general shape and how to be ready.

What an audit is checking

At its core, an audit tests one thing: can you substantiate the costs you claimed? It looks for evidence that the money was spent on the project as described, within the rules and the approved terms. That means checking things like:

that claimed personnel hours are backed by real working-time records
that costs are genuinely attributable to the project, not general business expenses swept in
that subcontracting was real, at arm’s length where relevant, and within the rules
that costs fall inside the approved period and categories
that the reported work actually happened and matches the content reports

What tends to trigger scrutiny

You can’t always predict an audit, and some are routine. But certain things raise the odds or the intensity:

large or unusual cost items, especially heavy subcontracting
related-party transactions (buying services from owners or connected companies)
inconsistencies between cost reports and content reports
weak or missing time records
material drift between the approved plan and what was actually done

Notice that several of these are self-inflicted. Clean, consistent reporting doesn’t just pass audits — it reduces the chance of a hard one.

The documentation that carries you

An audit is won or lost on records that already exist. The essentials:

Contemporaneous working-time tracking. The single most important thing. Hours logged as the work happened, not reconstructed later. This substantiates your largest cost category.
Cost evidence. Invoices, contracts, and a clear trail linking each cost to the project.
Subcontracting documentation. Agreements and evidence of what was delivered, especially for anything with a related party.
Evidence of the R&D itself. Enough record of the activity and results to show the work described was actually done.

If these exist, an audit is a retrieval exercise. If they don’t, it’s a reconstruction under pressure — and reconstructed records are exactly what auditors distrust.

Prepare from day one, not on notice

The mistake is treating audit prep as something you start when an audit is announced. By then the evidence either exists or it doesn’t. The real preparation is operational hygiene throughout the project: time tracking from the first day, disciplined cost attribution, tidy subcontracting paperwork, and reporting that stays consistent. A company running this way is always audit-ready and never has to scramble.

If an audit comes

Engage straightforwardly. Provide the records, be responsive and precise, and don’t be defensive — a well-run project with good documentation has nothing to fear. Where a genuine issue surfaces, addressing it honestly is far better than obscuring it.

The takeaway

The best audit preparation isn’t a document you produce on demand — it’s the way you ran the project. Track hours from day one, attribute costs cleanly, keep subcontracting tidy, and keep your reports consistent. Do that and an audit is administrative rather than existential.