Forschungszulage Consulting: The Process in 4 Calls

The process as a timeline: from first conversation to the tax office assessment

The application runs in two stages: first the Bescheinigungsstelle Forschungszulage (BSFZ) assesses whether your project qualifies as research and development under the law. Only then can the tax office assess the allowance. Between the stages sit waiting times you cannot influence; before them sits the work that decides success and funding amount.

1. Free assessment call (approx. 30 min): We give you an honest read on whether an application is worthwhile for you and which retroactive years are in scope.
2. Calls 1 to 4 (under 5 hours in total): Documents, figures, projects, review. Details below.
3. Submission via the BSFZ portal: Applications are filed exclusively through the BSFZ's online portal. There is no paper route.
4. BSFZ review (roughly two to three months): The BSFZ assigns your application to one of the assessing institutes. You cannot influence which one, and processing times vary by institute and workload.
5. The certificate: It covers the entire project including its full duration and can be used across several fiscal years.
6. Assessment at the tax office: Together with you, we determine the actual hours and costs per fiscal year and prepare the assessment request as a pre-filled ELSTER form. Your tax advisor reviews it and files it via ELSTER, and the tax office assesses the allowance. This is where the detailed review happens.
7. Offset or payout: The allowance is usually offset against the assessed income or corporate tax. If it exceeds that tax, the surplus is refunded. The details are in our article on the Forschungszulage payout.

Across the whole path from preparation to assessment, 6 to 9 months is a realistic range. This is why applying for the BSFZ certificate early pays off: without it, the tax office cannot assess anything at all.

Before you start: what you need, and what you explicitly do not

The most common reason companies keep postponing the application is the assumption that they first have to spend weeks collecting documents. We have deliberately set it up the other way round.

What you actually need:

• Someone who can explain your projects technically. Usually the CTO or a lead developer, and only for a single call, not for a multi-week marathon.
• Someone who connects us to your tax advisor, typically from finance or the management team.
• The willingness to review the draft once before submission.

What you explicitly do not need:

• No prepared document list. Which documents matter depends on the founding date, legal form, contractors, and affiliated companies. The checklist is built in call 1 and is company-specific.
• No finished project descriptions. We write them; you correct them.
• No finished timesheets. For the BSFZ application, traceable estimates are enough. For the assessment request, we reconstruct the actual hours together with you from tickets, commits, and calendars, using a documented method your tax advisor can follow.
• No homework between calls.

Calls 1 to 4 in detail

Why we write the text and you do not: your application is not read by administrative clerks but by technical assessors. They want to know the current state of the art, what exactly is technically new about your approach, and which concrete technical risk you faced. Product marketing language convinces nobody there. More on our Forschungszulage consulting page.

Responsibility matrix: who supplies what

The most common friction in the process is not technical, it sits at the interface with the tax advisor. So here is who owns which part, explicitly.

● accountable · ○ contributes input

The tax step deliberately stays with your tax advisor: as an external service provider we are not allowed to file the application with the tax office. From us he receives the complete cost breakdown per project and year, prepared so that he can review and file it. Each folder in the document package carries a cover sheet describing the method applied, so he can trace how every figure came about.

After submission: follow-up questions, revisions, decisions

Once submitted, the application is done from your side, but not from ours. What can happen next:

A request for additional information from the BSFZ. If the information on the three criteria is incomplete or evidently flawed, the BSFZ asks in writing for additions within a set deadline. As a rule there is one opportunity to respond, so the answer needs to be thorough. We handle that communication.

Revise and resubmit. A negative BSFZ decision is not the end of the road. A project can be re-scoped, argued more sharply in technical terms, and resubmitted. If something about the project changes after certification, that goes through an amendment request, which is usually processed considerably faster than a first application.

The certificate. It is binding on the tax office and covers the entire project including its duration. One certificate can span several fiscal years; your tax advisor still files the assessment request per fiscal year.

The assessment at the tax office. This is where the detailed review happens for the first time: gross salaries, timesheets, employment contracts, invoices for contract research, and the correct calculation of the assessment base. The BSFZ only checked costs for plausibility; the tax office looks closely. Worth knowing: only the tax office's decisions are final. An application is not set in stone once it reaches the BSFZ, whereas a tax office decision is.

How long it takes

The honest answer: the bulk of the waiting time sits neither with you nor with us, but with the authorities.

• Your preparation with us: four calls, under five hours of effort for your team, usually spread over a few weeks in calendar terms, because your tax advisor has to deliver between call 1 and call 2.
• BSFZ review: plan for two to three months rather than exactly two. Processing time varies by assessing institute and workload; amendment requests are much faster.
• Assessment and payout by the tax office: depends on the tax assessment, workload, and any follow-up questions.
• In total: typically 6 to 9 months from preparation to actual effect, meaning offset or payout. Follow-up questions or a complex tax assessment can stretch that further.

Once the process has been set up cleanly, the following years are considerably faster: project documentation, time tracking, and responsibilities are already in place.

What can go wrong, and how we handle it

And if you are already working with a consultant but unhappy: switching is possible even mid-process. What to watch out for is covered in our article on switching Forschungszulage consultants.

Which projects is this worth it for?

Not just lab research. Frequently eligible where genuine technical uncertainty and a methodical approach are present:

• Software and AI: new model and data pipelines, robust real-time processes, novel system architectures
• Production and processes: new methods, material or quality innovations
• Hardware and IoT: new prototypes, measurement and control methods
• B2B platforms with genuine technical uncertainty: scalability, latency, security, interoperability

What matters is not the buzzword, but: what was technically unclear, and how did you proceed systematically to resolve it? You will find concrete examples in the overview of requirements, and a first estimate of the amount in the calculator.

From 01.01.2026, the Forschungszulage becomes even more attractive, among other things through a higher assessment base and additional flat rates. If you are investing in development anyway, planning now pays off, and if you have already been working in an innovation-driven way in recent years: check retroactive eligibility, up to four years are possible.

Official contact point for the certificate: bescheinigung-forschungszulage.de