The 2027 R&D deduction proposals have not been decided. Government formation is ongoing, and on 12 November the outgoing government presented a caretaker budget without new reforms. We monitor developments continuously. Read the current status · Create a free account

R&D deduction examples: software, manufacturing and life science

Written and reviewed by Nordic Search · Last reviewed: · How we work with content →

Examples can make the conditions easier to understand, but they cannot decide whether your project qualifies. All situations below are hypothetical and are not Nordic Search customer cases or decisions by Skatteverket. An industry, a patent or an ambitious product roadmap is not enough. You need to explain the research or development under the statutory definition and connect it to the actual work of each employee. Our guide to what counts as R&D explains that definition, while the complete guide shows how it connects to the deduction. Use these examples as questions to ask about your own evidence, not as descriptions to copy and treat as an approved assessment.

Software: distinguish investigation from implementation

Imagine a company investigating a new method for processing data under a technical constraint. The team describes published research results, explains why those results are decisive for the intended development and runs structured experiments to examine whether the method works. That account gives a reviewer something concrete to assess, but it does not guarantee eligibility. The company still needs to show systematic, qualified work for a commercial purpose. Compare this with implementing a standard interface, migrating to a familiar cloud service or correcting ordinary defects. Those tasks do not establish qualifying development simply because engineers perform them. Separate the investigative work from deployment, support and routine maintenance. Record what was tested and what was learned, including approaches that failed, rather than describing the entire software release as R&D.

Manufacturing: a process improvement needs a research connection

Consider a manufacturer trying to substantially improve a production process using relevant research results about materials or process behaviour. A useful description identifies the existing limitation, the research being used, the experimental method and the intended improvement. Test records can show the relationship between a hypothesis, a trial and the resulting change. Contrast that with purchasing a standard machine, adjusting known production settings or carrying out routine quality assurance. Investment and improvement are not by themselves proof of development under the legislation. Production staff may work on both experiments and ordinary output during the same month, so time needs to be separated. A project-wide budget cannot show which person performed the eligible activity. Failed trials can document the work, but commercial risk or a difficult schedule alone does not establish research.

Life science: a research label does not include every activity

Imagine a life science business carrying out a planned investigation to produce new knowledge with a commercial purpose. Describe the question, method, observations and conclusions, and identify the employees working directly on the investigation. For a development project, explain the research results used and why they are decisive for a new or substantially improved product or process. The sector is not a blanket exemption from the legal conditions. Administration, management, marketing and routine quality assurance do not automatically qualify because they are necessary for the product. Nor does participation in a regulated process by itself establish eligibility. Distinguish the actual research activity from surrounding compliance and support tasks. If the boundary is uncertain, consult Skatteverket’s guidance about the specific activity instead of relying on the project’s scientific name or internal department label.

Calculation example: three developers with SEK 50,000 monthly salary

Assume three employed developers each receive SEK 50,000 in contribution-liable monthly remuneration. The total base is SEK 150,000. If every person and the work meet all conditions, and no contribution floor, other reduction or cap restricts the amount, the current 20 per cent deduction is SEK 30,000 for that month. Twelve identical eligible months would produce SEK 360,000. This is a calculation illustration, not a prediction that the people qualify for a full year. It assumes that the employee and contribution conditions allow the full amount. The total deduction is capped at SEK 3,000,000 per employer and calendar month, shared within a group, and cannot reduce contributions below the applicable old-age pension contribution. Check real monthly payroll conditions before using an estimate in an employer declaration.

The same project can produce different monthly outcomes

A qualifying project does not give a fixed entitlement for everyone assigned to it. The main time rule requires at least 50 per cent and at least 15 hours of actual working time per person and calendar month. One employee may meet the conditions while another spends too much of the month on excluded support duties. A person who meets them during one month may have different duties in the next. Keep actual working time, direct R&D hours and relevant remuneration connected in your records. Do not calculate eligibility from a planned team allocation alone. Our employer declaration guide describes how the monthly review becomes a reporting base and a deduction. The limited continuation exception in the law requires a separate assessment and is not permission to assume that every project month qualifies.

Turn an example into your own evidence, not a copied claim

Write down what actually happened in your project: the starting point, research connection, activities, method, results and people involved. Explain which parts differ from routine work and which tasks have been excluded. Link each monthly employee assessment to dated records rather than to a generic project story. Our documentation guide provides a checklist and a template to structure those records. If a significant fact is missing, investigate it rather than filling the gap with a hypothetical example. The 2027 changes are proposed, not decided, and must not be used to make the current examples more permissive. Check the 2027 status page separately. When your assessment and monthly data are ready, use the calculator to estimate value while keeping uncertainty and evidence gaps visible for the final human review.

Read the complete R&D deduction guide

Calculate your potential deduction

More guides

See what the R&D deduction could mean for your company

Create a free account to compare the current rules with the 2027 proposals and gather your evidence in one place.

Create a free account