R&D Tax Relief for Software Startups in Sweden
By CodexierPublished 5 min read
Sweden has a tax relief for companies whose employees work on research and development: the forskningsavdrag, a reduction of the employer contributions you pay on their salaries. For a software startup paying developers, it can lower the cost of building the product noticeably. This guide explains how it works in principle, what kind of software work can qualify, what records you need, and when to bring in an accountant. The rules and levels are set by law and change over time, so always check the current details with Skatteverket.
What the R&D deduction covers
The mechanism is simple: instead of a grant you apply for, you pay less in employer contributions for qualifying people. That makes it predictable, but it also means the burden of proof is on you. If Skatteverket reviews your company and your records do not hold up, the deduction can be reversed with a tax surcharge on top.
Which work can qualify
The law talks about research and development carried out on a commercial basis, and Skatteverket's guidance describes systematic work aimed at new knowledge or new or substantially improved products, processes or services. For software that means the line goes between building something genuinely new and doing routine work with known methods.
| Likely to qualify | Unlikely to qualify |
|---|---|
| Developing a new product where the technical solution is uncertain | Installing and configuring existing software |
| Designing and testing new algorithms or architectures | Routine bug fixes and maintenance |
| Building prototypes to test whether an approach works | Adapting a standard system for a customer |
| Systematic experiments with documented hypotheses and results | Sales, support, administration and marketing |
Examples for orientation. Whether a specific project qualifies is judged case by case. See Skatteverket's guidance on forskningsavdrag.
Records you must keep
The records are what make the deduction safe to claim. Set them up from the first month, not when someone asks for them. The good news is that a software team already produces most of the evidence in its issue tracker and version control; it just needs to be connected to people and time.
- A short project description per R&D project: the problem, why the solution is uncertain, and the goal.
- Time reports per person per month, showing time on R&D and time on other work.
- Links from time to evidence: tickets, commits, test results, design documents.
- Notes of what was tried, what failed and what was learned. Failed experiments are strong evidence of genuine development.
- Employment contracts or role descriptions that show the person works with development.
Applying it in the employer return
The deduction is claimed in the monthly employer declaration at individual level (arbetsgivardeklaration på individnivå), where you mark which employees qualify and report the reduction. Your payroll system or accountant usually handles the mechanics, but they need your input on who qualifies each month, since that can change as people move between product work and customer projects.
Limited company with salaried founders
Founders taking a salary from their AB are employees and can qualify if they work with R&D.
Sole trader
No employer contributions on your own income, so the deduction does not apply to your own work.
Bought-in developers
Invoices from consultants or agencies do not carry employer contributions, so they give no deduction.
Mixed roles
A developer who also does support must meet the time requirement on R&D; keep the split visible in time reports.
When to ask an accountant
Talk to an accountant before the first claim, when your team grows, when you start doing customer projects alongside product work, and if you are part of a group of companies, since caps can apply at group level. A short review is cheap compared with a reversed deduction. For the wider picture of paying for development, see our guide to funding an MVP in Sweden.
A note on how this relates to buying development: the deduction rewards having your own developers on payroll. If you buy an MVP from an external team, you get no forskningsavdrag on that invoice, but you may get a product sooner and hire later. Our MVP planning blueprint helps you decide what to build first and whether to build in-house or buy, and fixed prices are on our pricing page. We do not give tax advice; for that, your accountant is the right person. You can still book a short call about the build decision.
Frequently asked questions
Is the forskningsavdrag a grant I apply for?
No. It is a reduction of employer contributions that you claim yourself in the monthly employer declaration, backed by your own records.
Does building a SaaS product count as research and development?
Parts of it can, when the work is systematic and aims at something genuinely new with real technical uncertainty. Routine features built with known methods usually do not.
Can I claim the deduction for a consultant?
No. The deduction applies to employer contributions on salaries. Consultants invoice you, so there are no contributions to reduce.
What happens if Skatteverket rejects the claim afterwards?
You repay the reduction and may be charged a tax surcharge. Good records from the start are the protection.
Planning what to build, and who should build it?
Book 15 minutes. We help you scope the first version and weigh in-house development against buying it, so the budget and the tax picture line up.
Book a free 15-minute call