Topics
Winning the grant is the start of a reporting relationship, not the end of the paperwork. Treat it lightly and you risk clawback.

A grant is taxpayer money on loan against a promise to report honestly. Sloppy reporting can turn an award into a repayment.
When the Bewilligungsbescheid arrives, the celebration is justified - but the document itself is a set of binding conditions, not a congratulations card. It defines exactly what you are funded for, how the money is paid out, what you have to report and when, which costs are eligible, and what happens if you deviate. Read it the day it arrives, twice, and make a calendar of every reporting deadline it contains. The single most common cause of trouble later is a founder who filed the Bescheid without reading the Nebenbestimmungen (the ancillary conditions) attached to it, then violated one without knowing it existed.
We are not your legal advisor and the binding terms are whatever your specific Bescheid says - but as a category, these documents share a structure, and knowing the structure lets you read yours faster.
Read the Nebenbestimmungen
The ancillary conditions attached to your Bescheid (often the ANBest-P or similar) carry the real obligations - reporting deadlines, eligible-cost rules, change-notification duties. They are easy to file unread and expensive to violate unknowingly.
Grant money is rarely handed over as one lump sum at the start. Instead you call it down - the Mittelabruf - in tranches as you need it, usually against actual or imminently due costs. For an EXIST stipend administered through a university, the institution typically handles the mechanics and the stipend reaches you on a schedule. For project grants where you control the budget, you submit a Mittelabruf form on the programme's rhythm (often monthly or quarterly) declaring the funds you need for the coming period, and the Projektträger transfers them. The cardinal rule: you call down money for eligible costs that are actually being incurred, not to park cash in your account. Calling down more than you can spend in the allowed window can trigger interest claims or recovery.
Most multi-month grants require at least one interim report - the Zwischenbericht - and a final report at the end (the Schlussbericht or Verwendungsnachweis). The Zwischenbericht is where you show the Projektträger that the project is on track: what milestones you hit, where you deviated from the plan and why, how the money was spent against the budget, and whether the Verwertungsplan still holds. Reviewers reading interim reports are not looking for perfection - projects deviate, that is normal - they are looking for honesty and control. A report that quietly pretends everything went to plan when the milestones clearly slipped reads worse than one that names the slip and explains the recovery.
Practically, write the Zwischenbericht against the original plan section by section, so the reader can map your progress to what they funded. Keep the tone factual, lead with results, and attach the numbers. A good interim report takes a few days, not a few hours - budget for it the way you would budget for a release.
Public grants can be audited, sometimes years after the project ends. Every euro of Sachausgaben needs a receipt, every receipt needs to map to a budget line, and the whole trail needs to survive an auditor who was not there. The teams that suffer at audit time are the ones who threw receipts in a drawer and reconstructed the story at the end; the teams that breeze through are the ones who logged each cost against its budget line as it happened. Set up a simple structure on day one: a record per cost with date, amount, budget line, the milestone it served, and the receipt attached. The Drei-Angebote-Regel - keeping the competing quotes for items above the threshold - lives here too: keep the quotes, not just the winning invoice.
One record per euro, logged as it happens
The cheapest audit insurance is logging each cost against its budget line and milestone the day it is incurred, with the receipt attached. Reconstructing the trail at the end is the slow, error-prone way - and it is when teams discover a missing quote or an ineligible line.
Projects change, and most Bescheide allow reasonable deviation - but some changes require advance approval from the Projektträger, and making them without asking is where clawback risk concentrates. Significant budget reallocations, a change in the project scope, a co-founder leaving the team, a delay that pushes you past the funded period: these are the kinds of events you flag to your Projektträger contact proactively, in writing, before you act. The relationship works in your favour if you treat the Projektträger as a partner you keep informed; it works against you if they learn about a material change from your final report. When in doubt, ask first - a short email asking permission is always cheaper than a recovery proceeding.
FAQ
Free plan, no credit card. We host in Germany. You can export and delete everything self-serve.

Written by
Co-Founder + CEO
Julia is one of the Co-Founders. She handles design, product direction, and most of the support replies that arrive in the morning.
Read next
Building the EXIST Finanzplan: stipend, Sachkosten, Coaching, and the line items reviewers question
What EXIST actually pays, what it does not, and how to itemise Sachkosten.
Read
The Verwertungsplan: how to prove your grant turns into a real business
Wirtschaftliche, wissenschaftliche, and strategische Verwertung explained.
Read
De-minimis: the €300k cap that decides which grants you can actually stack
How to count, which programmes use it, and the planning trap.
Read