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

How to document R&D so you can support the deduction

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

Skatteverket may ask you to show that the work is research or development and that the time is correct. The earlier you document, the easier it gets. This applies whether or not the rules change in 2027.

Checklist per project

  • Project name, period and purpose
  • What is new and which technical problems you are trying to solve
  • Which methods or experiments you use
  • Which people take part and in what role
  • Time per person and month
  • Link to salary cost
  • What distinguishes the work from routine and maintenance

Why documentation is essential

The employer must be able to show that the conditions for the R&D deduction are met for each reporting period if Skatteverket reviews the claim. That applies both to the nature of the project and to each person’s actual work. A job title, a department name or a general statement that your company is innovative is not sufficient evidence.

Skatteverket does not prescribe one universal set of documents that guarantees entitlement. Relevant evidence can include project descriptions, planning records, time reports, research reports and information about funding. The documents need to explain your own work and its connection to research. Read the complete R&D deduction guide before deciding which activities to include.

Document as the work progresses. Dated records make it easier to explain what was known, what was investigated and who did the work. Later summaries can clarify the material, but should not disguise missing evidence or be presented as records written at the time. Keep original versions and explain later corrections.

Make the evidence understandable without relying on a particular employee’s memory. Explain abbreviations, identify attachments and record where the monthly reconciliation is kept. If a reviewer cannot follow the connection between a project, a person’s tasks and the reported hours, clarify it before submitting. Documentation should describe the actual work, not merely repeat the wording of the legislation.

What should be documented?

For each person, record the employer, reporting month, project, duties, actual total working time and qualifying R&D hours. Under current rules, qualifying work must account for at least 15 hours and at least 50 percent of actual working time during the month. Both conditions must be checked. Absence should not be counted as hours worked.

For each project, describe the commercial purpose, period, starting knowledge, what is new or substantially improved, the uncertainties, method and results. For development, explain which research results were decisive for the work. Identify routine activities and support tasks separately. Technical difficulty alone does not establish that the legal definition is met.

Connect the person’s work to remuneration and the monthly calculation. Keep a reconciliation to payroll, including which people were included or excluded and why. Use the R&D deduction calculator for an estimate, but remember that a calculated amount does not confirm entitlement or replace evidence for the underlying conditions.

Proposed, not enacted: changes discussed for 2027 include removing the minimum-hours requirement. Keep applying current rules until a change is enacted and takes effect. Follow the proposed changes for 2027 and distinguish future scenarios from the evidence supporting an actual claim.

Time reporting for R&D

Use a consistent project identifier and reporting month in your time records. Record hours against the work performed, not just a default percentage of salary or a team-wide allocation. A reviewer should be able to follow the link from a person’s monthly summary to the project and the activities described. Explain what your time categories mean.

Show both total actual working time and qualifying R&D time per person and month. Separate routine development, maintenance, support and other tasks from qualifying direct work. Avoid counting the same hour in two projects. Reconcile the totals against absence and payroll information and explain differences before you finalise the monthly evidence.

Decide who records time and who checks it. Keep dates, corrections and reasons for changes so that your records remain understandable after staff changes. This review process is a practical recommendation, not a prescribed approval form. The platform can bring payroll, time and project records together, but you still need to verify their accuracy and the legal conditions.

If historical time reports are incomplete, explain which contemporary records support the reconstruction. Project logs or experiment records can help establish what happened, but do not automatically prove the number of hours for each person. Do not fill gaps with unsupported estimates. Ask Skatteverket or an adviser when the available evidence is uncertain.

Example: project description

The template below is a starting point, not an approved project or a promise of entitlement. Replace the brackets with your own facts and link to dated evidence. Write so that an external reader can understand the research basis and distinguish the qualifying work from ordinary product development. Do not invent results to complete the template.

Project documentation template

Project: [name and identifier]
Period and commercial purpose: [dates and purpose]
Starting knowledge and research basis: [sources and their decisive connection]
New knowledge or substantial improvement: [what and why]
Uncertainties: [what was unknown]
Method and experiments: [plan, alternatives and tests]
Results and conclusions: [outcomes, dates and evidence]
People and work: [roles, monthly hours and linked time records]
Excluded activities: [routine work and support]
Payroll link and attachments: [references]
Written/reviewed: [responsible person, date and version]

Update the description when the project changes direction or moves into routine implementation. Record unsuccessful trials as well as successful results when they explain the investigation. A short, specific description supported by traceable records is more useful than a long sales presentation without a connection to actual work.

Use the same project name in the description, time records and payroll reconciliation. Attach a short list of supporting files with dates and explanations of what each file shows. If you refer to a test result, describe the question tested and why the outcome matters. Keep a clear boundary between measured observations, your interpretation and questions that remain unanswered. The template helps organise this information; it does not decide whether the project qualifies.

How long should evidence be retained?

Distinguish accounting records from other project material. Under Chapter 7, Section 2 of the Swedish Bookkeeping Act, accounting information must be retained until the end of the seventh year after the end of the calendar year in which the financial year ended. That is not a blanket rule stating that every R&D document has an identical retention period.

Bookkeeping Act (1999:1078), Chapter 7, Section 2

Determine which payroll, calculation and supporting records form part of your accounting information. Skatteverket states that employer declarations can be corrected up to six years back. This correction window is not itself a rule requiring you to delete evidence after six years. Keep relevant material accessible during any ongoing review or dispute, and obtain advice before disposing of it.

Establish a retention policy for your circumstances, with restricted access to personal and commercially sensitive information. Preserve files in a readable format and ensure that project references still work after a system change. If classification or retention is uncertain, consult Skatteverket and your accounting adviser rather than relying on an assumed universal R&D retention period.

Common weaknesses in documentation

A common weakness is a project description that says only what was built, without explaining new knowledge or the decisive research results. Another is time reporting that labels an entire department as R&D without describing each person’s actual tasks. These gaps make it difficult to connect the claim to the conditions for the reporting period.

Other weaknesses include missing months, inconsistent project names, unexplained corrections and payroll figures that cannot be reconciled. References to research reports need an explanation of their connection to your own work. A link alone is rarely a useful description. Check the evidence before submission and state clearly what still needs clarification rather than presenting assumptions as verified facts.

Tips

  • Document continuously, not afterwards.
  • Write so that an outsider understands what was new.
  • Keep everything in one place.
Create a free account and gather your evidence in one place

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