The SIFIDE season is, every year, treated primarily as a tax-related exercise.
The conversation typically revolves around deadlines, percentages, eligibility, and tax liabilities. The focus is on corporate income tax (CIT) impact and submission timelines. But this view is limiting. SIFIDE is not simply a tax deduction mechanism. Above all, it is a formal system for recognizing investment in knowledge. And this is precisely where the real challenge begins.
Ter I&D não chega. É preciso demonstrá-la.
SIFIDE does not assess intentions, talent, or apparent complexity. It assesses whether there was, in fact, a need to technically develop and validate a solution that would not have been obvious to a skilled professional in the field.
It is not enough for a project to have been difficult or demanding. The key question is different: was it necessary to experiment, test, and iterate in order to reach the solution?
In practice, many companies do exactly that. They experiment, test hypotheses, refine solutions, and face real technical uncertainty.
SIFIDE • 5min read
They invest senior-level time in solving problems that have no clear answers in manuals or standards. By definition, this is the creation of new knowledge.
The problem arises later.
When the time comes to formalize that activity, what typically exists is fragmented: implicit technical decisions, successive project iterations, and critical hours that were never framed within a clear methodological approach.
The challenge is not the absence of R&D, but the absence of structure to demonstrate it.
And this is where the critical issue lies. The gap between doing and proving continues to be underestimated. Perhaps that is why SIFIDE applications are rejected less due to a lack of R&D activity and more due to a lack of demonstrated technical consistency. It is not about the absence of technical work, but the inability to structure and clearly explain it. And it is important to emphasize: in this context, narrative is not marketing or embellishment. It is rigor. It is the ability to clearly articulate the initial uncertainty, the paths explored, what failed, what was adjusted, and what knowledge was ultimately retained within the company.
Because, in the context of SIFIDE, R&D must also be written down—or it simply goes unrecognized.
There is also a recurring misconception that weakens the discussion: viewing SIFIDE as a marginal benefit. It is not. It is a structural instrument for recovering investment in R&D, with a direct impact on corporate income tax and the possibility of being carried forward when there is insufficient tax liability. It is not an accounting detail. It is a meaningful fiscal policy tool aimed at fostering the value of knowledge.
But perhaps its most compelling impact is not financial—it is organizational.
Preparing an application forces companies to pause and ask questions they rarely address in a structured way: where did real technical uncertainty exist?
What new knowledge was actually generated? Which part of the effort was truly experimental rather than mere execution? Where was the most qualified time concentrated?
That exercise has value in itself. It forces companies to distinguish routine work from development.
It requires recognizing that not everything complex qualifies as R&D—and that, at times, what seems “routine” is in fact experimental development. That is why “More R&D, Less CIT” should not be read as a tax slogan, but as a logical outcome. Companies that better structure their knowledge are better positioned to recover the investment they make.
And those that recover more reinvest more consistently—in people, time, and technical capabilities.
Ultimately, the SIFIDE cycle becomes a test of maturity—not only of R&D itself, but of how a company understands, organizes, and values its own knowledge.
Innovation matters. But in a regulated environment, the ability to clearly demonstrate where R&D activity took place is what truly makes the difference.
Written by:
Catarina Costa | Associate