Deadline 31 Dec 2026Secure 2022 →

Forschungszulage requirements: who is eligible?

Explain this article with AI

Does my company meet the requirements?

If your company meets these basic requirements, there is generally nothing standing in the way of funding.

RequirementDetails
Tax liability in GermanyFully or partially tax-liable
Not a company in difficultyNo UiS under EU state aid law, no insolvency, no outstanding EU recovery order
Legal formAll legal forms tax-liable in Germany are eligible
  • Corporations (GmbH, AG)
  • Partnerships (KG, OHG)
  • Sole traders
  • Freelancers
  • Agriculture and forestry businesses
  • Opting partnerships under § 1a KStG
EEA for contract researchThe contractor must be based in the EEA

Does my project meet the R&D criteria?

This is where it gets interesting — and where most applications fail. What is actually funded? Not just basic research. The vast majority of funded projects fall into experimental development: there's an unsolved technical problem and you systematically test a solution.

Research has three categories — and most development in companies falls under one of them§ 2 FZulG§ 2 FZulG: Begünstigt sind Vorhaben der Grundlagenforschung, industriellen Forschung und experimentellen Entwicklung, eigenbetrieblich, als Auftragsforschung oder in Kooperation. Nicht mehr begünstigt sind Tätigkeiten, deren primäres Ziel die Marktentwicklung ist oder die ein festgelegtes Produktionssystem zum reibungslosen Funktionieren bringen sollen.

  1. Basic research — New scientific knowledge without direct application
  2. Industrial research — Systematic research with a concrete application goal
  3. Experimental development — Using existing knowledge to develop new or improved products, processes, or software (← where most applications land)

The three decisive criteria

Your project must answer these three questions with yes:

  • Novelty: Does your project aim for new knowledge or significantly improved products / processes — measured against the current state of the art?Prüfleitfaden Ch. 1.1.1Prüfleitfaden Ch. 1.1.1: „Neuartig ist ein FuE-Vorhaben dann, wenn es auf den Erwerb neuen Wissens abzielt. Dieses Wissen muss über den aktuellen Stand der Technik hinausgehen.“
  • Uncertainty (Risk): Are there technical risks or uncertainties? Could your approach fail? Purely economic risks do not count.Prüfleitfaden Ch. 1.1.2Prüfleitfaden Ch. 1.1.2: „Die BSFZ bezieht sich bei der Bewertung des Kriteriums Unwägbarkeit / Risiko ausschließlich auf wissenschaftliche und technische Aspekte. Wirtschaftliche Risiken und Unwägbarkeiten werden zur Beurteilung, ob ein FuE-Vorhaben im Sinne des FZulG vorliegt, nicht herangezogen.“
  • Systematic approach: Is the project carried out in a planned and documented manner?Prüfleitfaden Ch. 1.1.3Prüfleitfaden Ch. 1.1.3: „Planmäßig ist ein FuE-Vorhaben, wenn es einer systematischen Vorgehensweise folgt, deren Ziele, Methodik und zeitlicher Ablauf nachvollziehbar dokumentiert sind.“

Behind these three review criteria is the OECD's Frascati Manual. It describes R&D with five features: novel, creative, uncertain, systematic, and transferable and/or reproducible. The BSFZ condenses them into its three criteria, with “creative” absorbed into novelty and uncertainty. For a deeper dive, there is one article each on novelty, creative work, uncertainty and the systematic approach.

The Red Thread: How to argue R&D

Technical benchmarks instead of economic goals – that's what convinces the reviewers.

Illustrative example
STATE OF THE ART
81% accuracy
Current measurable technical benchmark
WP 1 · Method
New Method / Algorithm
WP 2 · Prototype
Prototype & Validation
WP 3 · Integration
Integration & Testing
TECHNICAL TARGET
92% accuracy
Technical target – not economic!

⚠Common mistake: market goals instead of technical goals (e.g. "50% more revenue")

