---
title: "What is a holding ID?"
slug: "what-is-a-holding-id"
tags: ["holdingId"]
updated: 2025-10-30T17:09:06Z
published: 2025-10-30T17:09:06Z
canonical: "support.lusid.com/what-is-a-holding-id"
---

> ## 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.

# What is a holding ID?

A *holding ID* is an identifier for a holding in a [transaction portfolio](/v1/docs/what-is-a-transaction-portfolio) that is:

- Unique across portfolios. For example, a Microsoft holding in a portfolio **does not** share an ID with any other holding in a different portfolio, even another Microsoft holding.
- Unique across [sub-holding keys](/v1/docs/what-is-a-sub-holding-key-shk) (SHKs) in a portfolio. For example, a Microsoft holding tagged by one SHK **does not** share an ID with a Microsoft holding tagged by a different SHK.
- Shared across [tax lots](/v1/docs/what-are-taxlots) in a portfolio. For example, a Microsoft holding purchased in one tax lot **does** share an ID with a Microsoft holding purchased in a different tax lot.
- Shared across unsettled and settled cash holdings in a portfolio. For example, a temporary USD balance of [holding type](/v1/docs/what-are-the-holding-types) `A` **does** share an ID with a settled USD balance of holding type `B`.

> **Note**: You can audit holding IDs in a [valuation report](/v1/docs/how-do-i-perform-a-valuation) using the `Holding/HoldingId` metric. In addition, a `Holding/UniqueId` metric returns a GUID that *is* unique across all the circumstances bulleted above.

Consider a portfolio with a tax lot accounting method of `FirstInFirstOut` and a SHK that divides holdings into Growth and Income strategies. The following transactions are recorded for that portfolio:

| **Transaction type** | **Instrument** | **Currency** | **Trade date** | **Settlement date** | **Units** | **Total consideration** | **Strategy** | **Notes** |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| FundsIn | USD | USD | 1 July 2023 | 3 July 2023 | 15000 | 15000 | Income |  |
| Buy | BP | GBP | 2 July 2023 | 4 July 2023 | 500 | -5000 | Growth |  |
| Buy | Microsoft | USD | 3 July 2023 | 5 July 2023 | 300 | -3000 | Income | Tax lot #1 |
| Buy | Microsoft | USD | 4 July 2023 | 6 July 2023 | 100 | -1100 | Income | Tax lot #2 |
| Dividend | Microsoft | USD | 5 July 2023 | 7 July 2023 | 400 | 40 | Income | 10% of units held |

Calling the [GetHoldings](https://www.lusid.com/docs/api#operation/GetHoldings) API on 6 July 2023 returns the following five holdings. Note the ID of the settled USD balance and the unsettled accrual for the cash dividend transaction is the same:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/a6860e70-5d30-480f-8364-18be78d92039.png)

Calling the `GetHoldings` API with `byTaxlots` set to `True` for 6 July 2023 returns the following six holdings. Note the ID of Microsoft in different tax lots is the same:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/ffa7dd79-1952-4bdc-a23e-2461b4bf6eb6.png)

You can call the [GetHoldingContributors](https://www.lusid.com/docs/api#operation/GetHoldingContributors) API with a particular holding ID to audit the transactions that have contributed to that position. For example, the following three transactions contributed to the Microsoft holding with ID `67940167`:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/c9444964-b289-45dd-8f40-97359f5fc23b.png)

The following four transactions contributed to the USD holding with ID `67940164`:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/330ebe32-dc72-4a15-aed3-513386ad28b9.png)