> For the complete documentation index, see [llms.txt](https://docs.samesystem.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samesystem.dev/business-guides/employee-lifecycle-management/rehire-employee/leave-and-rehire-consecutive-contracts.md). # Leave and rehire (consecutive contracts) An existing employee has been terminated with a future end date. This means the current contract has a future end date. The user is rehired while the current contract is still active. The rehiring will require a new contract to be created with a new start date. You will have two options to complete this task:

Rehire user

Since the user should be active all time, the start date for the new contract should be the current contract end date + 1 day (after the termination date), if you choose this option for rehiring. > Example:\ > Current contract A has an end date: 2026-01-28\ > New contract B must have a start date: 2026-01-29

To rehire a terminated employee in a single call, the following endpoint can be used: POST /{clientToken}/contracts/rehire Request body is an object conforming to the `ContractCreateInput` schema. The following fields are required in the ContractCreateInput schema:


`departmentId`	An internal (SameSystem) department id or our own external id. All departments with internal ids can be retrieved from API v1.
`startDate`	This is the start date for the new contract and will be the date from where the rehired user will be active.
`titleId`	A SameSystem title id. All titles can be retrieved from API v2.
`userId`	A SameSystem unique user id. The value is present in the user object: `user.id`. It can also be a custom Id, like an employee id or payroll number from an external system. If a custom id is used, you must include the parameter `useCustomId=true` in the call.

{% hint style="info" %} **Notice:** Assigning the correct title is very important as the title will control user rights, access to different absence types etc. If your external system uses its own identifiers, you can pass `useExternalDepartmentId=true` as a query parameter and the `departmentId` field will be treated as an external ID rather than an internal SameSystem ID {% endhint %}

Create a new contract

Since the user should be active all time, the start date for the new contract should be equal or lower to the current contract end date, if you choose to use this option to create a new contract. > Example: > > Current contract A has an end date: 2026-01-28 > > New contract B must have a start date: 2026-01-28 or lower.
> > When you add a start date: 2026-01-28 for the new contract B, the end date on contract A will be automatically adjusted -1 day, to: 2026-01-27. > > When you add a start date: 2026-01-27 for the new contract B, the end date on contract A will be automatically adjusted -1 day, to: 2026-01-26.

You will have the option below to rehire an employee by creating a new contract: * [Contract changes - Create new contract on existing user](/business-guides/employee-lifecycle-management/changes-to-employees/contract-changes.md#create-a-new-contract-on-existing-user). * [Contract changes - Create/update multiple users and contracts in one call (bulk creation)](/business-guides/employee-lifecycle-management/changes-to-employees/contract-changes.md#create-update-multiple-users-and-contracts-in-one-call-bulk-creation-update) You do not have to remove termination. After the new contract has been created, you can see that the current contract has been adjusted: Current contract end date = new contract start date – 1 day.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.samesystem.dev/business-guides/employee-lifecycle-management/rehire-employee/leave-and-rehire-consecutive-contracts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.