The BSFZ reviewers think in exactly this framework: Where are you today? → What are you doing? → Where do you want to go?Prüfleitfaden Ch. 1.1.1Prüfleitfaden Ch. 1.1.1: „Jeder Forschungs- und Entwicklungsprozess besteht aus drei wesentlichen Teilen: Start/Ausgangslage, Weg zur Umsetzung, Ziel: Produkt, Verfahren oder Dienstleistung.“

Each of these three points must be described in technical, concrete terms. Economic targets like "50% more revenue" or "better user experience" will not convince the certification body.

The most common mistake: the state of the art is described vaguely or in market terms

The BSFZ wants concrete, technical benchmarks — and the reviewers immediately recognise whether someone knows their field. Many companies conduct genuine experimental development without framing it that way — leaving hundreds of thousands or even millions in funding on the table.

Good technical differentiation
  • AI / Machine Learning: "Existing models achieve 82% classification accuracy on dataset X. Our approach combines method A with B to exceed 93% — at half the inference time."
  • Software: "Existing systems process 10 requests/second. Our goal is 50/second through a new caching approach based on X."
  • Mechanical engineering: "Current manufacturing tolerances are ±0.1mm. Our process aims to achieve ±0.02mm through method Y."
  • Medical technology: "Standard sensors measure at resolution Z. We are developing a new sensor approach targeting resolution W."
Common mistakes
  • "We want to improve the user experience"→ no technical benchmark
  • "Our goal is 30% more revenue"→ economic, not technical
  • "We are building the best solution on the market"→ market positioning, not technology

Checklist: R&D or not?

Research and Development
  • New developments or significant improvements to products / processes
  • New services enabled by digitalisation
  • Development or significant improvement of software components
  • Intelligent and self-learning design of industrial and manufacturing processes
  • New, more efficient algorithms based on new technologies
Not Research and Development
  • Use of already known products / processes
  • Recurring and routine changes
  • Configuration of existing software / hardwarePrüfleitfaden Ch. 2.4.1 ICTPrüfleitfaden Ch. 2.4.1 ICT: „Reine Konfiguration, Parametrisierung, Anpassung oder Portierung bestehender Software- oder Hardware-Komponenten erfüllt grundsätzlich nicht die Kriterien eines FuE-Vorhabens.“
  • Porting of software (e.g. standalone to cloud)Prüfleitfaden Ch. 2.4.1 ICTPrüfleitfaden Ch. 2.4.1 ICT: „Reine Konfiguration, Parametrisierung, Anpassung oder Portierung bestehender Software- oder Hardware-Komponenten erfüllt grundsätzlich nicht die Kriterien eines FuE-Vorhabens.“
  • Template-based software solutions without technical risksPrüfleitfaden Ch. 2.4.1 ICTPrüfleitfaden Ch. 2.4.1 ICT: „Reine Konfiguration, Parametrisierung, Anpassung oder Portierung bestehender Software- oder Hardware-Komponenten erfüllt grundsätzlich nicht die Kriterien eines FuE-Vorhabens.“
  • Routine software developmentPrüfleitfaden Ch. 2.4.1 ICTPrüfleitfaden Ch. 2.4.1 ICT: „Routinetätigkeiten der Softwareentwicklung wie Anforderungsanalyse, Testing, Debugging oder Bugfixing erfüllen nicht die Kriterien.“→ requirements analysis, testing, debugging
  • Pure administrative, certification, or approval activities
  • Feasibility studiesPrüfleitfaden Ch. 2.3.9Prüfleitfaden Ch. 2.3.9: „Durchführbarkeitsstudien können der industriellen Forschung oder experimentellen Entwicklung zugeordnet werden, sofern sie selbst Forschungscharakter aufweisen. Reine Vorstudien ohne FuE-Charakter sind nicht förderfähig.“
  • Work to achieve market readiness

Prototype, pilot line, trial production: where R&D ends

For the Forschungszulage, a prototype is not a first sample for sales or a pitch but a functional interim state that answers technical questions. Whether it is physical (component, machine) or digital (software demonstrator, algorithm, AI model) hardly matters. Development is typically eligible when

  • genuine technical uncertainties exist, for example in function, integration, scaling or performance,
  • you proceed systematically: plan, build, test, refine,
  • the prototype serves to gain knowledge, for example through tests under realistic conditions.

