We explain the full step-by-step process (BSFZ → tax office) in detail here: Application Process Guide. In this post, we deliberately focus on the retroactive topic, strategy, and typical practical questions.
"Retroactively" means: you can still claim R&D (FuE) expenses from years that have already been completed—up to four years retroactively. This is exactly what makes the Forschungszulage (public funding) so attractive for many companies that:
The key idea: retroactivity is not a "last resort," but a deliberately built-in advantage—especially for teams that have already been doing serious development work in the past.
Any company taxable in Germany (including sole proprietors) that carried out eligible R&D (FuE) projects in the relevant period. Profit or paying taxes in the expense year is not a requirement—if the allowance exceeds the assessed tax, it is paid out.
Eligible are projects in basic research, industrial research, or (most commonly) experimental development. Projects must be describable in technical terms: state of the art, measurable objective, technical uncertainty, and a systematic approach. A common mistake: wording that is too "business-heavy." Personnel costs are usually the biggest lever; R&D shares must be plausible. BSFZ initially only checks plausibility; the detailed review happens at the tax office.
Important: The 4-year period is running—if you haven't used it for several years, you should now systematically identify the relevant projects before a year expires permanently.
You can find more information in our guide to the requirements: Requirements for the Forschungszulage
Many people only know grant programs like this: apply upfront → report later → explain deviations. Exactly this "plan vs. reality" friction costs time, nerves, and in the worst case, funding money.
The Forschungszulage works differently—and retroactively, this advantage is strongest:
From an expert perspective, this is why applying for the Forschungszulage retroactively is often more efficient than applying "on an ongoing basis": less estimating, less rework, less need for amendments.
Instead of "as early as possible" (sounds good, but is too generic), the better practical question is:
Typical first-call situation:
Rule of thumb from practice:
Yes, the Forschungszulage (public funding) can be applied for retroactively—but: for older years, you need the technical certificate in time so the tax part can run cleanly. Especially when projects are far in the past, reworking documentation (tickets, commits, experiments, architecture decisions) does not get easier.
Practical recommendation:
This way you combine:
You'll find the full process in the Application Process Guide on zeitmaker.com. For the retroactive topic, this classification is enough:
When you apply retroactively, you typically want to process multiple years "in one go" cleanly. For that, the sequence must be right:
Because: Once the application is filed with the tax office, that is not the moment for "oh, we'll just correct it quickly later." Plan so that what you submit to the tax office is truly "final."
A common misconception: "We must hit the costs exactly in the BSFZ application."
In practice:
A proven practical strategy:
Here is a first cost estimate guide: Calculation of the Forschungszulage
Applying retroactively reduces deviations—but doesn't eliminate them, e.g., if you cover multiple years/project runtimes in the BSFZ application.
If it later turns out that:
… then an amendment application with BSFZ may be required before the tax office can assess cleanly.
Rule to remember: First keep BSFZ consistent, then submit the tax office application "fixed."
Yes. That is exactly what retroactivity is for: you can claim the Forschungszulage retroactively—typically up to 4 years retroactively, if the requirements are met.
In principle up to four years (the decisive factor is the deadlines per calendar year). It's important to realistically plan for processing times and the required BSFZ certificate—don't rely on "the very last day."
Often best: cover 1–2 years retroactively plus the current year, then catch up annually. This uses actual data without burdening you with unnecessary documentation work for very old projects.
The core process is the same (BSFZ → tax office). The difference is strategic: retroactively, you benefit more strongly from actual data and avoid typical plan deviations.
Not retroactivity itself—but an overly vague technical description (state of the art/goals/risks) or unclean consistency between the BSFZ certificate and the later tax office application.
Plan as if the answer is no: After submission it is practically "fixed." If something essential about the project must change, the correct path is typically: BSFZ first (if needed, an amendment application), then the tax office.
Drop us a line about what's on your mind — we'll get back to you personally and without obligation.
Forschungszulage documentation: timesheets, payroll evidence, contract research & GoBD-compliant filing – how to document audit-proof for the tax office.
The Forschungszulage offers 8 key benefits: statutory entitlement, retroactive claims, open to all sectors, usable without profit, digital process and broad cost coverage.
Check in 4 steps if your project qualifies for the Forschungszulage: R&D classification, novelty, technical risk and systematic approach. Quick self-test.
How to handle the Forschungszulage in your corporate tax return: offset vs. payout, BSFZ certificate, Appendix WA/12 and accounting explained.
