SUP 17 Annex 1 1Minimum content of a transaction report
List of fields for reporting purposes2
[Note: This table includes information required under MiFID Article 25(4) and contains additional FSA requirements permitted under Articles 13(3) and (4) of the MiFID Regulation]2
Where appropriate, firms should complete these fields in the formats described, or these formats must be contained in the fields that their approved reporting mechanism will use when sending a transaction report to the FSA on behalf of a firm.2
2Field Identifier |
Description |
||
EU |
1. Reporting Firm Identification |
A unique code to identify the firm which executed the transaction. |
|
2G |
This code should be the FSA reference number of the firm or the Swift Bank Identifier Code (BIC). |
||
2EU |
2. Trading Day |
The trading day on which the transaction was executed. |
|
2EU |
3. Trading Time |
The time at which the transaction was executed, reported in London local time. |
|
2G |
The time should be specified in hours, minutes and seconds (hhmmss). Where it is not possible to input seconds, '00' may be entered in this field. |
||
2EU |
4. Buy/Sell Indicator |
Identifies whether the transaction was a buy or sell from the perspective of the reporting MiFID investment firm. |
|
2EU |
5. Trading Capacity |
Identifies whether the firm executed the transaction |
|
- |
on its own account (either on its own behalf or on behalf of a client) (that is as principal); |
||
- |
for the account and on behalf of a client (that is as agent); |
||
- |
in an agency cross capacity (that is where the firm has acted as agent for both the selling and the buying counterparties) where the firm has chosen to submit a single report to the FSA representing both of these transactions; |
||
2G |
Where a firm has executed a transaction in an agency cross capacity, it may submit two reports rather than a single report, in which case this field should indicate that the firm is acting on behalf of a client. |
||
EU |
- |
in a principal cross capacity (that is where the firm has acted simultaneously for two counterparties as principal in a single product at the same price and quantity) where the firm has chosen to submit a single report to the FSA representing both of these transactions. |
|
2G |
|
Where a firm has executed a transaction in a principal cross capacity, and prefers to submit two reports rather than a single report, this field should indicate that the firm is acting on its own account. |
|
2EU |
6. Instrument Identification |
This shall consist of: |
|
- |
a unique code, decided by the FSA, identifying the financial instrument which is the subject of the transaction; |
||
2G |
The unique code should be an ISO 6166 ISIN. This code must always be used for, but is not limited to, reporting transactions in warrants. |
||
2EU |
- |
or, if the financial instrument in question does not have a unique identification code, the report must include the name of the instrument or, in the case of a derivative contract; the characteristics of the derivative. |
|
2G |
The FSA considers that where the financial instrument in question (which includes derivatives) is admitted to trading on a market where the ISO 6166 ISIN is not the industry method of identification, it will be sufficient to insert in this field the code assigned to the instrument by that market. |
||
2EU |
- |
or, in the case of an OTC derivative, the characteristics of the OTC derivative. |
|
2G |
Where an OTC derivative is the subject of the transaction a full description of the OTC derivative should be provided. |
||
2EU |
7. Instrument code type |
The code type used to report the instrument. |
|
2G |
Where the subject of the transaction is a financial instrument admitted to trading on a market this field should indicate whether that financial instrument has been identified using an ISO 6166 ISIN or, where the ISIN is not the industry method of identification for that market, a code assigned to that financial instrument by that market. |
||
2EU |
8. Underlying Instrument Identification |
The instrument identification applicable to the security that is the underlying asset in a derivative contract as well as the transferable security included within article 4(1)(18(c)) of MiFID. |
|
2G |
This field is only mandatory when the transaction involves an OTC derivative and the underlying is a single equity or single debt financial instrument admitted to trading on a regulated market or prescribed market. |
||
2EU |
9. Underlying instrument identification code type |
The code type used to report the underlying instrument. |
|
2G |
Firms do not need to complete this field since the FSA already has access to this information. |
||
2EU |
10. Instrument Type |
The harmonised classification of the financial instrument that is the subject of the transaction. |
|
2G |
This field is only mandatory when the transaction involves an OTC derivative or a financial instrument admitted to trading on a market where the ISIN is not the industry method of identification. This field must be used to indicate the instrument type of the underlying financial instrument, e.g. equity, bond, index, or other. |
||
2EU |
11. Maturity Date |
The maturity date of a bond or other form of securitized debt, or the exercise date / maturity date of a derivative contract. |
|
2G |
This field is only mandatory when the transaction involves an OTC derivative or a financial instrument admitted to trading on a market where the ISIN is not the industry method of identification. |
||
2EU |
12. Derivative Type |
The harmonised description of the derivative type. |
|
2G |
This field is only mandatory when the transaction involves an OTC derivative or a financial instrument admitted to trading on a market where the ISIN is not the industry method of identification, and must indicate the derivative type, e.g. option, future, contract for difference, warrant, spreadbet, credit default swap or other swap. |
||
2EU |
13. Put/Call |
Specification whether an option or any other financial instrument is a put or call. |
|
2G |
This field is only mandatory when (i) the transaction involves an OTC derivative or a financial instrument admitted to trading on a market where the ISIN is not the industry method of identification; and (ii) the derivative type is option or warrant. |
||
2EU |
14. Strike Price |
The strike price of an option or other financial instrument. |
|
2G |
This field is only mandatory when (i) the transaction involves an OTC derivative or a financial instrument admitted to trading on a market where the ISIN is not the industry method of identification; and (ii) the derivative type is option or warrant. |
||
2EU |
15. Price Multiplier |
The number of units of the financial instrument in question which are contained in a trading lot; for example, the number of derivatives or securities represented by one contract. |
|
2G |
This field is only mandatory where the transaction involves an OTC derivative. |
||
2EU |
16. Unit Price |
The price per security or derivative contract excluding commission and (where relevant) accrued interest. In the case of a debt instrument, the price may be expressed either in terms of currency or as a percentage. |
|
2EU |
17. Price Notation |
The currency in which the price is expressed. If, in the case of a bond or other form of securitized debt, the price is expressed as a percentage, that percentage shall be included. |
|
2G |
The ISO 4217 currency code must be used. The major currency must be used (e.g. pounds rather than pence). If the price is expressed as a percentage of nominal value then the ISO 4217 currency code of the nominal value must be used. |
||
2EU |
18. Quantity |
The number of units of the financial instruments, the nominal value of bonds, or the number of derivative contracts included in the transaction. |
|
2EU |
19. Quantity notation |
An indication as to whether the quantity is the number of units of financial instruments, the nominal value of bonds, or the number of derivative contracts. |
|
2G |
Firms do not need to complete this field since the FSA already has access to this information. |
||
2EU |
20. Counterparty |
Identification of the counterparty to the transaction. That identification shall consist of: |
|
- |
where the counterparty is a MiFID investment firm, a unique code for that firm, to be determined by the FSA; or |
||
- |
where the counterparty is a regulated market or MTF or an entity acting as its central counterparty, the unique harmonised identification code for that market, MTF or entity acting as central counterparty, as specified in the list published by the competent authority of the home Member State of that entity in accordance with Article 13(2). |
||
2G |
The FSA has determined that where an FSA reference number or a Swift Bank Identification Code (BIC) exists for the counterparty, one of these codes must be used, or in the case that a counterparty has neither an FSA reference number or a BIC, a unique internal code allocated by the reporting firm must be used and that unique internal code must be used consistently across all instrument types and platforms for that counterparty. |
||
2EU |
21. Venue Identification |
Identification of the venue where the transaction was executed. That identification shall consist in: |
|
- |
where the venue is a trading venue: its unique harmonised identification code, |
||
2G |
Where the venue is a regulated market, prescribed market or an MTF (or, where appropriate, an equivalent venue outside the EEA), the four character Swift Market Identifier Code ISO 10383 must be used. However, where the venue has been identified as a systematic internaliser, a Swift Bank Identification Code (BIC) should be used. |
||
2EU |
- |
where the transaction is made off market or the subject of the transaction is an OTC derivative this should be made clear. |
|
2EU |
22. Transaction Reference Number |
A unique identification number for the transaction provided by the MiFID investment firm or a third party reporting on its behalf |
|
2EU |
23. Cancellation Flag |
An indication as to whether the transaction was cancelled. |
|
2EU |
24. Customer/Client Identification |
This field contains the identification of the client or customer on whose behalf the reporting firm was acting. |
|
2G |
For agency transactions a customer/client identifier is required to identify the client on whose behalf the transaction has been conducted. Where an FSA reference number or a Swift Bank Identification Code (BIC) exists, one of these codes must be used or, in the case that a customer/client has neither an FSA reference number or a BIC, a unique internal code allocated by the reporting firm must be used and that unique internal code must be used consistently across all instrument types and platforms for that counterparty. |
||
2EU |
25. Any other fields |
Any other mandatory fields required by the reporting system. |
|