> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-8.29-coming-soon/voyage-management-system/step-by-step-guides/chartering/time-charter-contracts/internal-tc-relet-creation.md). # Internal TC Relet Creation Rather than manually creating and configuring a new TC In from scratch, the **Create Internal TC Relet** action generates the TC In as a copy of the TC Out and automatically establishes the link between the two contracts. Counterparty fields are pre-filled and kept synchronised by the system > **Note:** The action is available on TC Out contracts only. Once an Internal TC Relet has been created for a contract, the action is disabled — each TC Out contract can have only one linked TC Relet. *** ### Before Starting Before creating an Internal TC Relet, confirm the following: * The TC Out contract exists. * The charterer on the TC Out contract is linked to a company via the Internal Business Partner field in the Company Master Data. * The Company of the TC Out contract has a linked Internal Business Partner with type Head Owner *** ### Steps **1. Open the TC Out contract** **2. Open the three-dot menu and select Create Internal TC Relet** > **Important:** If a connected TC Relet already exists for this contract, the **Create Internal TC Relet** option is disabled. The **Create Internal TC Relet** modal opens. **3. Complete the modal fields** | Field | Description | | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Company / Business Unit** | The internal entity for the TC In contract. Defaults to the first company–business unit combination derived from the TC Out charterer company. Required. | | **Owner** | Pre-filled from the TC Out contract's internal business partner. Read-only, cannot be changed in this modal. | | **Charterer** | Pre-filled from the charterer on the TC Out contract. Read-only, cannot be changed in this modal. | The **Create** button is enabled once all required fields have valid values. If a required field is missing, an inline error message explains what needs to be completed before proceeding. **4. Click Create** VMS creates a copy of the TC Out contract, configured as a TC In and linked back to the original TC Out via the relet reference. *** ### After Creation Once the Internal TC Relet is created: * Both the TC Out and the new TC In display a **Relet** badge in the drawer header. The badge is clickable and navigates between the two linked contracts. * The **Owner** and **Charterer** fields on both contracts are locked. They are managed automatically by the system to remain synchronised and cannot be edited manually on either contract. * The new TC In contract is ready for further configuration — hire periods, costs, and voyage nominations can be added independently from the TC Out. *** ### What Is Copied The TC In created by the relet action carries over the main terms of the TC Out contract, including vessel details, contract period, hire rate, payment terms, and other header-level fields. ### What Is Not Copied The following are intentionally excluded from the TC In contract: | Excluded | Reason | | ------------------------ | ---------------------------------------------------------------------------------------------- | | **Voyages** | Voyage history and planned voyages belong to the originating contract and are not transferred. | | **Default Bank Account** | The receiving entity manages its own payment details. | | **TC Benchmark Percent** | Risk benchmarking is specific to each entity and must be set independently. | | **TC Benchmark Index** | Risk benchmarking is specific to each entity and must be set independently. | | **Exposure Duration** | Exposure t is specific to each entity and must be set independently. | *** ### Data Synchronisation After the Internal TC Relet is created, VMS keeps counterparty details synchronised between the two contracts: * The **Charterer** on the TC Out is kept in sync with the **Charterer** on the TC In. * The **Owner** on the TC Out is kept in sync with the **Owner** on the TC In. Changes to these values on one contract are reflected automatically on the other. This is why the Owner and Charterer fields are disabled for manual editing on both the relet TC In and the relet TC Out. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dataloy.com/release-8.29-coming-soon/voyage-management-system/step-by-step-guides/chartering/time-charter-contracts/internal-tc-relet-creation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.