Forschungszulage: Apply Yourself or Hire a Consultant?

What you can do yourself, and what is genuinely hard

The Forschungszulage is deliberately not a competitive programme. There is a legal entitlement once the criteria are met, and nobody requires you to hire a consultant. The application runs in two stages: first the technical submission to the certification body (Bescheinigungsstelle Forschungszulage, BSFZ), free of charge via their portal, then the assessment through your tax return at the tax office.

A lot of that is perfectly doable in-house:

• Checking the basic requirements. Tax liability in Germany, legal form, and the question of whether your company counts as an "undertaking in difficulty" on the relevant reporting date. That last one is the point to clarify first, not last: if more than half of the subscribed capital has been consumed by accumulated losses at the end of the fiscal year, the funding does not apply. In young companies even a convertible loan can push the balance sheet in that direction, and otherwise you only find out at the very end of the process.
• Estimating the funding amount. Assessment basis times funding rate, 25% as standard and 35% for SMEs, capped by the annual ceiling.
• Operating the portal. The submission itself is craft, not magic.

What is hard is something else: the three decisions that come before the form. Which projects do you claim, how do you cut them, and which costs do you assign to them? Almost everything that determines the size of your funding happens before the filing, not during it.

The realistic effort: not the form, the groundwork

An honest caveat up front: there is no reliable person-day figure for a DIY application, and anyone who quotes you one is guessing. The effort depends almost entirely on how much you already have in place. What comes up in every case:

1. Identify and demarcate projects. What is internally called "product development" has to be translated into projects with a technical objective, cleanly separated by fiscal year.
2. Research the state of the art. The current one, not the one from three years ago. In AI topics, for instance, hallucination problems long counted as an eligible technical hurdle; by now established countermeasures are part of the state of the art, and the same argument no longer carries.
3. Formulate technical target values. Concrete metrics instead of market or user goals. This is the mistake first-time applicants make most often.
4. Derive personnel costs. Gross salaries plus employer contributions and levies, and the R&D share per person, not a flat rate for the department.
5. Build time records. Timesheets countersigned by the employees, and work packages on a timeline. If that is not already running, this is the part that genuinely hurts.
6. Answer follow-up questions. Queries from the certification body come with short deadlines, typically around two weeks. Across the projects we support, the median time to the first decision is roughly 64 days, and you do not get to choose which certification body reviews your application.
7. Keep the filing audit-proof. Tax audits do happen, and then it is about repayment claims.

The real price is in none of those points: this work can realistically only be done by someone who understands the technology. In practice it therefore lands with your developers or directly with the CTO, that is, with the resource whose time is the most expensive and who has the least appetite for writing applications.

Three places where DIY applications leave money behind

The most common disappointment with the Forschungszulage is not rejection. It is the approved application that ends up delivering a fraction of what would have been possible.

1. The "test application". Submitting one small, safe project to try out the process first sounds sensible and is the most expensive mistake in the whole procedure. At the BSFZ you can improve and resubmit. But once the tax office has issued the assessment for a fiscal year, you will practically not get any further costs recognised for that year. Whatever you did not claim in the first round is, as a rule, gone for that period.
2. Cost types nobody has on their radar. Own contributions by shareholders, pro-rata fixed assets, the overhead flat rate introduced in 2026, and the question of how you cut your projects are all design decisions with a direct effect on the assessment basis. Without experience you set these conservatively, and conservative here means too low.
3. Misclassified people. Whether someone counts as an internal employee or as contract research determines whether their costs enter the assessment basis at 100% or only in part. Across several people and several years, that single classification quickly adds up to a five- or six-figure difference. Especially for teams abroad or employer-of-record setups the legal position is not settled on every point, so a careful review pays off here.

Where DIY applications get rejected

Rejections are no exception with the Forschungszulage. According to a BMBF letter dated 24 June 2024, the project-level success rate at the BSFZ averages 74.55%, putting the rejection rate at roughly one quarter. In 2024 it was temporarily higher. The full figures, including breakdowns by industry and company size, are in our Forschungszulage statistics analysis.

