CMVM
skip
Language
pageBackground
Legislation

Instruction No. 2/2007


Instruction No. 2/2007
Transaction Reporting for Financial Instruments
Admitted to Trading on a Regulated Market


(Repeals Instruction No. 1/2005)


 

Article 25 of Directive 2004/39/EC of the European Parliament and of the Council of 21 April 2004 on markets in financial instruments (DMIF) amending Council Directives 85/611/EEC and 93/6/EEC and Directive 200/12/EC of the European Parliament and of the Council and repealing Council Directive 93/22/EEC, requires the reporting from the relevant authorities on all transactions in financial instruments admitted to trading on a regulated market domiciled or operating in an EU member state.  The purpose of this requirement is to ensure that financial intermediaries act in an honest, impartial and professional manner in the best interests of the client and in tandem, promote and safeguard the integrity and transparency of the markets.


The Commission Regulation (EC) No. 1287/2006 of 10 August 2006 that implements the DMIF, defines in its articles 13 and 14, the contents of the transaction report which aims to collate data from Member States with the least divergence possible.  This harmonization input was complemented by CESR’s Recommendations on the coordination and establishment of mechanisms for the exchange of information concerning transactions carried out between the different relevant Member States.


Transaction reporting is due on financial intermediaries regarding all transactions carried out on a regulated market, multilateral trading facility (MTF) and systematic internaliser (SI) or outside them. Furthermore, a transaction reporting system subject to the prior approval of the CMVM, is also envisaged as per CMVM Regulation No. 2/2007, thus exempting financial intermediaries from complying with the reporting duty.


In addition to the transaction reporting duty and the duty to maintain an updated list of the financial instruments provided for in article 11 of the Commission Regulation (EC) No. 1287/2006 of 10 August 2006, this Regulation imposes on market managing entities of a regulated market or MTF domiciled or operating in Portugal, the duty to communicate to the CMVM all identifying reference data on each financial instrument that is admitted to or selected for trading in markets or systems managed by the mentioned entities.  


Lastly, this Instruction also requires financial intermediaries based in national territory and branches that have been authorised to carry out in Portugal, the execution of orders on behalf of third parties or trading for own account on financial instruments, to communicate to the CMVM, the relevant identifying reference data as per article 290/1/b and e/ of the Securities Code (hereinafter ‘SC’).


This Instruction was submitted for public consultation.


Thus, pursuant to the terms of article 315/8 of the SC, the CMVM determines the following:

Rule No. 1:  This Instruction regulates transaction reporting on financial instruments admitted to trading on a regulated market, MTF, SI or outside them.


Rule No. 2.1.:   Financial intermediaries based in national territory and branches that have been authorised to execute orders on behalf of third parties or trading for own account on financial instruments in Portugal as provided for in article 290/1/b and e/ of the SC, are required to communicate to the CMVM, no later than the close of the next working day following the execution of the transaction, all information concerning transactions in financial instruments admitted to trading on a regulated market, domiciled or operating in an EU Member State as per Attachments IV and V.

 

2.2. This rule is not incumbent on derivative transactions that do not have internationally accepted coding.


Rule No. 3:  The information required in Rule No. 2.1. may be made via a transaction notification system approved by the CMVM and identified by the financial intermediary.  The financial intermediary is thus relieved from the reporting duty.


Rule No. 4:  For the purposes of transaction reporting, the financial intermediaries mentioned in 2.1. are required to immediately communicate to the CMVM, the BIC code that they intend to use for the purposes of information reporting as per Attachment III.


 

Rule No. 5:  The managing entities of a regulated market or MTF domiciled or operating in Portugal, are required to immediately communicate to the CMVM the identifying reference data on each financial instrument that is admitted to or selected for trading in the relevant markets or systems as per Attachment II.


 

Rule No. 6:  Managing entities of a regulated market or MTF based in Portugal, are required to immediately identify themselves to the CMVM via email to (cmvm@cmvm.pt), using their MIC codes (Market Identifier Code – ISO Standard 10383) for each of the managed markets.  The central counterparties based in Portugal are required to identify themselves to the CMVM via email to (cmvm@cmvm.pt), using their MIC or BIC codes – ISO Standard 9362).


