--- title: "Configuring Copp Clark to import calendars using the Integrations dashboard" slug: "configuring-copp-clark-to-import-calendars-using-the-integrations-dashboard" updated: 2026-06-30T14:17:37Z published: 2026-06-30T14:17:37Z canonical: "support.lusid.com/configuring-copp-clark-to-import-calendars-using-the-integrations-dashboard" --- > ## 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. # Configuring Copp Clark to import calendars using the Integrations dashboard The Copp Clark integration allows you to set up one or more configurable instances that run in your LUSID domain to provide you with the latest market holiday data. - On Day 1, you *must* configure an instance of the Copp Clark integration to import at least one calendar, and ensure you enable the instance. - Subsequently, you *can* reconfigure the instance or create more instances to import different calendar types and calendars at different times. ## Configuring a Copp Clark instance You can set up instances of the Copp Clark integration to: - Import Copp Clark calendar types, such as Payment Systems, Financial Centres, Exchange Trading and Exchange Settlement, one calendar type per instance. - Import only a subset of calendars within these calendar types, such as AUD, GBP and USD. To do this: 1. Sign into the [LUSID web app](https://www.lusid.com/app) using the credentials of a LUSID administrator. 2. From the top left menu, select **Integrations > Dashboard**. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(317).png) 3. Select **Create instance** and choose **Copp Clark**. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/9aaf9179-f8fd-4b25-9dc8-db902e01dfce.png) 4. Under the **Integration settings** tab, specify the following: The following table provides a guide for each calendar type: | **Calendar type** | Description | **Accepted filter values** | **Imported qualified calendar code** | | --- | --- | --- | --- | | Currencies | Currency holidays affecting FX and money market settlements | ISO codes for required currencies e.g. `AUD`, `GBP`, `USD` | `<ISO>__C` | | Payment Systems | Payment system holidays | `<ISO>__P` | | Exchange Trading | Trading holidays for global exchanges | ISO Market Identifier Code for required exchanges e.g. `XASX,XLON,XNYS,XSTU` | `<ISOMIC>__T` | | Exchange Settlement | Settlement holidays for global exchanges | `<ISOMIC>__S` | | Financial Centres | Bank holidays for major financial centres (affecting retail and commercial banks) | LOCODEs or FpMLs for required countries/cities separated with `/`, `-`, `_` or nothing, e.g. `AU/SYD`, `GB-LON`, `USNYC`, `KR_SEL` > **Note:** Coverage for FpML is smaller than coverage for LOCODE. We recommend including LOCODE if you want to be sure all business centres are covered. | `<LOCODE>__B` | > [!NOTE] > For more information on how holidays are defined, [see the Copp Clark support documentation](https://www.coppclark.com/support.html). For example, we can choose the **Calendar type** `Currencies` and add `AUD`, `GBP` and `USD` to the **Currency filter** to request the instance only imports data for the AUD, GBP and USD Currency FX Markets: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/32a298a8-4d1b-4ac0-8938-631961439eba.png) - A **Name** to identify the instance. - A **Description** for the instance. - A **Calendar type** to determine which type of market holiday data to load into your domain. - The relevant filter values to define which market holiday data to load into your domain. - Whether the calendar codes should be *qualified* or *unqualified*, that is, suffixed with the calendar type the data comes from. We recommend importing *qualified* calendar codes; this generally means you do *not* need to tick the box to import to *unqualified* calendar codes. [Learn more on qualified and unqualified calendar codes.](/v1/docs/configuring-horizon-copp-clark-to-import-calendars-using-the-integrations-dashboard#appendix-a-qualified-and-unqualified-calendar-codes) 5. Under the **Execution settings** tab, specify a [cron expression](https://www.quartz-scheduler.net/documentation/quartz-3.x/tutorial/crontrigger.html#introduction) and timezone to determine the schedule for the data load. You can also choose whether to enable the instance to run on schedule as soon as it is created, or to pause the instance and manually enable it later on. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/7b9e1bcb-17a8-4812-b4c2-66f50112f8f1.png) 6. Click **Create** to confirm the new instance. Once created, the latest Copp Clark data for the specified calendars will be loaded into LUSID at the next scheduled time. Once you create an instance, you can view, update, enable/disable or immediately trigger a data load for the instance via the **Integrations** dashboard: ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/f4c26c89-728e-42fa-9022-d97a3d07fb0a.png) Note the **Instance ID**, which you can use to monitor runs of the instance. ## Monitoring Copp Clark runs and troubleshooting failures You can monitor the status and configuration of the latest run of a Copp Clark instance by navigating to **Jobs & Scheduling > Data Feed Monitoring** from the top left menu in the [LUSID web app](https://www.lusid.com/app): ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/0c73369e-2675-4d08-97d1-7b7e9299a2fb.png) The **Rows processed** column tells you the number of market holiday dates a run attempted to import data for and how many completed successfully, were ignored, or failed. You can click on the **View** icon to see more details on the latest run in the **Run Information** screen, or click the **Process name** to view previous runs of the instance. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/5e94c8ae-0029-4b5e-83d4-0cb26e65bdaa.png) If the **Rows processed** column on the **Data Feed Monitoring** dashboard shows one or more rows were ignored or errored, the run creates an output file in [Drive](/v1/docs/drive) that provides more details, one ‘Warning’ file for ignored rows and one file for errored rows. To view an output file, go to the **Files** tab in the **Run Information** screen and click on the hyperlink in the **File Name** column; this takes you to the file location in Drive. ## Appendix A: Qualified and unqualified calendar codes Some calendar types take in the same identifiers: - `Currencies` and `Payment Systems` both use ISO codes and *could* import two calendars with the same code, e.g. `AUD`. - `Exchange Settlement` and `Exchange Trading` both use ISO MICs and *could* import two calendars with the same code, e.g. `XASX` To help you know exactly which type of calendar data you are using, each imported calendar code is *qualified* (that is, suffixed) with a letter that identifies which calendar type the data comes from. The qualifying letter for each calendar is: | **Calendar type value** | **Code suffix** | **Example** | | --- | --- | --- | | `Currencies` | `__C` | `AUD__C` | | `PaymentSystems` | `__P` | `AUD__P` | | `FinancialCentres` | `__B` | `AU/SYD__B` | | `ExchangeTrading` | `__T` | `XASX__T` | | `ExchangeSettlement` | `__S` | `XASX__S` | We recommend using *qualified* calendars to avoid confusion with your dataset, but you can choose to import your market holiday data *unqualified* by ticking the **Import to unqualified** box when creating an instance. This option imports two of each calendar with one qualified and one unqualified code, for example `<ISO>__C` and `<ISO>`.