---
title: "How does LUSID resolve transactions to custodian accounts?"
slug: "how-does-lusid-resolve-transactions-to-custodian-accounts"
updated: 2026-08-14T09:26:53Z
published: 2026-08-14T09:26:53Z
canonical: "support.lusid.com/how-does-lusid-resolve-transactions-to-custodian-accounts"
---

> ## 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 does LUSID resolve transactions to custodian accounts?

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/custodian_account_resolution (5).png)

## Understanding resolution types

For each successfully-resolved movement in a transaction, LUSID populates a `resolvedCustodianAccount.resolutionType` field on the [output transaction](/v1/docs/input-and-output-transactions):

| `resolutionType` field value | Explanation |
| --- | --- |
| `BookingEntry` | The resolved custodian account is explicitly nominated in the `custodianEntries` field when loading the transaction. |
| `RelatedAccount` | The resolved custodian account is *related* to the one explicitly nominated in the `custodianEntries` field when loading the transaction. |
| `PortfolioDefault` | The resolved custodian account is the default for the account type. |
| `ContextCustodian` | The resolved custodian account is *derived* from the original holding. This typically occurs for transactions automatically generated by LUSID in response to instrument events (such as bond coupons) and corporate actions (such as cash dividends), where the original instrument is a security but the cash proceeds/outlay should be assigned to a cash custodian account. |

You can examine the resolution reason by adding the **Resolved custodian accounts** field to the **Portfolio Management > Transactions** dashboard in **Output** mode, for example:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-Y1P7WLQ6.png)