Question 1

Do we need to update our personal data processor agreements (PUB) when more metadata is sent?

Accepted Answer

No.

You already send personal data to Kivra in connection with API calls and via the salary specification as PDF. The division of responsibilities between you, your customer (sending company) and Kivra is unchanged.

The metadata that is now structured continues to be used for the same purpose – to convey salary statements to the user. Any future sharing of data will only take place on behalf of the user and with active consent.

Question 2

What legal basis do we have to share more personal data?

Accepted Answer

The information that is now requested is already sent in PDF format today. The difference is that it is structured as metadata.

If a user in the future chooses to share information further, for example in a loan application, this will be done on the user's initiative and with active consent. Kivra then acts as a personal data processor on behalf of the user. This is updated in our [general terms and conditions under 2.1](https://kivra.se/en/about-kivra/terms/general-terms-and-conditions).

Question 3

We are hesitant to send “hidden metadata.” What do you think about that?

Accepted Answer

The information is not hidden from the user. On the contrary, the goal is to make the data more transparent and easier to overview. The user gets better insight into their data and the ability to share selected data safely and in a controlled manner.

Question 4

You are requesting new data points that we have not previously sent. What is your reasoning?

Accepted Answer

The selection of metadata is based on a preliminary study of what is considered the standard for salary slips in Europe. We have had a dialogue with major Nordic banks and other actors who use salary information in credit and employment processes.

Salaryslip is part of our adaptation to upcoming European initiatives, including EU Wallet. Our goal is to create a long-term sustainable and standardized structure for citizens to be able to share their data with trusted parties.

Question 5

Are all fields mandatory?

Accepted Answer

No.
Only the fields marked as *required* in the specification are mandatory. All other fields are optional.

Question 6

When can we start sending metadata?

Accepted Answer

You can begin testing in the sandbox environment immediately.
It is also possible to send metadata in production. Development is complete on our side.

Question 7

When do we need to be ready?

Accepted Answer

Salaryslip will replace letter.salary on October 1, 2026.
By that date at the latest, you must have updated to the new type (salaryslip) and ensured that all metadata marked as *required* is sent according to the updated specification.
We recommend planning the implementation well in advance of this date.

Question 8

Is the Retain function supported for salaryslip?

Accepted Answer

Yes.
Our Retain service, which enables storage and lifecycle management of deliveries according to the agreed lifecycle, also supports the new type salaryslip.
The technical documentation has been updated on the [developer site](https://kivra.se/en/business/for-developers).

Question 9

Will Kivra continue to support HTML/UI-rendered payslips?

Accepted Answer

Yes. If you submit HTML/responsive content together with salaryslip, it will be displayed instead of the structured view. The PDF version will still be shown as part of the delivery, even if responsive content is submitted.
Salaryslip replaces letter.salary on October 1, 2026.

Salary slips with Kivra

6 382 729

217 772

56 528

Structured and searchable salary data

Built for cellphone use

Prepared for secure sharing

Adapted to upcoming European standards (EU Wallet)

Salaryslip – new standard for salary slips in Kivra

Get started & FAQ

To get started with Salaryslip you will need:

1. Uppdatera metadata-fält enligt specifikation

2. Byta typ till salaryslip

3. Testa i sandbox/testmiljön

Read more about how payslips in Kivra works

FAQ