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).

reports_regulatory_reports.png

The table contains the following fields:

NameDescription
ReportName of the reference file.
StatusStatus of the latest generation of the reference file.
StartedDate and time the latest generation was started.
ActionsThe Generate and Download buttons.

Generation statuses:

NameDescription
InitThe reference file has not been generated yet.
In progressThe reference file is being generated.
SuccessThe reference file has been generated, the files are available for download.
FailedAn 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 UPI field 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 the FX category - only Currency;
  • for a CFD on an Index, the Underlying instrument must be set;
  • for a CFD on an Equity or Privileged equity, the Underlying instrument with a filled ISIN must be set;
  • for a CFD on a Commodity, the Underlying instrument must be set, and the tenor must have the Expiration date.

Instruments of other categories are always included in errors.csv:

CategoryError 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
FUstrikePriceNotationType is mandatory for contract type 'FUTR' but no value is available
OPstrikePriceNotationType is mandatory for contract type 'OPTN' but no value is available
CASH and othersInvalid 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 Type and Asset Class are determined by the instrument category and the type of its base asset. The Asset type and Contract type fields of the instrument card are not used in the reference file.
NameDescription
Row NameAlways instrument.
Record IDNot filled.
Parent Record IDNot filled.
Symbol NameInstrument ID in the system.
Database Instrument NameInstrument Ticker.
Base CurrencyBase asset code if it is a Currency or Crypto, otherwise - the quoted asset code. The code must consist of three characters.
Quote CurrencyQuoted asset code.
Instrument DescriptionFor 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 TypeAlways CFDS.
ClearedN for CFD, Y for FX.
Clearing ObligationAlways UKWN.
ConfirmedAlways ECNF.
Contract SizeInstrument Lot size with 19 decimal places, e.g. 1.0000000000000000000.
Asset ClassBy the base asset type: CURR - Currency; EQUI - Equity, Privileged equity, Index, ETF, GDR, ADR, Alternative investment fund; COMM - Commodity, Crypto.
Derivative based on crypto-assets1 if the base asset is Crypto, otherwise 0.
Underlying Identification typeX for a CFD on an Index, I for a CFD on an Equity or Privileged equity. Not filled for others.
Underlying IdentificationFor type I - ISIN of the underlying instrument. Not filled for others.
Name of the underlying indexFor a CFD on an Index - Code of the underlying instrument. Not filled for others.
Identifier of the basket’s constituentsNot filled.
Indicator of the Underlying IndexNot filled.
Custom basket codeNot filled.
Venue Of ExecutionAlways XXXX.
Product ClassificationNot filled.
ISINNot filled.
Unique product identifierValue of the instrument UPI field.
Mapped Unique product identifierNot filled.
Product IDNot filled.
Reference RateNot filled.
Return or Payout TriggerNot filled.
Valuation Method or TriggerNot filled.
Proprietary Index IDNot filled.
Underlying asset typeNot filled.
Master Agreement TypeAlways BIAG.
Master Agreement VersionNot filled.
Other Master Agreement TypeNot filled.
Delivery TypeAlways C.
Price Notation TypeAlways M.
Base productCOMM for a CFD on a Commodity. Not filled for others.
Sub-productCOMM for a CFD on a Commodity. Not filled for others.
Further sub-productCOMM for a CFD on a Commodity. Not filled for others.
Strike Price Notation TypeNot filled.
Collateral RequirementNot filled.
Expiration DateNot filled.
Delivery point or zoneNot filled.
Interconnection PointNot filled.
Load typeNot filled.
Delivery interval start timeNot filled.
Delivery interval end timeNot filled.
Delivery start dateNot filled.
Delivery end dateNot filled.
DurationNot filled.
Days of the weekNot filled.
Delivery capacityNot filled.
Quantity UnitNot filled.
Price/time interval quantityNot filled.
Currency of the price/time interval quantityNot filled.
Option styleNot filled.
Strike price currency/currency pairNot filled.
Option premium currencyNot filled.
Maturity date of the underlyingNot filled.
SeniorityNot filled.
Reference entityNot filled.
SeriesNot filled.
VersionNot filled.
Index factorNot filled.
TrancheNot filled.
CDS index attachment pointNot filled.
CDS index detachment pointNot filled.

The errors.csv file

The file contains a row for each failed check, so one instrument may have several rows.

NameDescription
Instrument IDInstrument ID in the system.
CellThe reference file field on which the check failed, e.g. isin, upi, contractType.
ErrorError text in English.
Didn't find what you were looking for? Contact to support@unity.finance. We will be happy to help 24/7