Forschungszulage Rejected? How to File an Objection with the BSFZ (2026)

The short answer: one month, and filing informally is enough

You can file an objection against a rejection notice from the Bescheinigungsstelle Forschungszulage (BSFZ). The rules are:

• Deadline: one month from notification of the notice (§70 VwGO).
• Without a valid instruction on legal remedies: one year (§58 VwGO).
• The addressee is the BSFZ, the authority that issued the notice.
• The procedure is free of charge.

The most important point in practice: you can file the objection informally to meet the deadline and submit the technical reasoning afterwards. One sentence with the file reference stating that you are filing an objection is enough to preserve the deadline. The substantive work, meaning state of the art, technical uncertainties and evidence, follows after that.

First check: request for information or an actual rejection?

Before you react, read the feedback carefully, because the deadlines differ significantly:

• Request for additional information: The BSFZ requires additional information or documents within a deadline, frequently reported as only 14 days. This is often a good sign: the procedure is still running, you simply need to respond quickly and precisely. There is no objection here, because there is no notice yet.
• Rejection: The BSFZ concludes that the project as submitted does not meet the requirements. Only here does the formal objection apply, with its one-month deadline.

Filing an objection with the BSFZ: deadline, form, costs

1. Deadline. One month from notification of the notice (§70 VwGO). If a valid instruction on legal remedies is missing or incorrect, the deadline is one year (§58 VwGO).
2. Form. In writing, or as specified by the instruction on legal remedies in your notice. That instruction is the binding text: it names the addressee, the form and the deadline for your specific case.
3. Addressee. The BSFZ as the issuing authority, not the tax office and not the ministry.
4. Reasoning. Does not have to be submitted at the same time. Filing to meet the deadline and submitting the reasoning later is the usual route when the technical work takes more time than the deadline allows.
5. Costs. The objection procedure is free of charge. Effort only arises internally or through external support.
6. Process. The BSFZ reviews your case again in the remedial procedure and can uphold the objection in full or in part. There is no statutory deadline for this review, so do not build a fixed duration into your liquidity planning.
7. Missed deadline. Once the month has passed, the notice becomes final and binding and can no longer be challenged in the objection procedure. For the funding itself this is not the end: you can resubmit a revised project, and further applications remain possible.

How is an objection to the BSFZ structured?

An objection is not a form, it is a technical document. This structure has proven effective:

1. Reference. State the file reference, the date of the notice and the affected projects unambiguously.
2. Statement of objection. One clear sentence stating that you are filing an objection against the notice dated DD.MM.YYYY. If the reasoning will follow, announce it here.
3. Brief description of the project. Two or three sentences: what it is about technically, over which period, with which goal.
4. Address each ground for rejection individually. Always use the same pattern per point: take up the statement from the notice, clarify it technically, provide a new piece of evidence. Do not repeat the original application, answer specifically what was criticised.
5. Evidence for the three criteria. Address novelty, technical uncertainty and systematic approach explicitly, even if the notice names only one of them.
6. Request. Annulment of the notice and a new decision, stated explicitly.
7. Attachments. Work plan, experiment and test protocols, state-of-the-art comparison, and where relevant architecture or design decisions with dates.
8. Signature. By an authorised representative.

Common grounds for rejection and how to refute them

In practice, applications fail on presentation and structure, not on the degree of innovation itself. These are the typical patterns:

Novelty not distinguished from the state of the art

What the BSFZ criticises: The project reads as an application of known methods, because the submission does not say what already exists and where the existing solutions fall short.

How to refute it in the objection: Name the state of the art concretely, with methods, products or publications, and demonstrate the gap against it. Only the comparison makes novelty verifiable.

Technical uncertainty not apparent

What the BSFZ criticises: The application describes an implementation plan, but no open technical problem. If the outcome is certain from the start, the criterion is not met.

How to refute it in the objection: Describe how the chosen approach could fail and make the hurdle measurable: target values, tolerances, latencies, yields. Discarded approaches and their measurement results are the strongest evidence here.

Marketing language instead of technical depth

What the BSFZ criticises: Phrases such as "innovative platform" or "AI-powered" without technical substance. The reviewers are engineers and computer scientists and read such texts as assertions.

How to refute it in the objection: Replace adjectives with figures, methods and architecture decisions. One sentence with a concrete target value carries more weight than a paragraph of product description.

Commercial instead of technical risk

What the BSFZ criticises: The uncertainty cited is market acceptance, competition or financing. That is entrepreneurial risk and does not meet the criterion.

How to refute it in the objection: Frame the risk technically. Not "unclear whether customers will adopt it", but "unclear whether the method reaches the required accuracy with this data situation".

Systematic approach not substantiated

What the BSFZ criticises: Work packages, schedule and responsibilities are missing, contradictory, or do not match the claimed effort.