Rule No. 7: The information mentioned in the previous rules is required to be communicated to the CMVM as per the rules, format, technical specifications and contents provided for in Attachments I and V.

 
Rule No. 8:   Non-submission of the information report by the financial intermediary within the established deadline provided for in Rule No. 2.1., will infer that no transactions need be reported.


Rule No. 9:  The information required in this Instruction shall be submitted and processed through the CMVM’s extranet domain in a computer file as per Attachments I and V, which form an integral part of this Instruction. In the likelihood of temporary unavailability to submit said information via the CMVM extranet domain, the files may be submitted via email to (cmvm@cmvm.pt) or on a floppy disk, albeit complying with the rules for safeguarding the security, integrity and confidentiality of the information.  The submission of the information via this alternative means must be duly reasoned and is required to be resent via the extranet domain as soon as possible.


Rule No. 10:  The submission of said information via the extranet domain is subject to access permission to the CMVM’s database which is granted by allocating a digital certificate and a password.  Request for the issue of a new certificate must be made in writing and collected at the CMVM’s premises by an authorised person after receiving the password sent by the CMVM. The submission of information via email is subject to file encryption devices.


Rule No. 11: For the purposes of complying with the established submission deadline, information that has been submitted depicting inappropriate quality will be disregarded.  Information submitted without complying with the rules on information structure and contents as per this Instruction will be considered inappropriate and will thus be declined by the extranet domain during transmission due to lack of data conformity and consistency.


Rule No. 12:  In the event of amendments to the submitted information, the entire information shall be resubmitted as per Rule No. 9.  Former reported information will only be considered as replaced by the resubmitted version once the latter is accepted by the CMVM.

 
The CMVM may refuse the amendments made to the formerly submitted information if all the information that is requested on those changes, is not submitted during the established deadline.


Rule No. 13:  Within the ambit of this Instruction, the person designated by the financial intermediary or the managing entity of a regulated market or MTF based in Portugal, is responsible before the CMVM for the quality of the submitted information.


Rule No. 14:  Instruction No. 1/2005 is hereby repealed.


Rule No. 15: This Instruction will come into force on the working-day following notification to the relevant recipients.  Information to be reported concerning transactions carried out between 1 November 2007 and the day of the entry into force of this Instruction shall be communicated to the CMVM until 20 November 2007.  The reporting of information concerning fields 15 and 16 of Attachment IV as well as the contents of Attachment V, is discretionary until 30 June 2008.



Lisbon 5 de November 2007 – Vice-Chairman of the Executive Board, Amadeu Ferreira, Member of the Executive Board, Rui Manuel Pedras

 

 



Attachment I


 General Rules on Information


Structure and Content


 

1. The following rules on information structure are applicable to the tables in Attachments II to V:

1.1. Each table shall correspond to a sole file in ASCII format with the fields separated by a semicolon.

1.2. For attachments III, IV and V, the files’ names shall have the ‘NNNYYYYMMDDXXX.DAT’ format, whereby ‘NNN’ corresponds to the registration number assigned to the financial intermediary by the CMVM, ‘YYYY’, ‘MM’ and ‘DD’ corresponds to the year, month and day, respectively, to which the information relates.  ‘XXX’ identifies the table to which the file relates.  All the characters in the file name must be completed.


1.3. For attachment II, the file name shall have the ‘YYYYMMDDXXX.DAT’ format, whereby ‘YYYY’, ‘MM’ and ‘DD’ corresponds to the year, month and day, respectively, to which the information relates.  ‘XXX’ identifies the table to which the file relates.  All the characters in the file name must be completed.


1.4. Each file line has solely one entry and ends with a line break.  Entries are composed of the fields for each of the tables of the Attachments.


1.5. Names shall not be inserted for identifying entry fields.


1.6.  The field properties to be used are as follows:

1.6.1. Numeric field: will only accept characters from the [0;9] set.  Decimal point shall be used when applicable and no other characters shall be used to separate thousands and millions;


