---
title: "Request year transition"
method: PATCH
path: "/year/providers/employers/payrolladministrations/{payrollAdministrationId}/years/{yearId}/requestyeartransition"
tags: ["Year transition"]
---

# Request year transition

`PATCH /year/providers/employers/payrolladministrations/{payrollAdministrationId}/years/{yearId}/requestyeartransition`

## Request

- Base URL: `https://api.loket.nl`
- URL: `https://api.loket.nl/year/providers/employers/payrolladministrations/{payrollAdministrationId}/years/{yearId}/requestyeartransition`
- Auth: none required

__Activity name :__ PatchRequestYearTransitionByPayrollAdministrationIdAndYearId

This endpoint allows the user to request a year transition for a specific payroll administration and year. 
The user can indicate if an email will be sent to the employees and the date on which the employee can access the yearendstatement.
During the year transition the given year will be closed and a new year will be opened.

## Path parameters

- `payrollAdministrationId` string, uuid, required
- `yearId` string, uuid, required

## Headers

- `Authorization` string, required
- `Accept` string, required

## Request body

- YearTransitionPatch
  - `sentEssMail` boolean: Property that indicates if an email will be sent to the employees.
  - `dateAvailableEss` string, date, nullable: The date on which the employee can access the yearendstatement.

## Response `200`

OK

- object: a warning indacateds that the given payload is valide, however take notice of the warning this might ifluence behavour.
  - `version` Version
    - `obsoleteDate` string, date, nullable: The date (can be null) on which the `resourceVersion` is no longer supported/available
    - `resourceVersion` string, date: The resource version of the object in the response
  - `messages` object[]
    - `type` string: Indication of the type of message. See [the general documentation for more information](./#section/Response/Messages)
    - `description` string: Describes the message
    - `id` string, uuid, nullable: In some cases when the message may relate to a specific entity, or specific group of entities, this field provides the identifier of that entity
    - `code` integer: Identifying code for the message
    - `properties` string[]: An array that can contain additional information
  - `content` object

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `409`: Conflict
- `500`: Internal Server Error

---

[API](https://skmtc.dev/loket/apis/loket-api.md) - [All operations](https://skmtc.dev/loket/apis/loket-api/llms.txt) - [OpenAPI document](https://skmtc.dev/loket/apis/loket-api/revisions/32170564148f?raw)
