The innovation manager hands in their notice, the last day is set, the handover gets three weeks in the calendar. Those three weeks decide whether the company can defend the funding already granted to it across the whole commitment period — or whether, ten years later, a tax audit or an ex post check by the project management agency ends in recovery demands because nobody can explain any more how budget allocations, time records and cumulation decisions came about. In the world of funding, losing knowledge to a staff change is not a soft topic but a hard compliance question with quantifiable audit risk.[2][1]
Why knowledge leaves with people
Research and innovation funding in Germany and at EU level lives on documents that take shape in people's heads before they reach any system: the reasoning for why a particular sub-task was classified as experimental development; the calculation behind why a given person-month is assigned to one work package and not another; the judgement on whether a state programme cumulates with a federal one under state aid law. ISO 30401 addresses exactly this category as tacit knowledge: implicit, person-bound knowledge in organisations is the central problem knowledge management has to address — explicit documents are easier to transfer but are often not where the value actually sits.[7]
In its dossier on employment stability, the IAB bundles the empirical picture on job tenure and turnover in Germany and documents structurally shorter tenures among qualified specialists in research- and knowledge-intensive industries; Destatis data on employment confirm that tenure in knowledge-intensive services and IT is regularly below average. For a company with live grant notices that means: across the commitment period of a state or federal grant — typically five years after completion, with Horizon Europe adding a five-year retention period after the project ends — a change in the responsible people is the norm, not the exception.[6][9][4]
Fraunhofer IAO describes staff turnover as a double-edged event: moderate turnover can accelerate transformation, excessive turnover produces knowledge loss and organisational instability. The core finding for handover practice: knowledge transfer is not primarily a documentation problem but a process problem. Anyone who starts documenting only during the notice period still has a chance with codifiable knowledge, but hardly any with the logic of judgement and decision — that builds up continuously over years and cannot be reconstructed retrospectively in a handover document. The OECD Skills Outlook 2023 puts the same pattern at the macroeconomic level: companies systematically underestimate the share of job-specific knowledge lost when someone leaves, and generally react only once the loss has already happened.[5][10]
For funding compliance the consequence is: the moment knowledge belongs in the platform is not the day notice is given. It is the day the decision was made — the day the work package was written, the cumulation check carried out, the budget allocation fixed. Every gap still open when notice is given can no longer be reliably reconstructed after the leaving date.
The audit view of handovers
For years the European Court of Auditors (ECA) has documented in its annual reports that a considerable share of quantifiable errors in research spending falls on staff costs — incorrect attribution of working time, missing time records, person-months that cannot be evidenced. The ECA classifies such findings as substantive when the auditor can no longer clarify the underlying facts with the recipient — often because the person who originally made the attribution is no longer available or left no trace.[1]
The audit perspective is sober. Article 20 of the Annotated Model Grant Agreement (AGA) for Horizon Europe consortia obliges the recipient to keep "adequate records and other supporting documentation" for all declared costs and to make them available throughout the retention period. "Adequate" is made concrete in the Commission's annotations: the records must make the declared costs unambiguously reconstructable, and the reconstruction must be possible for an auditor without recourse to oral explanation. That is the core standard: in five years' time an auditor should be able to work with the files at hand — not with a phone call to the former project lead.[4]
At national level the logic is identical. Point 6.1 ANBest-P obliges the recipient to retain the books, vouchers and other business documents for five years after submission of the proof of use; section 147(1) nos. 1 and 4a of the Fiscal Code sets a ten-year period for books, inventories and annual accounts. For accounting vouchers alone, the period was shortened from ten to eight years by the Fourth Bureaucracy Relief Act with effect from 1 January 2025 (section 147(1) no. 4 of the Fiscal Code); the record-keeping and costing basis that matters for funding audits, however, remains subject to the ten-year period. The Finance Ministry's GoBD set a traceability principle for documentation systems: an expert third party must be able to gain an overview of business and accounting transactions within a reasonable time, and that requirement applies not only at the point of creation but across the whole retention period — that is, across every staff change.[2][8][11]
In the BNBest-BMBF 98 for BMBF project funding, the ministry tightens the duties to cooperate: the recipient is obliged to cooperate actively in proof-of-use and ex post audits and to supply the underlying work results, time records and reasons for attribution even where the staff originally responsible have left the company. The risks of not cooperating are explicit: missing or incomplete evidence can lead to full revocation of the grant notice, not merely to a reduction of the items concerned.[3]
The five questions in detail
The five questions below are derived from the logic of the primary sources and form a minimum standard. They are phrased so that a person with no access to the departing innovation manager has to be able to answer them the day after that person leaves — purely on the basis of the documents in the platform.
1. Are all live and completed applications versioned and accompanied by a trace of the reasoning? In the funding process an application is never a final artefact but a sequence of versions between outline, full application, rounds of questions with the project management agency, amendment requests during the term, and interim reports. The AGA annotations to Article 19 (roles, competence and staff of beneficiaries) require that the allocation of tasks and decisions within the consortium is documented and traceable for auditors. At national level, ANBest-P and the administrative provisions to section 44 of the Federal Budget Code require an unbroken chain of reasoning for all changes to the approved project. What is in the application is one question; why it is in the application in exactly that form is the second — and the latter leaves the company with the person.[4][2]
2. Are vouchers and time records held complete in a searchable, audit-proof system? The GoBD require digital records to be unalterable, complete and traceable; changes have to be logged. ANBest-P no. 6.2 refers, for time recording, to the company's usual records; ECA audit practice shows, though, that informal Excel lists, email chains reporting hours, or records kept only on personal drives regularly lead to findings. In an audit context, "searchable" means: every person-month of a work package can be traced back to a voucher in seconds, without the auditor having to piece fragments together from several systems.[8][1]
3. Are audit trails for decisions, approvals and deviations traceable? Not every decision in a funded project is a formal amendment request. Budget reallocations below the de minimis thresholds defined in the ancillary provisions, extensions within the project term, staff changes within a work package — all of these matter in funding law but are not necessarily communicated outside the company. The traceability of the internal approval (who decided what, when, on what basis) is the typical blind spot the departing person takes with them. ISO 30401 expressly requires a knowledge management system to capture the context of decisions — not just their outcome.[7][3]
4. Is the programme-specific procedural knowledge documented? Every funding programme has its own deadlines, its own submission systems, its own contacts at the project management agency, its own formats for interim reports. The BSFZ application platform works differently from easy-Online at the BMBF, differently from the European Commission's Funding & Tenders Portal, differently from the submission portals of the state development banks. How to handle queries, the informal rules for amendment requests, the tolerances of the particular agency — this is experiential knowledge that appears in no information sheet. ISO 30401 calls this category "procedural and contextual knowledge" and explicitly requires organisations to maintain mechanisms for capturing and passing it on. Handling an application once without that context produces delayed reactions and therefore risk to deadlines.[7]
5. Is there a robust mapping from the funding pipeline to budget planning, including cumulation status? Funding never stands alone. De minimis volumes, GBER and FIBER intensities, thresholds under competition law, the prohibition on double funding under section 7 FZulG and the ancillary provisions of state programmes — all these restrictions are checked cumulatively per project and per company. In most mid-sized companies, the cumulation table is an artefact in the head of the person handling the applications. The ECA regularly names cumulation errors in its annual reports as a category of their own, because unlike arithmetic errors they arise not from the calculation itself but from incomplete context. Without a written link from pipeline to budget, every statement about cumulation is fragile once the person handling it leaves.[1]
What has to be documented in the platform
The five questions translate into a concrete list of documentation objects that have to sit in a central system independently of the departing person. The decisive rule is singularity: each object exists once, versioned, with a defined owner and with access for at least two people. Redundant copies on personal drives, in email folders or in chat threads are unusable for audit purposes, because audit-proofing under the GoBD cannot be established for them.[8]
Per project, the platform has to hold: the full application in the version approved, versioned with all earlier versions and rounds of questions; the grant notice including ancillary provisions and any amending notices; the costing table with person-month attribution per work package, linked to the underlying personnel master data; the time records per employee and month with a work package reference; invoices and payment records for materials and external services with a project-related description of the service; interim and final reports with the agency's responses; the cumulation documentation with all funding running in parallel for the same or adjacent projects; the decision history on changes, budget reallocations and staff changes during the term.[4][2][3]
At company level — not per project but across all of them — the platform has to hold: the continuously maintained de minimis declaration under Regulation (EU) 2023/2831 with the grants received in the last three tax years; the overview of funding intensities declared under the GBER per project and per aid category; the mapping matrix between funding pipeline and budget planning with the cumulation logic visible; the list of contacts held with project management agencies and approval bodies and the credentials for the submission portals; the programme-specific procedural notes (deadlines, habits around queries, tolerances). The last of these is contextual knowledge in the sense of ISO 30401 and decides whether a successor can act in the live pipeline or has to improvise on every query.[7]
A handover checklist with primary sources
A handover checklist for the last working day is a stopgap in practice; the real work happens continuously. Where notice has been given and there is only time left to close gaps, working sequentially along the primary sources helps. First: reconcile all live grant notices with the files in the platform — every item in the notice has to be findable in the application, the costing and the latest version of the report. The basis is section 44 of the Federal Budget Code with ANBest-P no. 3 (use in accordance with the purpose).[2]
Second: a completeness check of time and staff cost records for all person-months declared in the last twenty-six months. That reference period follows from the usual practice of ECA sample audits and BMBF ex post audits, which largely go back to the most recently completed reporting periods. Every person-month without a time record that can be evidenced is an open finding.[4][1]
Third: review the cumulation logic for every live grant. For each project, document which other public funds flow to the same eligible costs, what aid intensity that produces and whether the applicable GBER article limit is observed. For de minimis funding, update the rolling three-year total under Regulation (EU) 2023/2831.
Fourth: write down the procedural notes for each programme. Which agency contacts are on file, which patterns of query are typical, which submission deadlines fall in the next twelve months, which interim reports are in preparation. ISO 30401 refers to this as capturing "tacit knowledge" — precisely the part that becomes transferable only by actively writing it down.[7]
Fifth: bring a second person into the platform with read and edit rights for all relevant objects — not at the exit interview, but ideally in the first third of the notice period, so that questions can still be put to the departing person. Fraunhofer IAO names the temporal overlap of responsibilities — in practice a tandem or staggered handover model — as the central transfer instrument; without it, even complete documentation is partly unusable, because the context around the objects is missing.[5]
Protecting against findings in a tax audit
A tax audit looks at accounting vouchers and the costing logic behind them; an ex post grant audit additionally looks at the funding-specific documents. Both types of audit regularly take place long after the person who originally did the work has left. The timing is built explicitly into the GoBD: the traceability requirement applies not at the moment the voucher is created but at the moment of the later audit — and then regardless of who is still there to represent the company.[8][11]
Structural protection against findings works at three levels. First: redundancy of responsibility. Every funding object has a primary owner and a named deputy with the same rights in the platform; the deputyship is not nominal but evidenced by actual involvement in creating and maintaining it. The IAB dossier on employment stability bundles empirical evidence that shared responsibilities and overlapping job profiles dampen the effect of turnover on organisational knowledge in knowledge-intensive industries.[6]
Second: continuous rather than event-driven documentation. Every decision — a budget reallocation, a staff change in a work package, turning down a parallel grant, a cumulation check — is filed in the platform at the moment of the decision, with the reasoning, the date and the responsible person, not in an email and not in a personal notebook. The GoBD requirement of timely recording in bookkeeping carries over to funding documentation and is the only approach that withstands reconstruction after the fact.[8]
Third: audit simulation at regular intervals. An internal proof-of-use check, in which someone not actively involved in the project reconstructs a complete report using only the documents in the platform, reveals gaps while they can still be closed. This practice corresponds to the principle of independent review in the ISO 30401 requirements for a knowledge management system and to the ECA's audit follow-up concept. Gaps found are not evidence of a broken process but input for the next iteration of maintaining the platform.[7][1]
In sum. In funding compliance, keeping the knowledge is not a nice-to-have. The sum of the requirements in ANBest-P, BNBest-BMBF, the Horizon AGA, the GoBD and the Fiscal Code produces a documentation profile that cannot be created after the fact and that has to keep working independently of the departing person. The five questions are the minimum test; the checklist is the emergency route; continuous maintenance in an audit-proof platform is normal operation. upsmart represents applications, vouchers, hours, decisions and cumulation status as connected, versioned objects — so that one person leaving does not become an audit event.
- [1]Annual Report 2023 — Implementation of the EU budget (Statement of Assurance)European Court of Auditors · 2024Open source
- [2]General Ancillary Provisions for Grants for Project Funding (ANBest-P)Federal Ministry for Economic Affairs and Climate Action · administrative provision to section 44 BHO · 2019Open source
- [3]Special Ancillary Provisions for BMBF grants for project funding (BNBest-BMBF 98, form 0027a/07.25)Federal Ministry of Research, Technology and Space (BMFTR) · Profi form library · 2025Open source
- [4]EU Grants — Annotated Grant Agreement (AGA) V2.0, Art. 19 Roles & Art. 20 RecordsEuropean Commission · DG Research & Innovation · 2025Open source
- [5]The underestimated power of turnover — how staff changes can accelerate transformationFraunhofer IAO · blog · Moritz Maier · 2025Open source
- [6]IAB dossier — employment stability: job security despite growing flexibilisation? (data on job tenure and turnover)Institute for Employment Research (IAB) · 2024Open source
- [7]ISO 30401:2022 — Knowledge management systems — Requirements (first edition 2018, revised 2022)International Organization for Standardization · 2022Open source
- [8]Principles of proper bookkeeping and data access (GoBD) — Federal Ministry of Finance circular, second amendment of 14 July 2025Federal Ministry of Finance · 2025Open source
- [9]Employment — job tenure and length of service (microcensus)Federal Statistical Office (Destatis) · 2024Open source
- [10]OECD Skills Outlook 2023 — Skills for a Resilient Green and Digital TransitionOECD Publishing · Paris · 2023Open source
- [11]Fiscal Code section 147 — rules on the retention of documentsFederal Ministry of Justice · gesetze-im-internet.de · 2024Open source
The ten-year rule: audit obligations after the grant notice
In the ECA's sample of audited research transactions, one in four shows quantifiable errors. Staff costs are the number one source of error — and the biggest block of the budget.
The reuse lever: how an application platform pays for itself from cycle 2–3
NIH R01 resubmission data show the empirical advantage of the second submission. What that means for the roadmap of German funding applications.
ZIM 2026: what the BMWK reform changes for Mittelstand applications
New rates, new priorities, new deadlines — and what innovation managers should adjust in their pipeline planning now.
From the analysis into the application.
We show the platform on a real case.