1.6.2. Alphabetic field: will only accept characters from the [A;Z] set;


1.6.3. Alphanumeric field: will only accept characters mentioned in 1.6.1 and 1.6.2;


1.6.4. No additional characters, such as spaces, shall be inserted in blank fields.  



 2. The following rules on information content are applicable to Attachments IV and V:


2.1. The data to be reported consists of the executed transaction and does not relate to its physical or financial settlement. Trading time shall also be inserted.


2.2.  Foreign currency transactions shall be expressed in the applicable reference currency by insertion in the respective field.


 



 

Attachment II  

Rules for the ‘CIF’ (CFI) Table – Characteristics of Financial Instruments

admitted to or selected for trading

in a regulated market or multilateral trading facility



1. The information in Rule no. 5 of this Instruction shall be submitted as per the the CFI table’s format, until the last working day prior to the update under the provided for in this attachment’s Rule 2.1.


2. The CFI table is comprised of the following fields and should observe the following rules:

2.1. Field 1 (Update Date): the date concerning the update made to the reference data of each financial instrument to be reported, shall be inserted in this field.


The ‘YYYYMMDD’ format shall be used for reporting purposes as per ISO standard 8601, whereby ‘YYYY’, ‘MM’ and ‘DD’ represent the year, month and day respectively.

Maximum Range:  8 numeric characters.

2.2. Field 2 (Update Description):  identifies the state of the financial instrument that is being reported and shall be inserted as per the following codes:


        - “ADM” – Admitted to or selected for trading;

        - “ACT” – Update or amendments to the financial instrument admitted to or selected for trading;

        - “EXT” – Extinction of the financial instrument admitted to or selected for trading;

        - “EXC” – Exclusion of the financial instrument admitted to or selected for trading;

        
        Maximum Range: 3 alphanumeric characters.

2.3. Field 3 (Date of Admission to Trading): the date when the financial instrument was admitted to or selected for trading in a regulated market or multilateral trading facility.


The ‘YYYYMMDD’ format shall be used for reporting purposes as per the requirements of ISO Standard 8601, where ‘YYYY’, ‘MM’ and ‘DD’ represent the year, month and day, respectively.


Maximum Range: 8 alphanumeric characters.

2.4. Field 4 (Date of the Last Trading Day): the date of the last trading day when the financial instrument was admitted to or selected for trading on a regulated market or multilateral trading facility.

The ‘YYYYMMDD’ format shall be used for reporting purposes as per the requirements of ISO Standard 8601, whereby ‘YYYY’, MM’ and ‘DD’ represent the year, month and day, respectively.


         Maximum Range: 8 alphanumeric characters.

2.5. Field 5 (Issuer Type):  the type of issuer of the financial instrument and the following codes shall be inserted accordingly:


      - ‘EMN’ – National Issuer;


      - ‘EMENIF’ – Foreign Issuer (Non-Financial Intermediary)


       - ‘EMEIF’ – Foreign Issuer (Financial Intermediary);


       - ‘EGM’ – Regulated Market or Multilateral Trading Facility;


       - ‘OTR’ – Type of Issuer other than those previously mentioned.


   Maximum Range: 3 to 6 alphanumeric characters


2.6. Field 6 (Issuer): identifies the issuer of the financial instrument and shall be filled in as per the type of issuer, mentioned previously and the following identification data shall be used:


  -  Taxpayer Registration Number – ‘EMN’;


  -  Tax Identification Number or Corporate Tax Identification Number –  ‘EMENIF’;    


 -   Bank Identifier Code (BIC) as per ISO Standard 9362 – ‘EMEIF’;


- MIC Code (Market Identifier Code) as per ISO Standard 10383, when processing standardized financial derivative instruments by the marketing entity of the regulated market or multilateral trading facility – ‘EGM’;


- Code specified by the marketing entity of the regulated market or multilateral trading facility that indubitably identifies the issuer – ‘OTR’.  


 Maximum Range: up to 50 alphanumeric characters.


