--- title: "Quantifi" slug: "quantifi" updated: 2026-07-23T13:37:12Z published: 2026-07-23T13:37:12Z canonical: "support.lusid.com/quantifi" --- > ## 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. # Quantifi FINBOURNE’s integration with Quantifi lets you bring your trade data from across credit, rates, FX, and commodities markets straight into LUSID. > [!NOTE] > Prerequisites > > Before getting started, ensure you have: > > - [x] An active commercial agreement with Quantifi > - [x] Quantifi `Trades` and `TradeCashflows` files delivered to the relevant location (SFTP or LUSID Drive) > - [x] [Contacted your FINBOURNE representative](https://www.finbourne.com/contact) to enable the integration in your LUSID domain ## Supported data types and methods LUSID can ingest the following from Quantifi: - `Trades` files to create [transactions](/v1/docs/transactions) and master new [instruments](/v1/docs/instruments) where they do not already exist - `TradeCashflows` files to update the cashflows on transactions you’ve previously loaded Once configured, LUSID picks up and processes new files as they arrive in Drive. Currently, the integration supports the following trade types: - ABS ([ComplexBond](/v1/docs/modelling-complex-bonds-in-lusid)) - [Bond](/v1/docs/modelling-fixed-rate-vanilla-bonds-in-lusid) - Bond [Future](/v1/docs/modelling-exchange-traded-futures-and-options-in-lusid) - [CdsIndex](/v1/docs/modelling-cds-index-instruments-in-lusid) - [CreditDefaultSwap](/v1/docs/modelling-cds-index-instruments-in-lusid) - Equity [Future](/v1/docs/modelling-exchange-traded-futures-and-options-in-lusid) - Fee - [FixedToFloatBond](/v1/docs/modelling-complex-bonds-in-lusid) - [FxForward](/v1/docs/modelling-fxforwards-in-lusid) - [FxFuture](/v1/docs/modelling-exchange-traded-futures-and-options-in-lusid) - [FxSpot](/v1/docs/how-do-i-load-fx-spot-rates-into-the-quote-store) - [FxSwap](/v1/docs/modelling-fx-swaps-in-lusid) - [RateFuture](/v1/docs/modelling-exchange-traded-futures-and-options-in-lusid) - RateOption (`InterestRateSwaption`) - [Repo](/v1/docs/modelling-repurchase-agreements-in-lusid) - [Stock](/v1/docs/modelling-equities-in-lusid) - [StockOption](/v1/docs/modelling-equity-options-in-lusid) - [Swap](/v1/docs/modelling-equity-swaps-in-lusid) - `TotalReturnSwap` The integration can currently master the following instrument types: - [CdsIndex](/v1/docs/modelling-cds-index-instruments-in-lusid) - [CreditDefaultSwap](/v1/docs/modelling-cds-index-instruments-in-lusid) - [FxForward](/v1/docs/modelling-fxforwards-in-lusid) - [FxSwap](/v1/docs/modelling-fx-swaps-in-lusid) - [EquityOption](/v1/docs/modelling-equity-options-in-lusid) - [Swap](/v1/docs/modelling-equity-swaps-in-lusid) - `TotalReturnSwap` Instruments of other types must already exist in LUSID. ## Setting up the integration ### Step 1: Create an integration instance An integration instance is a configuration of data points to import from Quantifi. 1. Navigate to **Integrations > Dashboard**. 2. Select **Create instance** and choose **Quantifi**. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-8SL33EPE.png) 3. Specify the following: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-9V7FI6G3.png) - **Name**: A friendly name for this integration instance - **Description**: A detailed description of the instance 4. Click **Edit imported properties > Add properties** and choose which Quantifi data fields you want to import as properties on the resulting transactions or instruments. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-W9M9UK23.png) > [!NOTE] > Note > > - To import `Tags` on Trades (and Products nested within a Trade), select the `Tags` property in the **Add properties** screen. This imports the full `Tags` object as a property on transactions and instruments (where relevant), alongside the individual tag values. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-ORMM811Y.png) > - You can select the **View imported fields** button and inspect the **Source Fields** and **Transformation Description** columns to see how LUSID maps Quantifi data onto LUSID entities. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-GUY5Q2A7.png) 5. Specify the following in the **Integration settings** tab: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image-Y3D5EFPO.png) - **Source file location**: The path in Drive, starting with `/sftp` or `/LUSID-`, where Quantifi will deliver your files - **Local time zone identifier**: Used alongside **Local Cut Time** to attach a time to date fields - **Quantifi file selections**: - **Quantifi file type**: `Trades` or `TradeCashflows` - **File mask regex**: A regex pattern to identify which file name to process, for example `^Trades_LUSID_.*\.xml$` (`^` = starts with, `$` = ends with) - **Local cut time**: Used alongside **Local time zone identifier** to attach a time to date fields - **Round applicable values?**: Optionally, select `Yes` to apply midpoint rounding to applicable fields and specify the number of decimal places to round to 6. Select the **Enable integration** checkbox in the **Execution settings** tab. 7. Click **Save** to create the integration instance. ### Step 2: Configure the portfolios to import data for [Follow these steps](/v1/docs/how-do-i-add-a-property-to-an-entity) to add the following properties to each transaction portfolio that should receive Quantifi data. | Property key | Value | Description | | --- | --- | --- | | `Portfolio/LUSIDConfig-Quantifi/IsIncluded` | `true` | Enables Quantifi data retrieval for the portfolio | | `Portfolio/LUSIDConfig-Quantifi/LinkedCode` | `BookingEntity.LegalEntity.Name` from the Quantifi file | Links the LUSID portfolio to a Quantifi trade’s booking entity | | `Portfolio/LUSIDConfig-Quantifi/LoadTransactions` | `true` or `false` | Enables transactions data loading for the portfolio | ## Running the integration The integration runs automatically each time a matching file arrives in the specified source path. [See how to run the integration manually.](/v1/docs/setting-up-an-integration#running-an-integration) ## Monitoring and troubleshooting integration runs [See how to monitor integrations and troubleshoot general issues.](/v1/docs/setting-up-an-integration#monitoring-integration-runs) ## Appendix: Quantifi file specifications ### Portfolio code The integration takes the portfolio code for a transaction from `BookingEntity.LegalEntity.Name`, which you can specify in the [LinkedCode property](/v1/docs/quantifi#step-3-select-the-instruments-to-import-data-for) to link trades to a LUSID portfolio: ### Unique instrument ID The unique identifier for an instrument in the Quantifi `Trades` file is the `Name` field nested inside the `Product` element. LUSID maps this to the `QuantifiInstrumentId` identifier. For example: ```xml                        FxForward00123             ``` For the example above, LUSID uses the `QuantifiInstrumentId` value `FxForward00123` to identify this instrument.. ### Trade ID The `TradeId` field uniquely identifies Quantifi trade cashflows; LUSID uses this value to match each trade cashflow to an existing transaction previously loaded from a `Trades` file. For example: ```xml                        FxForward00123                20220314    GBP    -200000    1234567890    2023-11-16T05:40:24.0000000Z    UpfrontPayment ```