> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rwa.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Manager Attribution

> How we record the legal managers in a fund's documents, and how we credit each asset to the firm whose strategy investors buy

A tokenized fund often names several firms. Its documents may appoint a management company, an investment manager it delegates portfolio management to, and a sub-adviser. The token may be a feeder that invests in another fund, or a wrapper around a fund someone else issued. We record each of these roles as the documents state them, and we credit the asset to one firm: the asset manager whose strategy and brand the investor is buying.

That gives every asset two managers:

| Concept | Question it answers | JAAA |
| - | - | - |
| **Legal manager** | Which legal entity do the fund documents appoint as manager? | Anemoy |
| **Strategy manager** | Whose investment strategy and brand is the investor buying? | Janus Henderson |

Manager totals, manager pages and league tables count each asset under its **strategy manager**. The legal manager and the other roles appear on each asset's page and in their own fields.

## Legal roles

We record the roles named in the fund's offering documents, prospectus, factsheet or regulatory filings, using the exact legal entity they name. We don't replace that entity with a brand name.

| Role | What it is |
| - | - |
| **Legal manager** | The investment manager or investment adviser the fund documents appoint. |
| **Management company** | The management company or AIFM, if the fund documents name one. This is common in Luxembourg, Irish and Cayman funds, where a management company delegates portfolio management to an investment manager. When the management company also runs the portfolio, it is the legal manager too. |
| **Sub-adviser** | A firm appointed to manage all or part of the portfolio on behalf of the legal manager, also called a sub-investment manager. |
| **Master fund** | For a feeder fund, the fund it invests in. The master fund has its own legal manager, management company and sub-adviser. |
| **Underlying asset** | For a third party-sponsored token, the asset it represents. See [Tokenization Sponsorship](https://docs.rwa.xyz/frameworks/tokenization-sponsorship.md). |

Many assets have only some of these roles, and some have none: stablecoins and tokenized stocks usually have no manager.

## How we find the strategy manager

We apply the rules below to the asset's own fund, in order.

1. **Master fund.** If the fund is a feeder into a master fund, the strategy manager is the master fund's strategy manager, found by applying these same rules to the master. The master fund always decides, whoever manages the feeder.
2. **Passthrough managers.** Otherwise, if the legal manager is a passthrough manager (see below) and the fund has a sub-adviser, the sub-adviser is the strategy manager.
3. **Legal manager.** Otherwise the legal manager is the strategy manager. A passthrough manager with no sub-adviser keeps the credit.
4. **Brand.** We credit the firm's brand: a legal entity that belongs to a larger asset manager rolls up to its top-level parent manager. A firm with no parent manager is its own brand.
5. **Wrappers.** If the asset's own fund resolves no manager and the asset is a third party-sponsored token, we apply the same rules to its underlying asset.

If none of these finds a manager, the asset has no strategy manager.

### Passthrough managers

Some firms act as the regulated manager of funds whose strategy is run by someone else: they provide the license, the fund structure and the tokenization, and appoint the strategy firm as sub-adviser. When such a fund has a sub-adviser, we credit the sub-adviser, because that is the strategy and brand the investor is buying. The passthrough manager still appears as the legal manager.

We treat a firm as a passthrough manager only when its own documents or filings show that it lends its license to strategies run by others. A sponsor that hires a sub-adviser for its own fund keeps the credit: WTGXX stays with WisdomTree even though Voya sub-advises it, because investors are buying a WisdomTree fund.

### Master and feeder funds

Many tokenized funds are feeders: the token holder owns shares of a feeder vehicle, often managed by a tokenization platform, and the feeder invests in a master fund run by the strategy manager. We record the master fund and its own managers, and the feeder is credited to the master fund's strategy manager.

The master fund always decides. This holds even when the feeder's manager is not a passthrough manager, and it applies through several levels if a master fund is itself a feeder.

Master funds are not tokenized, so they add no assets or value to any manager's totals. They exist in our data only to record the structure.

### Wrappers

A third party-sponsored token, such as a tokenized ETF issued by a tokenization platform, usually has no manager of its own. We credit it to the strategy manager of the asset it wraps, so a tokenized iShares ETF counts toward BlackRock.

If the wrapper's own vehicle has a manager recorded, the wrapper's own fund decides first, as for any other asset.

### Brands and legal entities

Large asset managers act through many legal entities. The Apollo Diversified Credit Fund, for example, names Apollo Capital Credit Adviser, LLC as adviser and Apollo Credit Management, LLC as sub-adviser. We record those entities in the legal roles and credit the fund to their parent, **Apollo Global Management**, so the firm appears once in manager totals and league tables.

A legal entity is credited to the top-level parent in its ownership chain that is itself an asset manager. Firms that share a name but are separately owned stay separate: Fidelity Investments in the US is a different manager from Fidelity International.

## Worked examples

| Asset | Legal manager | Strategy manager | Source |
| - | - | - | - |
| **JAAA** | Anemoy | Janus Henderson | `SUB_ADVISOR` |
| **ACRED** | Securitize Capital | Apollo Global Management | `MASTER_FUND` |
| **IVVon** | None | BlackRock | `UNDERLYING` |
| **HLSCOPE** | Securitize Capital | Hamilton Lane | `MASTER_FUND` |
| **WTGXX** | WisdomTree Digital Management | WisdomTree Digital Management | `LEGAL_MANAGER` |

**JAAA** (Janus Henderson AAA CLO Fund). The fund's legal manager is Anemoy, and Janus Henderson is its sub-investment manager. Anemoy provides the fund's license and structure while Janus Henderson runs the strategy, so JAAA is credited to Janus Henderson.

**ACRED** (Apollo Diversified Credit Securitize Fund). The token is a feeder fund managed by Securitize Capital that invests in the Apollo Diversified Credit Fund. The master fund decides: its adviser, Apollo Capital Credit Adviser, LLC, rolls up to Apollo Global Management.

**IVVon** (iShares Core S\&P 500 ETF, Ondo Tokenized). The token is issued by a third party and records no manager of its own. We follow it to the underlying iShares Core S\&P 500 ETF, whose manager is BlackRock.

**HLSCOPE** (Hamilton Lane Senior Credit Opportunities Securitize Fund). The token is a feeder managed by Securitize Capital that invests in the Hamilton Lane Senior Credit Opportunities Fund. The master fund's management company is FundRock LIS S.A., a third-party AIFM, and it delegates portfolio management to Hamilton Lane Advisors, L.L.C., the master's legal manager. That firm rolls up to Hamilton Lane. The management company is recorded but never decides attribution.

**WTGXX** (WisdomTree Treasury Money Market Digital Fund). WisdomTree is the fund's adviser, with Voya Investment Management as sub-adviser. WisdomTree is not a passthrough manager, so it keeps the credit.

## History

Historical manager totals use each asset's current strategy manager. When an asset's attribution changes, for example because we record its master fund, correct a manager from the fund documents, or link a legal entity to its parent, its full history moves to the new strategy manager. Manager time series therefore always reflect today's attribution, not the attribution at each past date.

## In the API

On assets:

| Field | Meaning |
| - | - |
| `strategy_manager` / `strategy_manager_id` | The strategy manager. Group by it with `groupBy=strategy_manager` in aggregates and time series. |
| `strategy_manager_source` | Which role or link the strategy manager came from (below). |
| `legal_manager` / `legal_manager_id` | The legal manager of the asset's own fund, as named in its documents. Empty when none is recorded, as for most wrappers. |
| `management_company_id` | The management company of the asset's own fund, if any. |
| `manager` / `manager_id` | **Deprecated** and will be removed. Equal to `strategy_manager` / `strategy_manager_id`, as `groupBy=manager` is to `groupBy=strategy_manager`. Use the strategy manager fields, or on `/v4/assets` the legal manager fields when you mean the manager named in the fund documents. |
| `literal_structure` | The recorded roles: legal manager, sub-adviser and management company of the asset's own fund, the master fund with its own roles, and the underlying asset of a wrapper with its roles. |

`strategy_manager_source` takes these values:

| Value | The strategy manager is |
| - | - |
| `LEGAL_MANAGER` | The legal manager of the asset's own fund. |
| `SUB_ADVISOR` | The sub-adviser, because the legal manager is a passthrough manager. |
| `MASTER_FUND` | The strategy manager of the master fund. |
| `UNDERLYING` | The strategy manager of the underlying asset of a wrapper. |

Rolling a legal entity up to its brand doesn't change the source: an asset whose legal manager is a subsidiary of a larger manager reports `LEGAL_MANAGER`, even though the credited name is the parent.

`strategy_manager_id`, `legal_manager_id` and `strategy_manager_source` can be used as filters. See [Manager roles](https://docs.rwa.xyz/schemas/assets.md#manager-roles) in the Assets Schema for the full field list.

## In the Snowflake data share

The [`ASSETS` view](https://docs.rwa.xyz/snowflake/tables#assets) carries the same concepts:

| Column | Meaning |
| - | - |
| `STRATEGY_MANAGER_ID` / `STRATEGY_MANAGER_NAME` | The strategy manager, matching `strategy_manager` in the API. |
| `STRATEGY_MANAGER_SOURCE` | Same values as `strategy_manager_source` in the API. |
| `LEGAL_MANAGER_ID` / `LEGAL_MANAGER_NAME` | The legal manager of the asset's own fund. |
| `MANAGEMENT_COMPANY_ID` / `MANAGEMENT_COMPANY_NAME` | The management company of the asset's own fund, if any. |
| `SUB_ADVISOR_ID` / `SUB_ADVISOR_NAME` | The sub-adviser of the asset's own fund. |
| `MASTER_FUND_NAME` | The master fund a feeder invests in. |
| `MASTER_FUND_MANAGER_NAME` | The legal manager of that master fund. |
| `MANAGER_ID` / `MANAGER_NAME` | **Deprecated.** Equal to `STRATEGY_MANAGER_ID` / `STRATEGY_MANAGER_NAME` and kept for existing queries. Use `STRATEGY_MANAGER_ID` / `STRATEGY_MANAGER_NAME` or `LEGAL_MANAGER_ID` / `LEGAL_MANAGER_NAME`, depending on which manager you mean. |

## On RWA.xyz

* An asset page's **Managed by** header shows the strategy manager.
* Manager pages and league tables count assets under their strategy manager.

> [!NOTE]
>
> Attribution follows the fund documents we hold. If you believe an asset is credited to the wrong manager, contact us at [team@rwa.xyz](mailto:team@rwa.xyz) with the relevant documents.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.