2.7. Field 7 (ISIN Code): insertion of the ISIN Code of the financial instrument (International Securities Identifying Number) as per ISO Standard 6166.


Maximum Range:  2 alphabetic characters, 9 alphanumeric characters and 1 numeric character.

 

2.8. Field 8 (ISIN Code of the Underlying Asset): insertion of the ISIN Code of the financial instrument’s underlying asset, as per ISO Standard 6166.


Maximum Range:  2 alphabetic characters, 9 alphanumeric characters and 1 numeric character.


2.9. Field 9 (Name of the Financial Instrument): this field shall contain the identification of the financial instrument, its characteristics or other relevant information that identifies the instrument.


Maximum Range: Up to 55 alphanumeric characters.


2.10. Field 10 (Type of Financial Instrument):  this field shall contain the type of financial instrument.  The following codes apply:

 
        - “ACC” – Shares


        - “CRT” – Certificates


        - “DIR” – Rights


        - “OBR” – Bonds


        - “TP” – Equity Certificates


        - “UP” – Investment Units


        - “VMOC” – Mandatory Convertible Security


        - “WAR” – Warrants


        - “OVM” – Other Securities


        - “IMM” – Cash Investments/Reserves


        - “OPC” – Options


        - “FUT” – Futures


        - “SWP” – Swaps


        - “CPTJ” – Interest Rate Futures Contracts


        - “OCD” – Other Derivative Contracts

 
       Maximum Range: 2 to 6 alphanumeric characters.


 


2.11. Field 11 (Form of the Financial Instrument):  this field shall contain the form of the financial instruments.  The following codes apply:

        
        - “ESCT” – Financial instruments issued in registered form;


        - “TIT” – Financial Instruments issued in bearer form;


        - “OTR” – Other forms of issuing financial instruments;

        
              Maximum Range: 3 or 4 alphabetic characters.

        

2.12. Field 12 (Class of the Financial Instrument): identifies the class of the financial instrument and shall be filled in as per the following codes:


        - “NOM” – Nominal Financial Instruments;


        - “PORT” – Bearer Financial Instruments;


        - “OTR” – Other class of Financial Instruments;  

        
        Maximum Range: 3 or 4 alphabetic characters.


2.13. Field 13 (CFI Code):  this field shall contain the CFI code (Classification of Financial Instruments) as per ISO Standard 10962.


Maximum Range: 6 alphabetic characters.

        

2.14. Field 14 (Identification of the admission to trading structure): identifies the market wherein the financial instrument was admitted to trading and shall be filled in as per the MIC Code of the regulated market or multilateral trading facility (Exchanges and Market Identification) in question, as per ISO Standard 10383.


Maximum Range: 11 alphabetic characters.

   

2.15. Field 15 (Accumulated Number of Transactions): identifies the amount of financial instruments admitted to or selected for trading.

 

Maximum Range: Up to 10 numeric characters.

        

2.16. Field 16 (Nominal Value): identifies the nominal value of the financial instrument admitted to or selected for trading.

 

Maximum Range: Up to 10 numeric characters.


 
 


  


Attachment III


Rules for the ‘IIF’ (IFI) Table – Identification of the Financial Intermediary

 

1. The information mentioned in Rule 4 of this Instruction shall be provided in the format as per the IFI table.


 2. The IFI table is comprised of the following fields and should observe the following rules:  


2.1. Field 1 (Registration Number at the CMVM): the registration number of the financial intermediary at the CMVM shall be inserted in this field.


Maximum Range:  3 numeric characters.


2.2. Field 2 (Identification of the Financial Intermediary): this field shall contain the BIC Code (Bank Identifier Code) as per ISO Standard 9362 or the SWIFT Code, should the former be unavailable.


Maximum Range: 11 alphanumeric characters.  Should the BIC Code contain solely 8 characters, then the default initials ‘XXX’ will be used as a stand-in for characters 9 to 11.

 

3.  Whenever changes are made to the identification code, the financial intermediary shall immediately report this fact to the CMVM by providing the new table with the updated code that the financial intermediary will begin using.

 
 


  


