--- title: "BlackRock Aladdin File Transfers" slug: "blackrock-aladdin-file-transfers" updated: 2026-04-17T09:51:59Z published: 2026-04-17T09:51:59Z canonical: "support.lusid.com/blackrock-aladdin-file-transfers" --- > ## 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. # BlackRock Aladdin File Transfers FINBOURNE’s BlackRock Aladdin integration allows you to import securities, trades, positions, prices, and other investment data into LUSID through file-based interfaces. > [!NOTE] > Prerequisites > > Before getting started, ensure you have: > > - [x] An active Aladdin contract with BlackRock, including data export capability > - [x] SFTP access configured to deliver files to LUSID Drive > - [x] The list of Aladdin interface numbers you want to import > - [x] [Contacted your FINBOURNE representative](/v1/docs/how-do-i-use-the-support-centre) to enable the integration in your LUSID domain ## Supported Aladdin interfaces BlackRock Aladdin delivers data through numbered interface files (for example INT10, INT11). Each interface provides specific types of data. You can configure your integration to only process the interfaces you need from the following options: | Interface | Type of data | Creates in LUSID | | --- | --- | --- | | INT10 | Security master | [Instruments](/v1/docs/instruments) | | INT11 | Trades | [Transactions](/v1/docs/transactions), [quotes](/v1/docs/market-data) | | INT14 | Positions | [Holdings](/v1/docs/holdings) | | INT15 | Counterparties | [Legal entities](/v1/docs/people-legal-entities-and-relationships) | | INT17 | Issuers | [Legal entities](/v1/docs/people-legal-entities-and-relationships) | | INT21 | Preliminary prices | [Quotes](/v1/docs/market-data), [SRS data](/v1/docs/what-is-structured-result-data) | | INT25 | Factors | [Quotes](/v1/docs/market-data) (`PoolFactor`) | | INT29 | Analytics positions | [Holdings](/v1/docs/holdings) | | INT29Analytics | Analytics position | [SRS data](/v1/docs/what-is-structured-result-data) | | INT54 | Portfolios | Portfolio [properties](/v1/docs/properties) | | INT86 | Economy | [Quotes](/v1/docs/market-data) (FX rates) | | INT95 | NAV | [SRS data](/v1/docs/what-is-structured-result-data) | | INT96 | New cash | [Transactions](/v1/docs/transactions) | | INT107 | Credit ratings (security) | Instrument [properties](/v1/docs/properties) | | INT113 | Strategies | [Custom data type](/v1/docs/how-do-i-create-a-custom-data-type-and-store-reference-data) | | INT144 | Credit ratings (issuer) | Legal entity [properties](/v1/docs/properties) | | INT243 | Collateral detail | [Relational dataset records](/v1/docs/how-do-i-create-a-relational-dataset-definition) | | INT244 | Collateral statement | [Relational dataset records](/v1/docs/how-do-i-create-a-relational-dataset-definition) | | INT274 | Ledger activity | [Transactions](/v1/docs/transactions) | | INT284 | Cash entries | [Transactions](/v1/docs/transactions) | | INT330 | Cash walk-forward | [Holdings](/v1/docs/holdings) | | INT332 | Prices (selected sources) | [Quotes](/v1/docs/market-data) | | Cashflows | Bespoke export | [SRS data](/v1/docs/what-is-structured-result-data) | [See appendix A for more information on each interface.](/v1/docs/blackrock-aladdin-file-transfers#appendix-a-further-information-on-aladdin-interfaces) ## Setting up the integration ### Step 1: Create an integration instance An integration instance is a configuration of data to import from one or more BlackRock Aladdin interface files. > [!NOTE] > Note > > Your BlackRock Aladdin files may arrive individually or bundled in a zip archive (sometimes called a "nugget"); make a note of the type of files you expect LUSID to receive. 1. Navigate to **Integrations > Dashboard**. 2. Select **Create instance** and choose **BlackRock Aladdin**. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-PLIOQ73H.png) 3. Specify the following **Integration details**: - **Name**: A friendly name for this integration instance - **Description**: A detailed description for this integration instance - **Edit imported properties > Add properties**: Select which BlackRock Aladdin data fields to import ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-1761300025233.png) > [!NOTE] > Note > > - You can select the **View imported fields** button and inspect the **Source Fields** and **Transformation Description** columns to see how LUSID maps your data > - Int29Analytics imports require you to add certain properties; [read more](/v1/docs/blackrock-aladdin-file-transfers#positions-and-holdings) 4. Specify the following **Integration settings**: - **Source file location**: A path in [Drive](/v1/docs/drive) starting with `/sftp` or `/LUSID-` to deliver incoming BlackRock Aladdin files for processing - For quote interfaces (INT11, INT21, INT25, INT29, INT86, INT332): - **Quote source**: A [value for](/v1/docs/recipes-locating-market-data#summary-of-fields-in-a-market-data-rule) `source` - **Quote field**: A [value for](/v1/docs/recipes-locating-market-data#summary-of-fields-in-a-market-data-rule) `field` - For transaction interfaces (INT11, INT96, INT274, INT284): - **Onboarding date**: LUSID ignores transactions prior to this date, unless overridden at the portfolio-level using the [property](/v1/docs/properties) `Portfolio/LUSIDConfig-BlackRock-Aladdin/OnboardingDate` - **Local time zone identifier**: A time zone for the data, used alongside the **Local cut time** specified in the interface selection - **Should unpack from archive**: - Tick the box if you expect your BlackRock Aladdin files to arrive zipped - **Archive file mask regex**: A regex pattern to identify the zip file in the source file location, for example `^ADX_I.*.tar.gz$` - For security mastering (INT10): - **Allow FX forwards to be non-deliverable**: - Tick this box to override Aladdin’s deliverable flag and import FX forwards as non-deliverable; this enables leg splitting in valuations - **Allow updates to core fields**: - **Never**: Only allow updates to missing instrument identifiers and properties in the `LUSID-BlackRock-Aladdin` scope - **Always**: Allow updates to any core field in the LUSID instrument definition - **Model unsupported instruments as SimpleInstrument**: - Tick this box to allow LUSID to attempt to model instruments with unmapped `<SEC_TYPE>` as [SimpleInstrument](/v1/docs/how-does-lusid-categorise-instruments-into-asset-classes), rather than logging as `ResourceFailed`; [see Appendix B for the full list of supported instruments](/v1/docs/blackrock-aladdin-file-transfers#appendix-b-instrument-coverage) - **Int10 CUSIP_ALIAS_set Identifiers**: Optionally, click **Add item** and specify the following to map a custom identifier alias to a [LUSID instrument identifier type](/v1/docs/understanding-instrument-identifiers): > [!NOTE] > Note > > If you do not specify any items, LUSID defaults to any existing configuration for loading specific identifiers in INT10 files. - **Cusip Alias Code** - **Cusip Alias Purpose** - **LUSID Instrument Identifier** - **Int10 Sets (FLOATER, IBND_DATA)**: Optionally, specify one or more sets to load into a LUSID [relational dataset](/v1/docs/how-do-i-create-a-relational-dataset-definition). The following sets are currently available: See [Appendix A](/v1/docs/blackrock-aladdin-file-transfers#appendix-a-further-information-on-aladdin-interfaces) for further details. - `FLOATER_set` - `IBND_DATA_set` - For processing analytics to the [SRS](/v1/docs/what-is-structured-result-data) (INT29), select one of the following files to process as **INT29 analytics file type**: - **NotApplicable**: Default - **PreliminaryAnalytics**: EOD analytics - **PreliminaryScenarios**: EOD scenarios - **Analytics**: Green package analytics - **Scenarios**: Green package scenarios - For trades (INT11): - **Round applicable values?**: Optionally, select **Yes** to apply midpoint rounding to the `TRD_ORIG_FACE` field in INT11 files (which maps to the transaction `units` in LUSID) - **Round to decimal places**: If rounding is enabled, specify the number of decimal places to round to - Click **Add item** and specify the following for each interface you want to process in this integration instance: *****Click to expand information on processing interface files in a particular order***** LUSID processes interface files according to: 1. The order specified in the diagram below (for relevant interfaces): ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-6G5RYFIO.png) 2. The order configured in your integration instance ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-KUYYGHHK.png) For example, if you configure an integration instance with interfaces in the order INT330 > INT21 > INT29 > INT10 > INT17, LUSID would instead process the interfaces in the order INT17 > INT10 > INT21 > INT29 > INT330. - **Interface number**: The Aladdin interface to process, see [appendix A](/v1/docs/blackrock-aladdin-file-transfers#appendix-a-further-information-on-aladdin-interfaces) - **File mask regex**: A regex pattern to specify which file name to process, for example `^filename.xml$` (`^` = starts with, `$` = ends with) - **Local cut time**: A time in `HH:mm:ss` to append to dates this integration instance processes, used alongside the **Local time zone identifier** 5. Choose whether to **Enable integration** on creation, then click **Save**. Note the **Instance ID**, which you’ll need for certain run methods. ### Step 2: Configure the portfolios to import data for [Follow these](/v1/docs/how-do-i-add-a-property-to-an-entity) steps to add the following properties to each portfolio that should receive BlackRock Aladdin data. #### Required properties for all portfolio interfaces - `Portfolio/LUSIDConfig-BlackRock-Aladdin/IsIncluded` set to `true`: Enables BlackRock Aladdin data retrieval for the portfolio - `Portfolio/LUSIDConfig-BlackRock-Aladdin/LinkedCode` set to the portfolio name in the BlackRock Aladdin data: Links the LUSID portfolio to one BlackRock Aladdin portfolio The two properties above are sufficient for INT54 (Portfolios) processing. For other interfaces, add the relevant additional property below. #### Additional properties by interface **For holdings interfaces (INT14, INT29, INT330):** - `Portfolio/LUSIDConfig-BlackRock-Aladdin/LoadHoldings` set to `true`: Enables holdings data loading **For transaction interfaces (INT11, INT96, INT274, INT284):** - `Portfolio/LUSIDConfig-BlackRock-Aladdin/LoadTransactions` set to `true`: Enables transactions data loading - Optionally, `Portfolio/LUSIDConfig-BlackRock-Aladdin/OnboardingDate` set to a particular date: LUSID ignores transactions prior to this date for the portfolio, overriding the date configured [in the integration instance](/v1/docs/blackrock-aladdin-file-transfers#step-1-create-an-integration-instance) **For ledger activity (INT274):** - `Portfolio/LUSIDConfig-BlackRock-Aladdin/LoadLedger` set to `true`: Enables ledger activity loading - `Portfolio/LUSIDConfig-BlackRock-Aladdin/LinkedFund` set to a BlackRock Aladdin FUND number: Links the LUSID ledger portfolio to a particular fund in the INT274 data ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-Q3XSCG94.png) ## Running the integration ### Automatic runs LUSID automatically processes files when they arrive in your specified **Source File Location** and match your configuration. For example, imagine you have an integration instance with the following configuration: - **Archive file mask regex**: `^ADX_I.*.tar.gz$` - **INT10 file mask regex**: `^sm.xml$` - **INT11 file mask regex**: `^transaction.xml$` BlackRock Aladdin might deliver the following to your specified location in Drive: - `ADX_I.2024040100001.tar.gz` containing: - `sm.xml` - `transaction.xml` LUSID then does the following: 1. Unzips nugget (matches the archive file mask regex) 2. Processes INT10 (matches `sm.xml` pattern) 3. Processes INT11 (matches `transaction.xml` pattern) ### Manual reruns To reprocess a file: 1. [Create a separate integration instance](/v1/docs/blackrock-aladdin-file-transfers#step-1-create-an-integration-instance) for reruns, setting the **Source File Location** to a Drive directory starting with `/LUSID-`. 2. Upload the file to your specified location. ## Monitoring and troubleshooting integration runs [See how to monitor integrations and troubleshoot general issues.](/v1/docs/setting-up-an-integration#monitoring-integration-runs) --- ### Troubleshooting #### The integration instance has run but no instruments/holdings/transactions have been created Check the portfolios you want to import data for have been decorated with the required properties and values; [see step 2](/v1/docs/blackrock-aladdin-file-transfers#step-2-configure-the-portfolios-to-import-data-for). #### Multiple securities in the BlackRock Aladdin data have matched with the same instrument in LUSID You may receive the following error message in the logs if LUSID maps two different instruments in the source data (typically INT10 Security Master) to one LUID: ```plaintext Multiple securities in the Vendor data have all matched with the same instrument in LUSID. Only one of them can be processed in a single operation, and this record has not been chosen to be processed into LUSID. ``` As this is a conflict, LUSID: - Processes one of the records with status `ResourceResolved` - Marks the other record with status `ResourceFailed` You can review the **Source Primary ID Type** and **Source Primary ID Value** [columns in the logs](/v1/docs/setting-up-an-integration#viewing-and-troubleshooting-all-runs) to track the cause of the conflict in the source data. #### INT10 ResourceFailed: `Unable to map TRSWAP ASSET_BENCHMARK to a supporting Bond or ComplexBond` You may receive the above error message in the logs if the INT10 file contains `TotalReturnSwap` instruments with the `ASSET_BENCHMARK` field referencing underlying bond instruments that are not present in the file or LUSID. LUSID cannot resolve the referenced underlying asset, and therefore cannot create a `TotalReturnSwap` instrument. #### INT10 ResourceFailed: `Core field is missing and entity cannot be constructed:  Instrument/LUSID-BlackRock-Aladdin/COUPON_FLOAT` You may receive the above error message in the logs if the fields `SM_SEC_GROUP`, `SM_SEC_TYPE` & `SEC_DESC2` indicate LUSID should create a ComplexBond instrument. [Read more on instrument coverage.](/v1/docs/blackrock-aladdin-file-transfers#appendix-b-instrument-coverage) The following pair of `ResourceFailed` and `AttributeFailed` errors for an incoming instrument in the logs indicate the instrument is missing coupon data: - **ResourceFailed**: `Reason: Core field is missing and entity cannot be constructed: Instrument/LUSID-BlackRock-Aladdin/COUPON_FLOAT. Detail: An error has occurred while attempting to parse data read from a file` - **AttributeFailed**: `One or more failures occurred.` Verify your file contains the following required **Source Field** columns (varying by fixed or floating): - `FLOATER_SET`/`FLOATER_RECORD`/`INITIAL_COUPON` - `COUPON_FIX` - `COUPON_FLOAT` #### INT29Analytics: No data returned in portfolio valuation The data LUSID uses to perform a valuation varies depending on the `quoteInterval` in your valuation [recipe](/v1/docs/what-is-structured-result-data#upserting-a-recipe-that-can-locate-data-in-the-srs) (under `resultDataKeyRule`). For example, a quoteInterval of `2D` (2 days) means LUSID can only retrieve data with an effective date within 2 days of the current date. Querying [SRS](/v1/docs/what-is-structured-result-data) data using the `Lusid.UnitResult.AtomisedResult` Luminesce provider always retrieves data using an unlimited quote interval (that is, from `0001-01-01`). You can therefore query this provider to verify that the INT29Analytics integration has run successfully. If necessary, amend the `quoteInterval` in your recipe to align with your integration run schedule, for example `1W` (1 week). ## Appendix A: Further information on Aladdin interfaces --- ### Securities and reference data #### INT10: Security master Securities from BlackRock Aladdin, including any security that: - Was traded - Is an underlying of a traded security - Was modified and ever traded Can also be configured for securities in external positions, indexes, or Galileo lists. > [!NOTE] > `FLOATER_set` and `IBND_DATA_set` data > > If your integration instance specifies one or more set selections, LUSID loads the corresponding set data into a LUSID [relational dataset](/v1/docs/how-do-i-create-a-relational-dataset-definition). The following sets are available: > > - `FLOATER`: LUSID loads the full floating coupon schedule for applicable instruments. > - Data is available under the scope `LUSID-BlackRock-Aladdin` and code `INT10_FLOATER`. > - You can query and join floater data against core instrument data using the `Lusid.RelationalDataset.LUSID-BlackRock-Aladdin.INT10_FLOATER` and `Lusid.RelationalDataset.LUSID-BlackRock-Aladdin.INT10_FLOATER.Writer` Luminesce providers. > - `IBND_DATA`: Loads the first item in the `IBND_DATA_set` for applicable instruments. > - Data is available under scope `LUSID-BlackRock-Aladdin` and code `INT10_IBND_DATA`. > > The integration automatically creates the relational dataset definition for each set if one does not already exist. #### INT15: Counterparties All counterparties in BlackRock Aladdin, modelled as Legal Entities in LUSID. #### INT17: Issuers Issuers of securities, modelled as Legal Entities in LUSID. #### INT107: Credit ratings - security master Credit ratings for traded securities or related securities, loaded into LUSID as properties on instruments. #### INT113: Strategies All valid strategies in the BlackRock Aladdin database. LUSID creates a custom data type for strategies, used as the data type for the `STRATEGYID` property associated with transactions. #### INT144: Credit ratings - issuer Credit ratings for issuers of traded securities or related securities, loaded into LUSID as properties on legal entities. --- ### Trading and transactions #### INT11: Trades Trades in active portfolios that were added, modified, or cancelled today. Trades are also available intraday for confirmed trades, as they are confirmed. LUSID creates transactions and quotes for instruments the transactions are booked against. #### INT96: New cash Cash subscriptions and redemptions at the portfolio level, loaded into LUSID as transactions. Includes all subscriptions and redemptions that today were: - Added - Updated - Cancelled Can be used to assist in cash and settlement reconciliations. #### INT243: Collateral detail Collateral detail data loaded into LUSID as [relational dataset records](/v1/docs/how-do-i-create-a-relational-dataset-definition) under the scope `LUSID-BlackRock-Aladdin` and code `CollateralDetail`. The integration creates the necessary relational dataset definition if it does not already exist. #### INT244: Collateral statement Collateral statement data loaded into LUSID as [relational dataset records](/v1/docs/how-do-i-create-a-relational-dataset-definition) under the scope `LUSID-BlackRock-Aladdin` and code `CollateralStatement`. INT244 enriches the data loaded from INT243 by joining on `STATEMENT_ID`, but can also load independently of INT243. The integration creates the necessary relational dataset definition if it does not already exist. #### INT274: Ledger activity Ledger entries loaded into LUSID as [transactions](/v1/docs/transactions). INT274 records each lifecycle event as a separate entry (unlike INT11 (Trades), which updates existing records). This makes it suitable for SFTR compliance and as-of date reporting. > [!NOTE] > Note > > You should load INT274 data into dedicated ledger portfolios, separate from your existing trade portfolios. > > We recommend naming ledger portfolios with the suffix `_Ledger`; for example, if you name an existing trade portfolio `PortfolioA`, you might name the ledger activity portfolio `PortfolioA_Ledger`. #### INT284: Cash entries Cash transactions including: - Principal - Interest - Fees - Other miscellaneous cash Does not include cash from trade settlements or capital flows (cash subscriptions and redemptions). Loaded into LUSID as transactions. > [!NOTE] > Note > > Consider using the INT274 Ledger Activity interface instead, as it uses cancel/correct methodology and contains cash from trades and subscriptions/redemptions. --- ### Positions and holdings #### INT14: Positions [Holdings](/v1/docs/holdings) in each portfolio as of EOD or SOD: - Can be reported at tax-lot level, or fund and security level - Each row shows traded and contractually settled positions - Enables you to reconcile positions from BlackRock Aladdin versus custodian or other systems LUSID supports loading INT14 at fund and security level using [SetHoldings](/v1/docs/how-do-i-manually-adjust-or-set-holdings), which replaces all current holdings in the portfolio. Can be used with INT330 (Cash Walk-Forward) to include committed cash in the portfolio. #### INT29Analytics and INT29: Positions (Analytics) Soft copy of the Green Package. The fields are determined by your needs, and can be configured to load into LUSID as: - Holdings (INT29) - Data points in the [SRS](/v1/docs/what-is-structured-result-data) (INT29Analytics) When loaded as holdings, LUSID uses [SetHoldings](/v1/docs/how-do-i-manually-adjust-or-set-holdings) to replace all current holdings in the portfolio. > [!NOTE] > Important > > For instruments types with legs that you want to import INT29Analytics data for, you must ensure you: > > - Include INT10 in your **BlackRock Aladdin interface selections** > - Add the following properties to import in your integration instance: > - `CUSIP_RECEIVE` > - `CUSIP_PAY` > > You must select one property per relevant **Property Entity Sub-Type**: > > ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-9WJUEBTG.png) #### INT330: Cash walk-forward Multi-purpose interface for cash reporting, projection, and reconciliation: - Cash reporting: View starting and ending cash positions and transactions for past date ranges - Cash projection: View starting and ending cash positions and transactions for future date ranges - Cash reconciliation: Reconcile Aladdin cash versus custodian cash (MT950s) or other systems LUSID loads committed cash from this interface as holdings using AdjustHoldings to update current holdings. This interface is typically used by those who load positions via INT14 rather than INT29. --- ### Pricing and valuations #### INT21: Preliminary prices Closing market price for each security held in production portfolios, with one price per security per Aladdin price-source hierarchy. You can configure this to include: - Accrued interest and accrual dates - Risk metrics - Yields. Prices are usually not reviewed. LUSID loads prices as [quotes](/v1/docs/market-data) and accrued interest to the [SRS](/v1/docs/what-is-structured-result-data). #### INT25: Factors Factors for securities that amortise their principal over time or apply an inflation factor. Loaded into LUSID as [quotes](/v1/docs/market-data) with a quote type of `PoolFactor`. #### INT332: Prices (selected sources) Closing market prices for selected price sources, loaded into LUSID as [quotes](/v1/docs/market-data). This interface provides prices from a configured list of sources. If a source provided no price that day, LUSID receives no record for that source. #### INT86: Economy Economic data used in the Green Package. LUSID processes spot rate data from this interface and loads it into the LUSID Quote Store as [FX rates](/v1/docs/market-data). --- ### Portfolio data and analytics #### INT54: Portfolios Active portfolios for your selected portfolio group(s), as of that day, loaded into LUSID as [properties](/v1/docs/properties) on portfolios. Shows all available attributes of each portfolio. #### INT95: NAV Net Asset Value (NAV) of each portfolio, including: - All new or updated NAVs since the previous interface run - Estimated or actual (signed off) NAV - Asset value (not including cash) You can use this data to reconcile against internal systems or custodian. LUSID loads NAV data points to the [SRS](/v1/docs/what-is-structured-result-data). #### Cashflows (bespoke export) Bespoke output file, loaded into the LUSID [SRS](/v1/docs/what-is-structured-result-data), containing cash flows for: - `INTEREST` - `SCHED_PRIN` (scheduled principal) - `UNSCHED_PRIN` (unscheduled principal) ## Appendix B: Instrument coverage Currently, you can model the following Aladdin security types as LUSID instruments: *****Click to expand list***** | `SM_SEC_GROUP` | `SM_SEC_TYPE` | `SEC_DESC2` | [LUSID instrument type](/v1/docs/supported-instruments-in-lusid) | | --- | --- | --- | --- | | `CASH` | `AGENCY` | | `Bond` | | `CASH` | `CP` | | `Bond` | | `CASH` | `TBILL` | | `Bond` | | `CASH` | `TD` | | `Bond` | | `SWAP` | `CDSWAP` | `CDS` | `CdsIndex` | | `SWAP` | `CDSWAP` | `CDX` | `CdsIndex` | | `ABS` | `ABS` | | `ComplexBond` | | `ABS` | `AGENCY` | | `ComplexBond` | | `ARM` | `POOL` | | `ComplexBond` | | `BND` | `AGENCY` | | `ComplexBond` | | `BND` | `CORP` | | `ComplexBond` | | `BND` | `GOVT` | | `ComplexBond` | | `BND` | `LOCAL` | | `ComplexBond` | | `BND` | `MUNI` | | `ComplexBond` | | `BND` | `MUNITAX` | | `ComplexBond` | | `CASH` | `CD` | | `ComplexBond` | | `CMBS` | `SENIOR` | | `ComplexBond` | | `CMBS` | `SUB` | | `ComplexBond` | | `CMO` | `AGENCY` | | `ComplexBond` | | `CMO` | `WHOLE` | | `ComplexBond` | | `LOAN` | `TERM` | | `ComplexBond` | | `MBS` | `POOL` | | `ComplexBond` | | `MBS` | `TBA` | | `ComplexBond` | | `EQUITY` | `EQUITY` | | `Equity` | | `EQUITY` | `PFD` | | `Equity` | | `EQUITY` | `WARRANT` | | `EquityOption` | | `OPTION` | `EQUITY` | | `EquityOption` | | `SWAP` | `TRSWAP` | `EQ` | `EquitySwap` | | `OPTION` | `FUTURE` | | `ExchangeTradedOption` | | `FUTURE` | `FIN` | | `Future` | | `FUTURE` | `INDEX` | | `Future` | | `FX` | `CSWAP` | | `FxForward` | | `FX` | `FWRD` | | `FxForward` | | `FX` | `SPOT` | | `FxForward` | | `OPTION` | `CUROTC` | | `FxOption` | | `IBND` | `AGENCY` | | `InflationLinkedBond` | | `IBND` | `CORP` | | `InflationLinkedBond` | | `IBND` | `GOVT` | | `InflationLinkedBond` | | `SWAP` | `SWAP` | `IFS` | `InflationSwap` | | `SWAP` | `SWAP` | `LPI` | `InflationSwap` | | `SWAP` | `CSWAP` | | `InterestRateSwap` | | `SWAP` | `SWAP` | `ASP` | `InterestRateSwap` | | `SWAP` | `SWAP` | `BASIS` | `InterestRateSwap` | | `SWAP` | `SWAP` | `IRS` | `InterestRateSwap` | | `SWAP` | `SWAP` | `OIS` | `InterestRateSwap` | | `SWAP` | `SWAP` | `ZERO` | `InterestRateSwap` | | `SYNTH` | `SWAPTION` | | `InterestRateSwaption` | | `CASH` | `REP` | | `Repo` | | `CASH` | `RRP` | | `Repo` | | `CASH` | `TPREPO` | | `Repo` | | `CASH` | `CASH` | | `SimpleInstrument` | | `CASH` | `COLLATERAL` | | `SimpleInstrument` | | `CASH` | `TFN` | | `SimpleInstrument` | | `FUND` | `CLOSED_END` | | `SimpleInstrument` | | `FUND` | `OPEN_END` | | `SimpleInstrument` | | `FUND` | `STIF` | | `SimpleInstrument` | | `OPTION` | `OTC` | | `SimpleInstrument` | | `SWAP` | `TRSWAP` | `FI` | `TotalReturnSwap*` | | `SYNTH` | `CAP` | | `Auxiliary securities` | | `SYNTH` | `INDEX` | | `Auxiliary securities` | *This is a basic implementation, and is not suitable for valuation purposes. `TotalReturnSwap` instruments must be created with the underlying as *inline* and not a reference to a separately mastered bond. > [!NOTE] > Note > > LUSID attempts to model any data which is not included in the table above as a `SimpleInstrument` if your integration instance has **Model unsupported instruments as SimpleInstrument** [enabled](/v1/docs/blackrock-aladdin-file-transfers#step-1-create-an-integration-instance).