Help Center
Our products knowledge base for customers
Regulatory Reports
Regulatory Reports
The report is designed to generate the broker's regulatory reference files. A reference file is generated in the background and downloaded as CSV files.
Currently, one reference file is available in the report - EMIR instrument reference: the broker's instrument reference for EMIR reporting.
To view and generate the reference file, the user needs the Broker management profile permission (for more information, see the Roles article).
![]()
The table contains the following fields:
| Name | Description |
|---|---|
| Report | Name of the reference file. |
| Status | Status of the latest generation of the reference file. |
| Started | Date and time the latest generation was started. |
| Actions | The Generate and Download buttons. |
Generation statuses:
| Name | Description |
|---|---|
| Init | The reference file has not been generated yet. |
| In progress | The reference file is being generated. |
| Success | The reference file has been generated, the files are available for download. |
| Failed | An error occurred during generation. |
The Generate button starts generating the reference file. After clicking it, the Report generation started notification is displayed and the status changes to In progress. The status is updated without reloading the page. While the reference file is being generated, the Generate button is unavailable.
Each new generation replaces the files of the previous one. If generation ends with the Failed status, the files of the latest successful generation remain available for download.
The Download button downloads two files: instruments.csv and errors.csv. The button is unavailable until the reference file has been successfully generated at least once.
EMIR instrument reference
When the reference file is generated, all of the broker's instruments are checked, each tenor in a separate row. An instrument that passes all checks is included in the instruments.csv file. An instrument that fails at least one check is not included in instruments.csv: its errors are written to the errors.csv file.
Both files are in CSV format, the first row contains the column names.
Which instruments are included in the reference file
Under the current rules, only instruments of the CFD and FX categories can pass the checks. For them:
- the
UPIfield must be filled in the instrument card; - the quoted asset code must consist of three characters;
- the base asset type must be one of:
Currency,Crypto,Commodity,Equity,Privileged equity,Index,ETF,GDR,ADR,Alternative investment fund. For theFXcategory - onlyCurrency; - for a CFD on an
Index, theUnderlying instrumentmust be set; - for a CFD on an
EquityorPrivileged equity, theUnderlying instrumentwith a filledISINmust be set; - for a CFD on a
Commodity, theUnderlying instrumentmust be set, and the tenor must have theExpirationdate.
Instruments of other categories are always included in errors.csv:
| Category | Error in errors.csv |
|---|---|
| EQ | 'EQUITY' is not a valid Contract Type, as well as the cleared, masterAgreementType, deliveryType errors |
| BO | 'BOND' is not a valid Contract Type, as well as the cleared, masterAgreementType, deliveryType errors |
| FU | strikePriceNotationType is mandatory for contract type 'FUTR' but no value is available |
| OP | strikePriceNotationType is mandatory for contract type 'OPTN' but no value is available |
| CASH and others | Invalid category <category> |
The instruments.csv file
The file contains 68 columns. Below is how they are filled for instruments included in the reference file. Columns marked Not filled are always empty in the file.
Please note!Contract TypeandAsset Classare determined by the instrument category and the type of its base asset. TheAsset typeandContract typefields of the instrument card are not used in the reference file.
| Name | Description |
|---|---|
| Row Name | Always instrument. |
| Record ID | Not filled. |
| Parent Record ID | Not filled. |
| Symbol Name | Instrument ID in the system. |
| Database Instrument Name | Instrument Ticker. |
| Base Currency | Base asset code if it is a Currency or Crypto, otherwise - the quoted asset code. The code must consist of three characters. |
| Quote Currency | Quoted asset code. |
| Instrument Description | For CFD - CFD on <Code>. For a CFD on an Index, (Futures) is added, for a CFD on a Commodity - - <expiration date DD/MM/YYYY> (Som - Futures) if the underlying instrument tenor denotes a futures month, and - <expiration date DD/MM/YYYY> (Non - Futures) if it does not. For FX - Spot FX <Code>. |
| Contract Type | Always CFDS. |
| Cleared | N for CFD, Y for FX. |
| Clearing Obligation | Always UKWN. |
| Confirmed | Always ECNF. |
| Contract Size | Instrument Lot size with 19 decimal places, e.g. 1.0000000000000000000. |
| Asset Class | By the base asset type: CURR - Currency; EQUI - Equity, Privileged equity, Index, ETF, GDR, ADR, Alternative investment fund; COMM - Commodity, Crypto. |
| Derivative based on crypto-assets | 1 if the base asset is Crypto, otherwise 0. |
| Underlying Identification type | X for a CFD on an Index, I for a CFD on an Equity or Privileged equity. Not filled for others. |
| Underlying Identification | For type I - ISIN of the underlying instrument. Not filled for others. |
| Name of the underlying index | For a CFD on an Index - Code of the underlying instrument. Not filled for others. |
| Identifier of the basket’s constituents | Not filled. |
| Indicator of the Underlying Index | Not filled. |
| Custom basket code | Not filled. |
| Venue Of Execution | Always XXXX. |
| Product Classification | Not filled. |
| ISIN | Not filled. |
| Unique product identifier | Value of the instrument UPI field. |
| Mapped Unique product identifier | Not filled. |
| Product ID | Not filled. |
| Reference Rate | Not filled. |
| Return or Payout Trigger | Not filled. |
| Valuation Method or Trigger | Not filled. |
| Proprietary Index ID | Not filled. |
| Underlying asset type | Not filled. |
| Master Agreement Type | Always BIAG. |
| Master Agreement Version | Not filled. |
| Other Master Agreement Type | Not filled. |
| Delivery Type | Always C. |
| Price Notation Type | Always M. |
| Base product | COMM for a CFD on a Commodity. Not filled for others. |
| Sub-product | COMM for a CFD on a Commodity. Not filled for others. |
| Further sub-product | COMM for a CFD on a Commodity. Not filled for others. |
| Strike Price Notation Type | Not filled. |
| Collateral Requirement | Not filled. |
| Expiration Date | Not filled. |
| Delivery point or zone | Not filled. |
| Interconnection Point | Not filled. |
| Load type | Not filled. |
| Delivery interval start time | Not filled. |
| Delivery interval end time | Not filled. |
| Delivery start date | Not filled. |
| Delivery end date | Not filled. |
| Duration | Not filled. |
| Days of the week | Not filled. |
| Delivery capacity | Not filled. |
| Quantity Unit | Not filled. |
| Price/time interval quantity | Not filled. |
| Currency of the price/time interval quantity | Not filled. |
| Option style | Not filled. |
| Strike price currency/currency pair | Not filled. |
| Option premium currency | Not filled. |
| Maturity date of the underlying | Not filled. |
| Seniority | Not filled. |
| Reference entity | Not filled. |
| Series | Not filled. |
| Version | Not filled. |
| Index factor | Not filled. |
| Tranche | Not filled. |
| CDS index attachment point | Not filled. |
| CDS index detachment point | Not filled. |
The errors.csv file
The file contains a row for each failed check, so one instrument may have several rows.
| Name | Description |
|---|---|
| Instrument ID | Instrument ID in the system. |
| Cell | The reference file field on which the check failed, e.g. isin, upi, contractType. |
| Error | Error text in English. |