The reasons repeat themselves:

• Market goals instead of technical goals. "Faster for the user" is not a target value. A measurable technical metric is.
• No recognisable step beyond the state of the art. If you do not properly establish what the state of the art is today, you cannot show where the technical uncertainty begins.
• Inflated, generic text. Engineers do the reviewing. If an application reads like a checklist of buzzwords, that works against you.
• Implausible R&D shares. A company where supposedly everyone spends 100% of their time on research, even though someone has to handle support and sales, stands out immediately.
• Activities that are not funded. Interface and UI work, connecting to standard APIs that are already provided, and pure regulatory compliance are generally out, even when a lot of effort goes into them. There are borderline cases, but you have to be able to justify them.
• Gaps in time tracking and documentation. At the tax office at the latest, it gets detailed. How to set this up cleanly is covered in our post on Forschungszulage documentation.

One point that rarely gets named: with a DIY application you have exactly one data point. You do not learn who reviewed it, you cannot call them, and you never see how the same situation was assessed elsewhere. Anyone who has seen many applications, queries and appeals writes the next one differently.

The decision matrix: five questions

It is not the funding amount that decides this, it is the structure of your case. Five questions are enough:

1. How many projects? A single, clearly outlined project is easy to present yourself. With five parallel development efforts, demarcating them from each other becomes the actual task.
2. How many funding years? Up to four years retroactively are possible. A current year with fresh data is something entirely different from four years for which time shares have to be reconstructed.
3. How obvious is the R&D character? A novel method with clear technical uncertainty largely carries itself. As soon as eligibility becomes a matter of interpretation, the wording decides the outcome.
4. Who writes it, and when? Is there someone technical who genuinely has the time, or does the application land on the "next week" pile and get thrown together just before the deadline? And: does the time tracking already exist?
5. What does a failed attempt cost you? Time is replaceable, a fiscal year assessed too low is not. Work through the scenario where the application goes through, but at half the amount.

As a rule of thumb: one project, one year, clear R&D character, free technical capacity, time tracking already running means you can realistically do it yourself. The more of these points tip, the more the trade-off shifts, and it shifts via the funding amount, not via the effort.

If you do it yourself: our four guides

We have written up the fundamentals in enough detail that you can actually work with them:

• Requirements: who is entitled and which three criteria a project has to meet, including a status check on tax liability, legal form and "undertaking in difficulty".
• Calculation: the formula built from assessment basis and funding rate, the cut-off dates, the ceilings and a worked example.
• Application process: the two-stage route from the BSFZ to the tax office, with deadlines, processing times and what you should prepare.
• The FZulG explained: the law itself, section by section with the original wording, for the cases where you really need to substantiate a demarcation.

If you get through with that, we are genuinely glad. The Forschungszulage is worth it for smaller projects too, and it is worth it regardless of who writes the application.

If not: what consulting takes over

The difference is not that someone else fills out the form. It lies in the three steps before that: identifying eligible projects, extracting the maximum costs that can be soundly justified, and drafting the application with enough technical depth to hold up under review. What you end up with is the list of projects per fiscal year, the written technical project descriptions, the complete cost breakdown, a time-tracking setup that also holds up in following years, the prepared figures for your tax advisor, and a filing structure that withstands a later tax audit. Your team invests under five hours across four calls for that.

For context: industry-wide, the BSFZ rejects around 25% of projects. Across the applications we support, the success rate is above 92%. That is not a promise for any individual case, it is the result of state of the art, technical target values and uncertainties being written the way the reviewers actually assess them.

Whether that pays off for you comes down to a plain calculation: more funding and lower risk against the cost of the support. Which models exist on the market and how to compare them is covered in What does Forschungszulage consulting cost?. And if you want to know what Forschungszulage consulting would concretely look like in your case, a free initial call is the fastest route to a clear answer.