Tag: fine

  • ESMA fines trade repository for data delivery breaches

    ESMA has announced it has fined a trade repository for failing to provide regulators direct and immediate access to details of derivative contracts. The failures relate to trade terminations and valuations and collateral updates for the period from the start of EMIR trade reporting go live in February 2016 through to October of the same year. According to the public notice, ESMA remained unaware of the error until it was informed by the Dutch national competent authority (NCA) in July 2016.

    The fine should be a reminder to all industry participants that ESMA takes EMIR trade reporting very seriously. ESMA and the NCAs also have a ‘Data Quality Action Plan’ to address quality issues in EMIR trade reports submitted by firms.

    If you are in any doubt whether your reports meet the standards required by the regulators, please get in contact with us to discuss your EMIR data quality. The FCA has already issued a £34.5m fine for EMIR reporting breaches – we can help you put the right controls in place to make sure that you are not at risk too.

  • Second fine for transaction reporting breaches in two weeks is a record £34.3m

    Second fine for transaction reporting breaches in two weeks is a record £34.3m

    The FCA has issued a record fine of £34.3m for incorrect transaction reporting, hot on the heels of a fine two weeks ago for similar breaches. 

    According to the FCA, the firm in question failed to provide accurate and timely reporting relating to 220.2 million transaction reports between November 2007 and March 2017.

    If any firm doubts the FCA’s resolve in its pursuit of complete and accurate transaction reporting, they need to take note of these fines and the accompanying warning from Mark Steward, the FCA’s Director of Enforcement:

    ‘The failings in this case demonstrate a failure over an extended period to manage and test controls that are vitally important to the integrity of our markets. These were serious and prolonged failures. We expect all firms will take this opportunity to ensure they can fully detail their activity and are regularly checking their systems so any problems are detected and remedied promptly, unlike in this case.’

    The two recent fines are almost double the amount of the previous 12 fines for MiFID reporting combined.

    What went wrong?

    The FCA’s Final Notice tells a very familiar tale of what happens when a complex organisation, acting in good faith, attempts to deliver upon these very complex regulatory obligations; a significant, material, and widespread set of issues left undetected for many years.

    The key message is that these errors result from inadequate systems and controls over transaction reporting. In particular, the FCA found issues with:

    1. Change management
    2. Accuracy and completeness controls – again signalling issues with an approach that only tests data samples
    3. Reference Data – identification of counterparties

    The FCA is evidently tired of sounding like a broken record as these three control issues continually result in transaction reporting failings. The message should be familiar to firms and their SMCR managers responsible for reporting.  It’s not a secret that if firms don’t test the accuracy of their reporting, don’t test their reference data and change management processes, and don’t have adequate reconciliation from front office systems to the reports received by the FCA, then they cannot have confidence their reporting is correct.

    Lessons for MiFIR transaction reporting

    It is important to note that both fines are for failures under the previous MiFID transaction reporting regime. It is possible that this now marks the end of sanctions for the MiFID reporting regime and that the FCA’s focus will turn to the MiFIR reporting regime which is considerably more complex than the MiFID reporting regime. The FCA has already warned about the unsatisfactory quality of some transaction reporting under the new regime and the potential future consequences. There are many more things that can go wrong under the new regime and it is essential that firms are confident that they have adequate controls over their transaction reporting. Firms need to take note that the reference period for this fine’s transaction reporting breaches started on 5 November 2007 – the very first day of the MiFID transaction reporting; no grace period. 

    Get peace of mind in your reporting quality

    Our blog about the fine two weeks ago asks ‘could it have been you?’ and if you have any doubt, it is important to act now.  These two fines should be a wake up call for senior managers to get their reporting controls up to standard – and fast. This is exactly what we here at Kaizen exist to do.  We have a proven track record in helping firms tackle their trade and transaction reporting issues and risks head on – and helping them to avoid censure whether it is for MiFIR, EMIR, Dodd-Frank or another G20 regulation.

    Our ReportShield™ quality assurance service marries our regulatory expertise with data science, and uniquely tests every single record at source avoiding the pitfalls of testing only a sample of data.  The service includes everything you need for reporting assurance including a bespoke control framework, quality assurance testing, reference data testing, advanced reconciliation and training. Please contact us for a discussion with one of our regulatory experts to find out how we can give you peace of mind in your reporting quality. 

  • FCA MiFID reporting fine – could it have been you?

    FCA MiFID reporting fine – could it have been you?

    Many firms were wondering when the first fine for MiFIR transaction reporting breaches would be levied by the FCA, so it might have come as a surprise to see a fine for a breach under the previous MiFID transaction reporting regime. We have seen strong signals from the FCA that it is disappointed with quality of some of the transaction reports it receives and it has been tireless in explaining that complete and accurate transaction reports are essential to monitor for market abuse effectively.

    Tough line

    Despite these warnings, some might have been thinking that the FCA was too occupied with Brexit to take enforcement action for transaction reporting breaches. The latest fine, at £27.6m after a 30% early settlement discount, is over twice as large as the previous fine for MiFID transaction reporting and should leave firms in no doubt that the FCA will continue to take a hard line with reporting breaches of both the MiFID and EMIR variety.  Many may be left considering what they should be doing to make sure they’re not the next subject of enforcement action.

    What failings did the FCA identify?

    Purely in terms of numbers, between 5 November 2007 and 24 May 2017, the firm:

    1. Failed to report 3,658,423 transactions;
    2. Inaccurately reported 83,074,015 transactions, and
    3. Erroneously reported 49,152,274 transactions.

    These look like very large numbers, but they have to be taken in context: In the period in question approximately 1.8 billion transactions were reported. This implies that the FCA didn’t raise any issues for approximately 1.665 billion transaction reports, or 92.5% of the submitted reports. It would be interesting to know how many senior managers are confident their firm is reporting more than 92.5% of its transactions correctly. Of course, they should be aiming for 100% complete and accurate reporting, but it is possible that many senior managers don’t actually know their accuracy rate.

    Systems and controls

    Of course, it isn’t just a numbers game. The accompanying Final Notice highlights a lack of sufficient systems and controls. In particular, the FCA stated there was a breach of Principle P3 by:

    1. Failing to have adequate systems and controls to ensure that reference or ‘static’ data used for various mandatory fields in the transaction reports submitted to the authority were complete and accurate;
    2. Failing to have in place adequate change management controls to manage changes affecting transaction reporting processes and systems, and
    3. Failing to undertake appropriate testing to ensure the completeness and accuracy of transaction reports.

    It is particularly interesting to note the criticisms in the Final Notice of the control framework calling out that it “did not adequately test and reconcile the completeness and accuracy of all transaction reporting data from its front office systems to the ARM reporting to the Authority.”

    Lessons to be learned

    The obvious lesson is that the FCA is actively enforcing transaction reporting. If your firm does not have adequate systems and controls in place or doesn’t even know how good (or bad) its reporting is; you could be at risk.

    Interestingly, in reference to the weakness of the reconciliation and testing controls, the notice called out the “periodic, sample based” nature of them. The limitations of sample testing and the false confidence that it provides has been one of the root causes of many a fine. At Kaizen, we provide quality assurance testing on all transaction reports and our reconciliation service tests all trades in the front office systems, determines whether they should be reported, and only then reconciles against the reports submitted to the regulator. We can also advise on the control framework, test all reference data (including ISINs, counterparty LEIs and for natural persons) and provide training on the regulatory requirements.

    Firms need to react

    When issues are identified by the FCA the clock is ticking. Firms should take any issue identified by the FCA as a trigger to not only investigate the issue raised but to look across all of its reporting to make sure it is correct. Flushing out issues quickly is critical in maintaining the confidence of the FCA. The industry is littered with examples of firms that have completed reviews and improved procedures only to have issues found many months and sometimes years later.

    Senior Managers liable

    The Senior Managers and Certification Regime (SMCR) has increased the reporting risks by making senior managers personally liable for transaction reporting controls.  The SMCR is soon to extend to all core firms at the end of the year.  Firms and their senior managers need to examine the systems and controls they have over transaction reporting and ask themselves whether they truly understand whether they are meeting the FCA requirements or whether they could be potentially next in line for enforcement action.

    If you have any doubts whether your reporting and controls are up to the required standard, we can help.  We have a proven track record in helping firms tackle their transaction reporting issues and risks head on – and helping them to avoid censure.Our ReportShield™ quality assurance service provides everything you need for reporting assurance including a bespoke control framework, quality assurance testing, reference data testing, reconciliation and training.  

    Please contact us for a discussion with one of our regulatory experts to find out more.

  • Kaizen’s reaction to the £27.6 million fine issued by the FCA for incorrect reporting

    Kaizen’s reaction to the £27.6 million fine issued by the FCA for incorrect reporting

    Our Senior Regulatory Reporting Specialist, David Nowell, commented on the £27.6 million fine issued by the FCA today for breaches under the MiFID reporting regime:

    “Many may be surprised that the FCA should levy such a large fine for breaches under the previous MiFID reporting regime. However, it is a clear sign of the FCA’s tenacity and determination to strive for complete and accurate transaction reporting. It is also a message that could strike fear in the hearts of many senior managers as the new MiFIR transaction regime is far more complex than the previous MiFID regime. The requirement for adequate systems and controls over transaction reporting are clearly set out in Article 15 of RTS. Having a strong governance framework, regular reconciliations, quality assurance testing, and reference data testing are key elements in meeting these requirements. The FCA has been clear and consistent in its demands for complete and accurate transaction reporting; this latest fine is a strong and timely reinforcement of this message.”

    For accurate and complete reporting please contact us.
    For media inquiries, please contact Fiona Wilde on media@kaizenreporting.com or +44 (0) 20 3912 3271.

     

  • Valid but wrong: FCA warns on MiFIR transaction reporting data quality

    Valid but wrong: FCA warns on MiFIR transaction reporting data quality

    Senior Managers will not need a crystal ball to predict what will happen when the first MiFID II enforcement case is completed…

    In a speech on 7 February, the FCA’s Head of Market Policy, Stephen Hanks, warned about the unsatisfactory quality of some transaction reporting and the potential future consequences. The FCA stated that it was “particularly disappointed” to see fundamental errors in transaction reports that would have been incorrect under the previous MiFID reporting regime, let alone the far more complex MiFIR reporting regime.

    To demonstrate this type of error, the FCA noted that it was seeing zero in the price field in many reports. This is a classic example of what we call the “valid but wrong” problem. A zero price will pass the ESMA validation, but that doesn’t make it correct – we would only expect a zero price to be seen in exceptional cases, such as certain swap contracts where the spread is zero.

    The FCA also warned that just because there has been no enforcement action so far under MiFiD II, it doesn’t mean that it is happy with how firms have met the MiFID II requirements. Of course, formal sanctions are not the only tool at the FCA’s disposal and many firms have discovered how problematic remediating transaction reporting failures can be when issues are discovered. At Kaizen, we recommend four key areas that firms need to focus on to avoid the worst of the FCA’s wrath:

    1. Accuracy Testing
      • Quality assurance testing of all reportable data to identify incorrect transactions, using independent sources of data where possible
    2. Reconciliation
      • Reconcile all trades in your books and records with data received by the regulator
      • Note that the RTS 22, Article 15 reconciliation requirement includes “checking the timeliness of the report, the accuracy and completeness of the individual data fields and their compliance with the standards and formats specified in Table 2 of Annex 1”
    3. Reference data testing
      • Testing of counterparty and instrument static data for accuracy and completeness
    4. Control Framework
      • A risk and accountability framework tailored to your business
      • Process documentation, steering groups, training and remediation process.

    There is no need to have a crystal ball to understand what will happen when the first fine is issued under MiFID II. Senior management teams (which now include the SM&CR Manager responsible for transaction reporting) in organisations large and small will know exactly how well placed their organisation is in terms of judging the data quality of their reports. The call will go out to Compliance, Operations, Business and IT teams to run an immediate and urgent review of controls and data quality. This takes up valuable management and SME time and firms often don’t end up with the full picture. This is the typical response of firms who have not put in place effective controls and emphasises the need to be proactive and get these controls operational.

    At Kaizen Reporting, we have a team of specialist regulatory experts and data analysts delivering excellence on each of these four transaction reporting assurance requirements. Contact us to find out more about how we can give you peace of mind in the quality of your regulatory reporting and keep you on the right side of the regulator.

  • Measure for measure: ESMA’s assessment of EU-wide supervisory measures for EMIR

    Measure for measure: ESMA’s assessment of EU-wide supervisory measures for EMIR

    Measure for Measure is classed as a comedy yet it is also considered one of Shakespeare’s problem plays as it has aspects of a tragedy. Dealing with the concepts of justice and virtue, the play sprang to mind when reading ESMA’s recently published report on EMIR supervisory measures.

    This is because the report, which runs to some 40 pages, highlights some significant differences in approach by the national competent authorities (NCAs) on supervision and enforcement of EMIR requirements, as well as the fines and other supervisory actions that have been undertaken to date. The report has both good and bad news for financial firms.

    Let’s start with the good: There have only been three fines raised for EMIR breaches to date across Europe. Two of these fines were levied by COVIP (Italy), one for €105k and the other for €60k both in relation to article 9 reporting breaches and article 11 breaches in respect of clearing activities. Within each jurisdiction, the maximum fines that can be levied are almost consistently low.

    And the bad news: the third fine in our list is the eye-watering £35m fine raised by the FCA for the non-reporting of 68 million exchange-traded derivative contracts.  The per-record penalty applied by the FCA was increased because of prior breaches under the MiFID I transaction reporting regime. That points to the FCA treating reporting failures as a single type of breach irrespective of the reporting obligation concerned. In its final notice, the FCA also took the time to highlight that insufficient testing was carried out to ensure the accuracy and completeness of reports as well as weaknesses in oversight arrangements. And in another piece of bad news, the largest potential fine for those countries that have a cap is France’s €100m. 

    Few investigations across Europe

    Perhaps it’s unsurprising, but not all authorities have been active in conducting investigations since the inception of EMIR.  What is surprising is how few investigations have been carried out across Europe when the number of entities, both financial and non-financial, falling within the scope of EMIR is so vast.  We can’t tell the true number of investigations conducted as the “more than 20” category (as shown below) could hold a great many but we would expect ESMA to have stopped there because it was closer to 20 than 40. 

    In terms of investigations carried out, Belgium is the standout performer with more than 20 investigations being run across reporting, clearing obligation, reporting, risk mitigation techniques and Article 11 in respect of Non-Financial counterparties. On the other end of the scale, we have a number of countries that haven’t undertaken any investigations at all including Ireland, Finland, Norway and the Netherlands.

    Number of investigations carried out on the reporting obligation by country in 2017:

    None

    BU

    CZ

    FI

    HR

    IE

    LV

    MT

    NL

    NO

    SI

    1 to 5

    FR

    EL

    SK

    UK

     

     

     

     

     

     

    6 to10

    AT

    DK

    PL

    SE

     

     

     

     

     

     

    11 to 20

    CY

    ES

    PT

     

     

     

     

     

     

     

    >20

    BE

    DE

    LU

    IT

     

     

     

     

     

     

     

    Another piece of bad news (at least for firms) is that we can expect ESMA to push for more harmonisation and more investigative activity.  ESMA and other competent authorities have been concerned with the quality of reporting under EMIR and MiFID. This, combined with the EMIR regime being in its 4th  year and matching rates across repositories remaining challenging, pressure to improve reporting will continue.  Pressure to ensure compliance with the clearing obligation and risk mitigation techniques can also be expected in the coming year.  

    The report also drew attention to the fact that no work seems to have been carried out in terms of the anti-evasion provisions of EMIR.  This would be a complex area to assess but firms should be prepared for questions on this which means having a handle on what guarantees are in place between EU group entities and non-EU entities.

    Penalties across the EU

    The report highlights the approach to penalties as an area where there is a low level of harmonisation. We’ve created the table below which shows the divergence in percentage terms of the maximum caps (France at €100m) and minimum penalties (Bulgaria €40k) across the EU. 

    In the UK and Spain, there is no stated penalty cap. In the case of the UK, a per record penalty is applied which means that the penalty regime scales to the level of reportable activity and degree of non-compliance for the firm concerned. 

    Country

    Percentage of maximum

    Max € (000)

    Notes

    Spain

    n/a

    –

    Variable no stated maximum

    France

    100.00%

    100,000

    Capped at less than 10x gain made or loss avoided

    United Kingdom

    n/a

    –

    Variable no stated maximum

    Finland (articles 4 & 10)

    10.00%

    10,000

    Capped at less than 10% turnover

    Sweden

    5.00%

    5,000

    Now capped at 10% of turnover but figures relate to a decision when the old rules applied.

    Belgium (National Bank)

    5.00%

    5,000

    Capped at less than 10% turnover

    Italy

    5.00%

    5,000

    Capped at less than 10% turnover

    Greece

    3.00%

    3,000

     

    Ireland

    2.50%

    2,500

     

    Poland

    2.50%

    2,500

    < 10% of turnover

    Belgium (FSMA)

    2.50%

    2,500

    Capped at 3x gain made or loss avoided

    Luxembourg

    1.50%

    1,500

    Capped at 5x gain made or loss avoided

    Netherlands

    1.00%

    1,000

     

    Cyprus

    0.70%

    700

    Capped at 2x gain made or loss avoided

    Germany

    0.50%

    500

     

    Czech Republic

    0.40%

    400

     

    Austria

    0.15%

    150

     

    Malta

    0.15%

    150

     

    Latvia (legal persons)

    0.14%

    142

     

    Finland (articles 9 & 11)

    0.10%

    100

     

    Slovenia

    0.10%

    100

     

    Croatia

    0.07%

    67

     

    Latvia (natural persons)

    0.06%

    57

     

    Bulgaria

    0.04%

    40

     

     

    NCA powers across the EU

    NCA powers are relatively consistent allowing them to: summon and interview personnel, conduct on-site investigations and inspect documents. They also all have the power to issue fines, issue binding and non-binding letters whilst some NCAs have the power to issue criminal sanctions against individuals. 

    Actions firms should be taking for EMIR reporting

    Firms should be reviewing their EMIR control environment. This means assessing the more difficult activities of regular accuracy testing, reference data testing and front to back reconciliations as well as ensuring the governance process is robust and up-to-date. 

    Governance arrangements need to be looking at the operation of the reporting process itself, the assurance process around accuracy and completeness of reporting but also the remediation process, ensuring that known issues are being appropriately escalated, prioritised and remediated which includes replaying records to correct historic errors. 

    While we are known for providing accuracy testing and reconciliation services, we also help our clients mature their broader reporting controls with our Control Framework – all are key components of our ReportShield™ quality assurance service. We also, in conjunction with our consultancy partner Elixirr, run remediation programmes to bring firms’ trade repository records into line.  If you would like to discuss your reporting controls please contact us.

    A variation of this article was published by Thomson Reuters Accelus (subscription only) on 20 July 2018. 

  • FCA’s first EMIR reporting fine highlights importance of robust testing and controls

    FCA’s first EMIR reporting fine highlights importance of robust testing and controls

    The £34.5 million fine issued this week by the FCA is the first enforcement action for failing to comply with Article 9 of EMIR and highlights the increasing importance the regulator is placing on data quality.

    It was generally accepted that the regulator would eventually take enforcement action against a firm for EMIR breaches and there would have to be a firm first in line.  In this case it was Merrill Lynch International, however it could probably have been one of many firms that have struggled to deal with the EMIR reporting requirements. 

    The FCA understands that reporting won’t be 100% all the time however its final notice highlights insufficient testing to ensure the accuracy and completeness of reports as well as weaknesses in oversight arrangements that would have contributed to the under reporting of 68 million exchange-traded-derivatives over a two year period. 

    Poor quality data is industry wide 

    While these are serious failures, we would argue that they are not unique to Merrill Lynch.  Poor quality data is a widespread industry problem, something that the regulator and we here at Kaizen have been highlighting for some time. 

    Just last week Ana Fernandes, of the FCA’s Markets Reporting team, focused on the issue of data quality at an industry conference we attended.  She highlighted the importance of  having comprehensive in-depth testing and reconciliations in place at a frequency appropriate to trading volumes.  Firms must test for the accuracy and completeness of their transaction reports and have the appropriate oversight arrangements to detect and remedy systemic problems.  Ana said there were ‘high expectations’ come 3 January 2018 when MiFID II goes live that they would see better data and this is as essential for EMIR, as it is for MiFID and MIFID II.

    Just the tip of the iceberg

    Last year we published our analysis of FCA MiFID I reporting fines which shows how easy it is to get reporting wrong.  More often than not, firms continue to get false confidence from the validations provided by ARMs and Trade Repositories without testing whether the data at source is correct.  Ana in her speech last week focused on just that, “Don’t think that because the file has gone to the ARM and the FCA that it is done” she said. 

    The final notice clearly demonstrates the FCA’s expectations for robust and comprehensive testing of reporting.  This requirement is more clearly articulated for MiFID II, where testing for accuracy and completeness is mandatory under RTS 22, Article 15 and these controls should be in place at go-live.  Similarly, from 1 November (next week!) when EMIR Level 3 goes live, a lot of reporting requirements currently in the EMIR Q&As become part of the Regulatory Technical Standards and therefore become more easily enforceable by the national competent authorities.

    The FCA says the fine, the largest so far, ‘reflects the importance’ it puts on this type of reporting and the important role it plays in ensuring a transparent market. The action also shows that the regulator will fine you more if you’ve got it wrong previously and that it is applying the same approach to EMIR as it does with MiFID in terms of fining on a per record basis. 

    Expect more fines as regimes mature

    As the G20 reporting regimes mature, we are seeing a general trend of increased enforcement activity.  The CFTC has been active recently re DFA, and we also saw the recent ASIC fine by the Australian regulator so I expect further fines to follow.

    Improving firms’ reporting data quality is the reason we at Kaizen exist.  We have several clients that report over 100k trades per day to a trade repository.  With these types of volumes, it’s very easy to end up facing an eye watering fine which is why we have designed our services to protect both the firm and the individuals with reporting oversight responsibility under the senior manager’s regime. 

    Please don’t hesitate to contact us if you would like to discuss your regulatory reporting data quality or any of the issues raised in this piece.

  • Your ASIC reporting risk just increased

    Your ASIC reporting risk just increased

    The Australian Securities and Investment Commission (ASIC) has issued its first penalty notice for alleged breaches of the derivative reporting rules, which require counterparties to report derivative transaction and position information to derivative trade repositories. 

    The notice was issued to Australian bank Westpac together with a fine for AU$127, 250 (about £75,000) for incorrect transaction reporting. The bank failed to ‘report information about 112,556 reportable transactions,’ between October 2013 to 30 April 2015.

    The example demonstrates the importance of having testing and controls in place to identify data quality issues quickly, as we outlined on our recent webinar.

    Flaw in system caused reporting failure

    ASIC said a flaw in Westpac’s reporting system caused the failure, which the bank was made aware of in July 2014, however it wasn’t aware that the flaw was causing the transactions not to be reported. 

    Westpac decided not to further investigate the flaw and put off the investigation to a later date as it thought only a small number of transactions would be affected. 

    The bank only discovered that it was a ‘material number’ of transactions in March 2015.  It reported the unreported transactions to DTCC in January 2016, but they were reported ‘with the counterparty buyer/seller information inadvertently reversed’.

    Firms must have testing in place to identify issues

    This example demonstrates once again how important it is for financial firms to understand their transaction reporting obligations and – just as crucially – to have testing in place to identify issues quickly. 

    Not only that, but when seeking to address an issue through replays, appropriate testing is needed to ensure that the replays do not introduce new errors as is the case here.  Firms would do well to note the two main ‘banana skins’ that have contributed to the notice, notably Westpac’s failure to:

    • Have testing in place to identify at an early stage any reporting quality issues (both accuracy and completeness testing), and
    • Implement assurance on the replays they were submitting.

    These failures left them exposed to regulatory censure which means not only a fine but also reputational damage, both of which could easily have been avoided with the right controls in place.

    Reporting risk levels have increased

    As a first penalty notice under the derivatives reporting regime, the scale of the fine and the quantum per erroneous trade report should be noted as this sets the level of reporting risk that firms are facing from a fining perspective: around AU$1 per incorrect or missing report. 

    If you consider that reporting volumes are significantly higher for most firms, reporting risk levels just increased.

    No matter what the regulation, Kaizen can help protect you from regulatory fines and penalties.  Please contact us for a chat about your regulatory reporting challenges.