> 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.31/voyage-management-system/step-by-step-guides/finance/derivatives/allocating-voyages-to-a-derivative-line.md). # Allocating Voyages to a Derivative Line Connecting voyages to a derivative line records which operational voyages are covered by that settlement period. One line can be linked to multiple voyages. > **Current limitation:** Voyage allocation is informational only in this release. The derivative is not factored into voyage P\&L calculations. #### Allocating Voyages 1. Open the derivative drawer. 2. Locate the Derivative Line to allocate voyages to. 3. Click **Add Voyages**. 4. Use the multi-select to search for and select voyages. 5. Confirm. The selected voyages appear listed under the line. #### Removing a Voyage Allocation Open the derivative line's voyage list and use the remove action next to the voyage. Removing the link does not affect the voyage itself. #### Behaviour When Copying a Voyage Copying a voyage in VMS does **not** copy any derivative line allocations to the new voyage. Each allocation must be managed explicitly. Deleting a voyage does not delete its derivative — only the link is removed. *** --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/finance/derivatives/allocating-voyages-to-a-derivative-line.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 `build a script that syncs our docs to a CMS` 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.