Skip to main content
PUT
Update a SIPL person
In a submission this edits the not-yet-reported person in place. In a correction it amends the already-reported one; amending a person the tax authority has never seen is rejected, so add new persons with POST instead. This replaces the person, so send all their accounts every time, not just the ones that changed.

Authorizations

Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Path Parameters

submissionId
string
required
clientPersonId
string
required

Body

application/json

A person reported under SIPL, with every account of theirs you paid income into. The person is the unit of reporting: it becomes exactly one reportable person entry, and a correction replaces it whole, accounts included. SIPL reports legal entities as well as natural persons, so send either individual or organisation. Only persons whose income across all their accounts reaches 15000 EUR are reportable; the total is summed from the accounts rather than sent.

clientPersonId
string
required

Your own stable id for this person. Identifies them within the submission, so it must be unique across the persons you push, and it is how you address them on update and delete.

Maximum string length: 255
Example:

"CLIENT-000123"

accounts
object[]
required

List of accounts with the income paid into each of them

Required array length: 1 - 1000 elements
individual
object

The reportable natural person. Given instead of organisation.

organisation
object

The reportable legal entity. Given instead of individual.

Response

Person updated

Result of pushing, updating or deleting a single person

status
enum<string>
required
Available options:
SUCCESS,
FAILED
errors
object[]
required

Why the person was rejected. Empty when accepted.

clientPersonId
string

Your id for the person, echoed back to correlate this result with your record

Example:

"CLIENT-000123"

Last modified on September 1, 2026