The line runs where knowledge gain ends and market or operational logic begins. A pilot line still counts as long as it mainly delivers technical data and experience. Trial production that already prepares the series launch usually does not. Also typically not eligible:

  • design studies and models without a technical function,
  • pre-series, series development and product adaptations without new technical findings,
  • marketing and sales, even if they belong to the project,
  • pure project steering (status, budget, deadlines) without a technical share.

"Part of the project" does not automatically mean "eligible". So set the project end at the first functional prototype or the completion of technical testing.

What is funded by the Forschungszulage?

  • Wage costs for employees in R&D projects
  • Own work by sole traders / co-entrepreneurs
  • Contract research (70% of expenditures)
  • Depreciation on movable fixed assets related to the project

Find the exact calculation and funding amounts under Calculation.

Application deadline

Costs for R&D activities can be claimed within a 4-year period. The decisive factor is the date the application is received by the BSFZ.

The Forschungszulage is particularly attractive because you can apply retroactively. Unlike European funding programmes where you plan future projects and then report extensively, here you claim costs that have already been incurred. No planning stress, no reporting problems.

More on the application process →

Proving eligibility

The Forschungszulage is granted through a two-step process:

  1. Content review (BSFZ)— Assesses whether your project meets the R&D criteria. Prüfleitfaden Ch. 1.2Prüfleitfaden Ch. 1.2: „Bezogen auf die Angaben zum finanziellen und personellen Rahmen wird durch die BSFZ eine Plausibilitätsprüfung „dem Grunde nach“ durchgeführt.“ More on the application process →
  2. Financial review (tax office) — Reviews the actual expenditures (wage costs, timesheets, employment contracts). More on calculation →

The two stages check different things, but they interlock: whatever is not cleanly delimited in the BSFZ certificate can hardly be rescued on the numbers side at the tax office. That seam is exactly where Forschungszulage consulting comes in: it delimits the project cleanly in the BSFZ application and supplies the matching cost breakdown and a pre-filled ELSTER form for your tax advisor to review and file.

FAQs on eligibility

The most important questions answered briefly. If your case isn't covered here, just write to us.
The following criteria must be met:
  • Tax liability: The company must be fully or partially tax-liable in Germany.
  • Not a company in difficulty under EU state aid law.
  • No pure consultancy: The funded project must involve its own R&D activities.
  • No insolvency at the time of application.
  • No outstanding recovery order: There must be no outstanding recovery order for EU state aid.
No. The Forschungszulage funds not only basic research, but explicitly also experimental development. In fact, the majority of all applications fall into this category. Most start-ups and SMEs carry out this kind of development every day — often without knowing they can receive funding for it.
All companies tax-liable in Germany, regardless of size, legal form, or industry. Start-ups and agricultural or forestry businesses are also eligible. Only tax-exempt institutions are excluded.
Yes. Even companies that pay little or no tax receive the Forschungszulage. If the allowance exceeds the assessed tax, the surplus is paid out as a tax refund ("cash"). This is particularly attractive for start-ups.
No. The Forschungszulage is open to companies of all sizes — from sole traders to large corporations. SMEs benefit from an increased funding rate (35% instead of 25%) since the Growth Opportunities Act. See Calculation.
No. Since research by definition involves risks and uncertainty, it is the effort that is funded, not the outcome. Even abandoned or failed projects are eligible, as long as they were carried out systematically.
Yes. Software development is a classic example of experimental development, provided it overcomes technical hurdles and does not merely configure existing components. According to the BSFZ review guideline, routine development activities (requirements analysis, testing, debugging) are not eligible — there must be genuine technical uncertainty.
The Forschungszulage funds R&D projects in three categories: basic research, industrial research, and experimental development. Specifically, the following expenditures are eligible: wage costs for employees in R&D projects, own work by sole traders, contract research (70% of costs), and depreciation on project-related assets. The funding rate is 25% (SMEs: 35%) of eligible expenditures.

Unsure whether your project is eligible?

Write us briefly what you're working on — we'll check for free whether the Forschungszulage applies to you.