How to refute it in the objection: Submit a consistent work plan: work packages with goals, time frame, owners and milestones, reconciled with the person-months in the application.

Costs not clearly allocable

What the BSFZ criticises: Expenditures cannot be cleanly attributed to the project, time shares look like flat estimates.

How to refute it in the objection: Allocate people and time shares to the work packages and back them with your ongoing documentation. That allocation also pays off later with the tax office.

How common are rejections?

Rejections for the Forschungszulage are not an exception. According to a BMBF letter dated 24.06.2024, the BSFZ rejection rates (per project) were 24% (2020), 21.08% (2021), 26.22% (2022), and 25.46% (2023). For 2024, a record high of 28.89% (as of end of May) is cited; across all years the average is 25.45%. You will find more figures in our analysis of success rates.

This rate is not a stop sign for innovation. Above all it shows how decisive clear technical argumentation, clean structure and complete evidence are.

What the BSFZ actually contests: findings from our application practice

With the applications we support, queries and rejections are rare: the success rate is 95 % compared with around 75% across the industry. But when the BSFZ does come back, a very clear pattern emerges. Broken down by the criterion contested, the queries are distributed as follows:

One query often contests several criteria at once, which is why the shares add up to more than 100%.

Three conclusions follow from this:

1. Novelty and technical risk rest on the same argument. Naming the state of the art, making the technical hurdle measurable and describing how the approach could fail answers both questions in one go.
2. Market arguments answer none of the criteria. "More revenue", "better user experience" or "faster rollout" belong in the business plan, not in the project description.
3. The cost figures themselves are almost never contested. The bottleneck is the technical presentation, not the calculation.

On length: a project description of around two A4 pages is usually enough. Depth beats length. What matters is the thread running from state of the art through the technical goal to the risk of failure.

Objection or new application: which makes sense when?

An objection is worthwhile if:

• the notice criticises a specific point that you can clearly refute technically,
• information was missing from the application that already exists (protocols, measurement series, work plans),
• there is a misunderstanding, for example because a technical term was read differently than intended,
• only part of the projects was rejected and that part accounts for a relevant amount.

A new application is often better if:

• the structure fundamentally does not hold, for example because projects are scoped too broadly or too narrowly,
• the project has to be re-scoped substantively to meet the criteria cleanly,
• the deadline has already passed and the notice is final and binding,
• another financial year is coming up that you intend to apply for anyway.

Partial rejection and partial objection. The BSFZ reviews project by project and can reject individual projects in one notice while certifying others. In that case you direct the objection specifically at the rejected parts only. The certified projects remain unaffected and continue as normal in the procedure with the tax office, so nothing gets blocked.

If the objection is also unsuccessful. Legal action against an objection decision is possible, again with a one-month deadline. That is a trade-off: procedural costs and professional support versus the expected funding amount. In many cases the pragmatic route is the revised new application, because it produces a result faster and rebuilds the argument from the ground up. How the application runs in detail, from the BSFZ through to the tax office, is covered in the application guide.

When the tax office, not the BSFZ, is the obstacle

The Forschungszulage follows a two-stage process: first the BSFZ reviews the substantive criteria, then the tax office determines the eligible costs and decides on payout or crediting. The official entry point for the BSFZ is bescheinigung-forschungszulage.de.

Even with a positive certificate, reductions can occur at the second stage if costs are not cleanly documented or are incorrectly allocated. Especially for retrospective applications, complete and traceable cost and time documentation is decisive. Unlike the BSFZ procedure, where you can improve and resubmit, the decisions of the tax office are the final ones.

Why the effort pays off: the Forschungszulage from 2026

An objection costs time, but the amount behind it is rarely small. Since 1 January 2026:

• The assessment base is up to 12 million euros per year (previously 10 million euros).
• SMEs receive 35% of eligible expenses, large companies 25%.
• That means up to 4.2 million euros of Forschungszulage per year for SMEs.
• Applications remain possible up to 4 years retroactively, subject to the deadlines per calendar year.

For everything else that changed at the turn of the year, see our overview of the changes to the Forschungszulage in 2026.

Your next steps after a rejection

A rejection ties up internal resources and delays liquidity. The lever is almost always in presenting the project in a reviewable way: technically concrete, structured, and aligned with the three criteria. That is exactly what we work on at zeitmaker.com: we look at which technical points the BSFZ objected to and sharpen the reasoning, for the objection with the BSFZ or for the new application.

The process stays lean: 4 calls, under 5 hours of effort for your team. We run the interviews, write the technical descriptions and file the BSFZ application, you review. We bill 100% success-based, payable only after the tax office has paid out. If the rejection happened with another consultancy, switching your Forschungszulage consultants shows how to hand over documents, deadlines and ongoing proceedings cleanly.