Attachment IV

Rules for ‘OPE’ Table - Transactions in Financial Instruments admitted to trading on a Regulated Market


 

        1. The information referred to in Rule No. 2.1. of this Instruction shall be submitted as per the ‘OPE table’s format.  Each transaction on the ‘OPE’ table is identified solely by the following fields:  ‘Identification of the Financial Intermediary’, ‘Transaction Date’, ‘Buy/Sell Indicator’, ‘Instrument Identification’ and ‘Transaction Reference Number’.

         

            2. The ‘OPE’ table is comprised of the following fields and should observe the following rules:

 

                      2.1. Field 1 (Identification of the Financial Intermediary): this field shall contain the BIC Code (Bank Identifier Code) as per ISO Standard 9362 or the SWIFT Code, should the former be unavailable.

Maximum Range:  11 alphanumeric characters.  Should the BIC Code contain solely 8 characters, then the default initials ‘XXX’ will be used as a stand-in for characters 9 to 11.

 

2.2. Field 2 (Transaction Date): this field shall contain the date in which the transaction was carried out.  The relevant date is the transaction execution date and not the physical settlement date.

 

This field does not recognize future dates.

 

                    The ‘YYYYMMDD’ format shall be used for reporting purposes as per the requirements of ISO Standard 8601, whereby ‘YYYY’, MM’ and ‘DD’ represent the year, month and day, respectively.

                 

                       Maximum Range: 8 alphanumeric characters.

 

2.3. Field 3 (Trading Time):  this field shall contain the time when the transaction was executed with the ‘HHMMSS’ format as per ISO Standard 8601.  ‘HH’ indicates the hour, ‘MM’, the minutes and ‘SS’, the seconds according to the local time where the transaction was executed.

 

Maximum Range:  6 numeric characters.  

 

2.4. Field 4 (Time Zone Offset Indicator): this field indicates the time at which the transaction was executed expressed as Coordinated Universal Time (UTC) +/-hh.

Maximum Range:  1 symbol and 2 numeric characters.

 

2.5. Field 5 (Buy/Sell Indicator): identifies a buy or sell transaction as to who reports the information, should the transaction be for own portfolio or, if not, from the client’s perspective.  The indication of ‘B’ for buying and ‘S’ for selling, shall be inserted.

 

Maximum Range:  1 alphabetic character.

 

                      2.6. Field 6 (Trading Capacity): the following codes shall be used when identifying the intermediary’s trading capacity:

                 

- ‘P’: transactions undertaken for the financial intermediary’s own portfolio;

- ‘A’: transactions undertaken for the financial intermediary’s clients’ portfolio.

 

Maximum Range: 1 alphabetic character.

         

                      2.7. Field 7 (Instrument Identification): insertion of the ISIN Code of the financial instrument (International Securities Identifying Number) as per ISO Standard 6166.

                       Maximum Range:  2 alphabetic characters, 9 alphanumeric characters and 1 numeric character.

                 

2.8. Field 8 (Unit Price): insertion of the unit price concerning the traded financial instrument.  The price excludes any commission and other costs, for instance, accrued interest.  For bonds, the percentage price shall be used and for other form of debt instruments, the price may be expressed in currency or as a percentage.

The ‘%’ symbol shall not be used for percentage price.  If the price is expressed in percentage terms, for e.g. 23,45%, it should be reported as ’23,45’ and not ‘0,2345’.

Maximum Range:  up to 19 numeric characters with a maximum of five decimal places.

 

2.9. Field 9 (Price Notation):  this field identifies the type of price used in Field 8 (Unit Price) and shall be filled in with one of the following codes:

 

 - ‘M’: when field 8 is expressed in currency;

- ‘P’: when field 8 is expressed in percentage terms.

 

Maximum Range:  1 alphabetic character

 

                       2.10. Field 10 (Currency Notation): this field identifies the reference currency used for price reporting in field 8 (Unit Price).  Should the price be indicated in percentage terms, the field should be filled in with the relevant currency of the financial instrument’s nominal value.

