--- title: "How do I allocate executions?" slug: "how-do-i-allocate-blocks" updated: 2025-10-10T11:26:07Z published: 2025-10-10T11:26:07Z canonical: "support.lusid.com/how-do-i-allocate-blocks" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.lusid.com/llms.txt > Use this file to discover all available pages before exploring further. # How do I allocate executions? LUSID has a variety of built-in allocation algorithms that you can use to allocate your executions to the portfolios of each order. [Read about LUSID’s allocation algorithms.](/v1/docs/allocating-fills-automatically-using-allocation-algorithms) You have several options for defining when LUSID should book an allocation as a transaction: - Automatically at close of business or another specified time trigger. - Based on the state, such as when a placement is 100% filled. - On receipt of a Done for Day (DFD) FIX message for individual orders. For example, if you configure a placement to be filled over multiple days, upon receiving a DFD message and knowing you won't receive any more fills for the order that day, LUSID can book all existing allocations for the order as transactions. - As soon as you allocate a fill. - When you choose to manually book an allocation as a transaction. > [!NOTE] > **Note:** If you need assistance setting up an automated option from the list above, [contact support](https://www.finbourne.com/contact/). There are several ways to allocate executions in LUSID: - [Using the Order Blotter in the LUSID web app](/v1/docs/how-do-i-allocate-blocks#using-the-order-blotter-in-the-lusid-web-app) - [Using the LUSID REST API](https://www.lusid.com/docs/api/lusid/endpoints/allocations/UpsertAllocations) - [Using Luminesce](/v1/docs/lusidallocationwriter) ## Using the Order Blotter in the LUSID web app You can allocate one or more executions at a time using the Order Blotter in the LUSID web app. To do so: 1. Sign in to the [LUSID web app](https://www.lusid.com/app). 2. Navigate to **Portfolio Management > Order Blotter** via the top left menu. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(770).png?sv=2026-02-06&spr=https&st=2026-11-04T02%3A00%3A36Z&se=2026-11-04T03%3A00%3A36Z&sr=c&sp=r&sig=V%2BYwGEu43%2BWs6mmi%2BpQ%2B9e0cMjQ2HFevS6ag6tOVaEE%3D) 3. Click anywhere on the row of the order block you wish to create allocations for. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(666).png?sv=2026-02-06&spr=https&st=2026-11-04T02%3A00%3A36Z&se=2026-11-04T03%3A00%3A36Z&sr=c&sp=r&sig=V%2BYwGEu43%2BWs6mmi%2BpQ%2B9e0cMjQ2HFevS6ag6tOVaEE%3D) 4. Navigate to the **Placements** tab. 5. Click the **Create allocation** button. > [!NOTE] > Note > > - You can only create allocations if you have received at least one execution for the placement. > - If you receive executions across more than one date, LUSID creates separate allocations for each date. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(667).png?sv=2026-02-06&spr=https&st=2026-11-04T02%3A00%3A36Z&se=2026-11-04T03%3A00%3A36Z&sr=c&sp=r&sig=V%2BYwGEu43%2BWs6mmi%2BpQ%2B9e0cMjQ2HFevS6ag6tOVaEE%3D) 6. Choose an **Allocation Algorithm** from the dropdown. [Read about allocation algorithms and their codes.](/v1/docs/allocating-fills-automatically-using-allocation-algorithms#appendix-a-allocation-algorithm-codes) ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(669).png?sv=2026-02-06&spr=https&st=2026-11-04T02%3A00%3A36Z&se=2026-11-04T03%3A00%3A36Z&sr=c&sp=r&sig=V%2BYwGEu43%2BWs6mmi%2BpQ%2B9e0cMjQ2HFevS6ag6tOVaEE%3D) 7. Click **Allocate**. LUSID suggests how to distribute the available executions across your placements and portfolios and saves each row as an allocation. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(687).png?sv=2026-02-06&spr=https&st=2026-11-04T02%3A00%3A36Z&se=2026-11-04T03%3A00%3A36Z&sr=c&sp=r&sig=V%2BYwGEu43%2BWs6mmi%2BpQ%2B9e0cMjQ2HFevS6ag6tOVaEE%3D) 8. (Optional) If you are not yet ready to book the suggested allocations as transactions, click the ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(683).png?sv=2026-02-06&spr=https&st=2026-11-04T02%3A00%3A36Z&se=2026-11-04T03%3A00%3A36Z&sr=c&sp=r&sig=V%2BYwGEu43%2BWs6mmi%2BpQ%2B9e0cMjQ2HFevS6ag6tOVaEE%3D) icon. LUSID saves your allocations, but they are not confirmed until you book them as transactions. > [!NOTE] > Note > > - You can reallocate up until an allocation is booked as a transaction. > - You can monitor your allocations via the **Allocations** tab (click the ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(685).png?sv=2026-02-06&spr=https&st=2026-11-04T02%3A00%3A36Z&se=2026-11-04T03%3A00%3A36Z&sr=c&sp=r&sig=V%2BYwGEu43%2BWs6mmi%2BpQ%2B9e0cMjQ2HFevS6ag6tOVaEE%3D) icon to display any new allocations): ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(684).png?sv=2026-02-06&spr=https&st=2026-11-04T02%3A00%3A36Z&se=2026-11-04T03%3A00%3A36Z&sr=c&sp=r&sig=V%2BYwGEu43%2BWs6mmi%2BpQ%2B9e0cMjQ2HFevS6ag6tOVaEE%3D) 9. Once you are ready to book the allocations as transactions, return to the **Create allocations** screen (steps 6 and 7). At this point you can also choose to: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(686).png?sv=2026-02-06&spr=https&st=2026-11-04T02%3A00%3A36Z&se=2026-11-04T03%3A00%3A36Z&sr=c&sp=r&sig=V%2BYwGEu43%2BWs6mmi%2BpQ%2B9e0cMjQ2HFevS6ag6tOVaEE%3D) - Manually override values in the **Allocation** column by typing directly into the cell. - Add fees and commission, or any other additional columns via the **Configuration** icon. Note that LUSID automatically adds [fees and commission](/v1/docs/managing-order-fees-and-commissions) when booking transactions if an allocation matches your defined rules. *More information coming soon.* 10. Click **Create Transactions** to book the allocations as transactions in their respective portfolios. Once booked, you can monitor and update your transactions via the **Transactions** dashboard. [See how.](/v1/docs/how-do-i-create-or-update-a-transaction) --- ### FAQ #### How do I override the Total Consideration of a booked transaction? You can configure [FIX tags](/v1/docs/understanding-how-lusids-order-management-system-works) on your executions that propagate to your subsequent allocations and booked transactions. These tags enable you to override certain fields, including Total Consideration. If you need assistance with this, [contact support](https://www.finbourne.com/contact/). Alternatively, you can edit your transaction to update the **Gross Trade Amount** and **Commission & Fees**. [See how.](/v1/docs/how-do-i-create-or-update-a-transaction#updating-a-transaction) #### How are fields in an allocation mapped to fields in a booked transaction? LUSID maps fields you specify for an allocation to the following transaction fields: | Allocation field | Transaction field | | --- | --- | | `price.currency` | `transactionCurrency` | | `"<id.Scope>/<id.Code>"` | `transactionId` | | `side` | `type` | | `instrumentIdentifiers` | `instrumentIdentifiers` | | `date` | `transactionDate` | | Uses `settlementDate` if available. If not available, uses `date` and the instrument [settlement cycle business days](/v1/docs/roll-conventions-and-business-day-conventions) offset. | `settlementDate` | | `quantity` | `units` | | `price.amount` | `transactionPrice` | | `settlementCurrency` | `totalConsideration.currency` | | Uses `Transaction/Override/TotalConsideration` property value if available. If not available, uses transaction type calculation or standard formula.* | `totalConsideration.value` | | `Transaction` properties from allocation and fees | `properties` | | `counterparty` | `counterpartyId` | | Uses `Portfolio/default/OrderProcessingTransactionTypeSource` property value if available. If no value is available, uses `"default"`. | `source` | | `settlementCurrencyFxRate` | `exchangeRate` | | null | `otcConfirmation` | | `allocatedOrderId` | `orderId` | | `id` | `allocationId` | | null | `custodianAccountId` | > [!NOTE] > *`totalConsideration.Value` > > LUSID maps the `totalConsideration.Value` for a transaction using the following prioritisation: > > 1. Using the value specified for the `Transaction/Override/TotalConsideration` property (if a value is specified). > 2. If the above property isn’t set but an applicable [transaction type calculation](/v1/docs/what-is-a-transaction-type-calculation) exists, LUSID sets `totalConsideration.Value` to `0` and applies the calculation to the output transaction. > 3. If neither 1 or 2 applies to the allocation, LUSID calculates the value using the following formula: $\text{TotalConsideration} = (\text{GrossTradeAmount} + \text{AccruedInterest}) \times \text{SettlementCurrencyFxRate}$