This field shall be filled in as per ISO Standard 4217.

Maximum Range:  3 alphabetical characters.

 

2.11. Field 11 (Quantity): insertion of the trade volume, the nominal value of the bonds or the number of derivative contracts in the transaction.

Maximum Range: Up to 19 numeric characters with a maximum of 5 decimal places.

 

2.12. Field 12 (Counterparty): insertion of the counterparty transaction.  The following format shall be used:

 -  Financial Intermediary – BIC Code as per ISO Standard 9362;

- Regulated Market or Multilateral Trading Facility – MIC Code as per ISO Standard 10383;

 - Central Counterparty – MIC Code as per ISO Standard 10383 or the BIC Code as per ISO Standard 9362;

- Financial Intermediary’s Client – the relevant client code as per the provisions for Field 15.

 

Maximum Range:  11 or 4 alphanumeric characters or 7 alphabetic characters.

 

                       2.13. Field 13 (Counterparty Code): this field identifies the type of code used in Field 12 (Counterparty).  The following codes shall be used:

- ‘B’: when field 12 is identified with the BIC Code;

- ‘M’: when field 12 is identified with the MIC Code;

- ‘C’: when field 12 is identified with the client’s code.

 

Maximum Range:  1 alphabetic character.

         

                       2.14. Field 14 (Trading Venue Identification): this field shall be used to identify where the transaction was executed and shall use the following information:

- MIC Code as per ISO Standard 10383 for a regulated market or multilateral trading facility;

- BIC Code as per ISO Standard 9362 for a systematic internaliser (financial intermediary);

-  ‘XOFF’ Code for off-the-market transactions.  

 

Maximum Range:  11 or 4 alphanumeric characters.   

 

                      2.15. Field 15 (Customer/Client Code): identifies the natural or legal person (the orderer) that instructs the financial intermediary, who in turn reports such transaction to the CMVM.  This field shall be filled in as follows:

-  BIC Code as per ISO Standard 9362, if one exists for the orderer;

-  In the absence of the BIC Code, the Tax Identification Number shall be used. A foreign entity that does not hold a Tax Identification Number, shall use the Identification Number allocated by the Central Bank (Banco de Portugal);

- In the absence of both the Tax Identification Number or the Identification Number allocated by the Central Bank (Banco de Portugal), an Internal Identification Number shall be used which has been allocated to the client by the financial intermediary.  The internal numbers allocated to the customers by the financial intermediary shall be consistent with the code and person that identifies same;

- Should the amount of orders inserted in field no. 11 be transmitted by more than one orderer (aggregated orders), this field shall include an ‘AG’ code and the table in Attachment V shall also be sent as per the terms mentioned therein.

 

Maximum Range:  40 alphanumeric characters.

 

                      2.16. Field 16 (Customer/Client Identification): identifies the nature of the customer/client code used in Field 15 (Customer / Client Code).

              The following codes are to be used:

- ‘B’:  if the previous field has been filled in with the BIC Code;

- ‘N’:  if the previous field has been filled in with the Tax Identification Number;

- ‘P’: if the previous field has been filled in with the Identification Number allocated by the Central Bank;

- ‘I’: if the previous field has been filled in with the Internal Identification Number allocated to the orderer by the financial intermediary; and

- ‘G’: if the previous field has been filled in with the ‘AG’ Code.

Maximum Range: 1 alphabetic character.

 

                      2.17. Field 17 (Transaction Reference Number): this field shall contain the sole transaction reference number furnished by the market or system managing entity on transactions executed on a regulated market or multilateral trading facility.  As to off-market transactions, the sole transaction reference number furnished by the financial intermediary shall be used.

              Maximum Range:  Up to 40 alphanumeric characters.

         

                     2.18. Field 18 (Cancellation Indicator Flag): cancelled registrations shall be wholly reported and filled in with ‘C’, or otherwise left blank.

The cancellation indicator may not be used when resubmitting an incorrect data report that had previously been reported.

Maximum Range:  1 alphabetic character.

 

 

 

 

Attachment V

 

Rules for Table ‘AGC’ – Client Information concerning Aggregate Transactions

 

           3. Client information concerning aggregate transactions which were reported as ‘AG’ in field 15 of the ‘OPE’ table, is to be reported as per the corresponding ‘AGC’ table.  The sum of the amount reported in the ‘OPE’ table with field 15 filled in with ‘AG’.

           4. The ‘AGC’ table is comprised of the following fields and should observe the following rules:

                      4.1. Field 1 (Identification of the Financial Intermediary): this field shall contain the BIC Code (Bank Identifier Code) as per ISO Standard 9362 of the SWIFT Code, should the former be unavailable.

                      Maximum range:  11 alphanumeric characters.  Should the BIC Code contain solely 8 characters, then the default initials ‘XXX’ will be used as a stand-in for characters 9 to 11.

                 

4.2. Field 2 (Transaction Date): this field shall contain the date in which the transaction was executed.  The relevant date is the transaction execution date and not the physical settlement date.

 

This field does not recognize future dates.

                 

                      The ‘YYYYMMDD’ format shall be used for reporting purposes as per the requirements of ISO Standard 8601, whereby ‘YYYY’, MM’ and ‘DD’ represent the year, month and day, respectively.

                 

                       Maximum Range: 8 alphanumeric characters.

 

4.3. Field 3 (Buy/Sell Indicator): identifies a buy or sell transaction as to who reports the information, should the transaction be for own portfolio or, if not, from the client’s perspective.  The indication of ‘B’ for buying and ‘S’ for selling, shall be inserted.

 

Maximum Range:  1 alphabetic character.

 

                    4.4. Field 4 (Instrument Identification): this field identifies the transacted financial instrument. Insertion of the ISIN Code of the financial instrument (International Securities Identifying Number) as per ISO Standard 6166.

                 

                      Maximum Range:  2 alphabetic characters, 9 alphanumeric characters and 1 numeric character.

 

                      4.5. Field 5 (Transaction Reference Number): this field shall contain the sole transaction reference number furnished by the market or system managing entity on transactions executed on a regulated market or multilateral trading facility.  As to off-market transactions, the sole transaction reference number furnished by the financial intermediary shall be used.

              Maximum Range:  Up to 40 alphanumeric characters.

                 

                    4.6. Field 6 (Customer/Client Code): identifies the natural or legal person (the orderer) that instructs the financial intermediary, who in turn reports such transaction to the CMVM.  This field shall be filled in as follows:

-  BIC Code as per ISO Standard 9362, if one exists for the orderer;

-  In the absence of the BIC Code, the Tax Identification Number shall be used. A foreign entity that does not hold a Tax Identification Number, shall use the Identification Number allocated by the Central Bank (Banco de Portugal);

- In the absence of both the Tax Identification Number or the Identification Number allocated by the Central Bank (Banco de Portugal), an Internal Identification Number shall be used which has been allocated to the client by the financial intermediary.  The internal numbers allocated to the customers by the financial intermediary shall be consistent with the code and person that identifies same;

                       Maximum Range:  40 alphanumeric characters.

         

                    4.7. Field 7 (Customer/Client Identification Code): identifies the nature of the customer/client code used in Field 15 (Customer / Client Code).

             The following codes are to be used:

- ‘B’:  if the previous field has been filled in with the BIC Code;

- ‘N’:  if the previous field has been filled in with the Tax Identification Number;

- ‘P’: if the previous field has been filled in with the Identification Number allocated by the Central Bank;

- ‘I’: if the previous field has been filled in with the Internal Identification Number allocated to the orderer by the financial intermediary; and

 

Maximum Range: 1 alphabetic character.  

 

                    4.8. Field 8 (Amount): insertion of the disaggregated amount of the transacted financial instrument, the nominal value of bonds or the number of derivative contracts.  The sum of the disaggregated amounts is equal to the total amount of the reported transaction in the ‘OPE’ table with field 15 filled in with ‘AG’.

                 

                      Maximum Range:  Up to 19 numeric characters with a maximum of 5 decimal places.