Tag: Controls

  • Kaizen Achieves SOC 2 Type II and SOC 3 Information Security Attestations

    Kaizen Achieves SOC 2 Type II and SOC 3 Information Security Attestations

    Latest Attestations Complement Kaizen’s ISO 27001 Information Security Management System and Reinforce Global Compliance and Data Security Excellence

    London, 27 November 2025 – Kaizen, a leading provider of regulatory compliance solutions for global financial institutions, today announced it has successfully achieved System and Organization Controls (SOC) 2 Type II and SOC 3 attestations, further strengthening its commitment to the highest standards of information security and data protection for its global client base.

    The attestations, conducted by an independent American Institute of Certified Public Accountants (AICPA) accredited Certified Public Accountant (CPA) firm, validate the operational effectiveness of Kaizen’s security controls over a 12-month period. This achievement complements the company’s existing ISO 27001:2022 certified Information Security Management System (ISMS), creating a robust dual-framework approach that addresses the diverse compliance requirements of financial institutions across the UK, EU, US and APAC.

    “Achieving SOC 2 Type II and SOC 3 attestations represents a significant milestone in our continuous journey to provide world-class information and data security to our clients,” said Dario Crispini, Founder and CEO at Kaizen. “While our ISO 27001 certification has long demonstrated our systematic approach to information security management, these SOC attestations provide the detailed operational validation that our North American clients particularly value. Together, these frameworks create a comprehensive security system that meets and exceeds expectations of our global client base.”

    The SOC 2 Type II attestation evaluated Kaizen’s controls across all five Trust Services Principles – Security, Availability, Processing Integrity, Confidentiality, and Privacy – providing detailed assurance on the effectiveness of controls protecting client data throughout Kaizen’s ReportShield platform. The accompanying SOC 3 report enables Kaizen to publicly demonstrate its commitment to security excellence.

    Financial institutions are facing increased scrutiny from regulators worldwide on information security. Therefore, by maintaining both ISO 27001 certification and SOC 2 Type II attestation, the company is addressing the wide range of data security requirements across different regulatory jurisdictions, from prescriptive ISMS focused requirements in Europe and APAC, to the detailed control validation  required by US institutions. While the ISO 27001 certification provides a framework for continuous improvement in data security and risk management, SOC 2 Type II provides operational evidence and control testing for our security practices.

     

    (Ends)

     

    For more information about Kaizen’s security certifications, please contact: communications@kaizenreporting.com

     

  • Cappitech and Kaizen Reporting publish findings of SFTR implementation survey

    Cappitech and Kaizen Reporting publish findings of SFTR implementation survey

    FOR IMMEDIATE RELEASE

    17 September 2019, London and Tel Aviv: Cappitech and Kaizen Reporting today published the findings of the SFTR implementation survey conducted by Cappitech, a leading provider of regulatory reporting and intelligence solutions for the financial services industry, and analysed by Kaizen Reporting, global leaders in quality and accuracy for regulatory reporting, in which securities financing market participants were asked to help establish the industry’s state of readiness.

    While there is a greater state of readiness among the banks (due to go live in the first phase, April 2020) of reporting, the survey shows that 56% of banks are still only in the pre-implementation planning stages. The survey concluded that overall only 37% of the securities lending industry has started or completed SFTR implementation and expect to be ready in time when the regulation comes into force in phase one. 11.5% have not even begun to plan. While some allowance can be made for the fact that a number of respondents have later go-live dates, this is somewhat concerning.

    The current lack of readiness across the industry for this new and complex regulation is highlighted by the survey. Both Cappitech and Kaizen Reporting believe industry participants need to prioritise planning, implementation and testing of robust processes for SFTR, to ensure timely implementation.

    Jonathan Lee, Senior Regulatory Reporting Specialist (SFTR) at Kaizen Reporting said, “The findings from the SFTR survey make it clear that many companies are not as prepared as they should be at this stage. In order for firms to be ready by April 2020 there is a need to accelerate their plans and make sure that they allow enough time for testing and implementation.”

    Ronen Kertis, Founder and CEO of Cappitech comments, “Reporting firms who aren’t ready, especially those that haven’t started planning, will need to prioritise this in the coming months. Where possible, an extension of their existing technology may provide an easier and more seamless transition.”

    Reporting firms highlighted a number of additional concerns with SFTR including, most significantly, the issue of UTI matching; 54% of respondents felt they will need to implement UTI matching, with another 33% still considering it.

    40% of survey respondents are also still undecided regarding which trade repository (TR) they are intending to use, bringing additional readiness to test. While tier 1 firms often decide based on board seats and shareholdings, for the rest of the market pricing will be key and most TRs have not yet published detailed pricing data.

    Additional findings from the report include:

    Vendor Selection: This is an ongoing process, with 58% of respondents planning to implement extensions of their current reporting tools.  

    Delegated reporting: 51% of the banks surveyed are committed to providing delegated reporting. “Delegated reporting brings real challenges, not least of which is the need for clients to have control of and access to their reporting data to meet their regulatory requirements. Specific delegated reporting solutions  solve this challenge for banks when they offer delegated or assisted reporting to their clients,” says Mr. Kertis.

    UAT testing: The report also shows that despite its importance, UAT testing has not been fully embraced by the industry. Approximately 54% plan to test in the three months prior to go-live but Kaizen and Cappitech experience proves that many regulatory programme deliveries are delayed, leaving minimal time for testing. This has a knock on negative impact on data quality and regulatory compliance. For the 11% who are planning not to do any testing, and the 7% whose planning only incorporates testing one month before, these risks are greater with Mr. Lee stating, “We would caution that three months will not necessarily prove sufficient to launch such a large and complex reporting regime.”

    For a full copy of the report and to access further findings, please download it here.

    (ends)

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

  • 10 Lessons from industry responses to the ESMA Guidelines Consultation

    While not an exhaustive list, here are our key takeaways from reading the ESMA SFTR Guidelines consultation responses. The overall level of engagement in relation to the consultation was substantial, with 49 files published by ESMA following the consultation period.

    1. Reporting certainty

    A few fundamental questions are key to providing clarity to support a timely build for SFTR reporting. Banks and credit institutions (due to report from April 2020) need answers to some of the these questions well in advance of the self-imposed Q4 2019 deadline set by ESMA.

    In particular, question 25, whether to provide full reports or the delta of changes for modifications and corrections – respondents overwhelming voted for full reporting.

    2. Reportability of intraday market infrastructures executed SFTs

    Which intraday transactions executed on behalf of firms by CSDs and CCPs remain in-scope for reporting? While T2S Auto-collateralisation transactions are explicitly excluded from reporting, does this also cover UK Crest Auto-collateralised repos? Extracting and reporting this data presents unique challenges.

    3. Scope and third country considerations

    The approach to determining the ‘conclusion’ of a transaction by a branch is far reaching and strays from the EMIR definition. It appears to focus on the activities of individuals rather than risk held in the EU. The practical challenges of reporting SFT activities of non-EU entities where traders are supervised by EU branches are immense and likely to lead to significant confusion in relation to areas such as bilateral margining and reuse.

    Concerns were raised where SFTR does not require non-EU AIFs managed by EU AIFMs to be reported (unlike EMIR), while EU AIFs must be reported regardless of whether the AIFM is based in the EU (again unlike EMIR).

    4. Why are buy-sell backs still treated differently?

    ESMA have specified that documented buy-sell backs should be reported as buy-sell backs listing the master agreement, but it is still unclear why the reporting requirements differ from repo. The inability to apply a repo rate, forward breakeven yield or forward price on a buy-sell back is a particular issue.

    5. Is fails reporting really required?

    There has been some confusion about the reporting of settlement fails (general consensus was that perfect settlement would be assumed unless both parties chose to modify a transaction to reflect a default or extended fail).

    6. How to report bilateral variation margining

    Concerns continue to surround the reporting of bilateral variation margins for repo. Given these margin calls at the counterparty portfolio level are entirely separate from the trade level collateral, there should be a separate end of day collateral update report to reflect bilateral margining. They cannot, as ESMA examples suggest, be incorporated with trade level collateral updates.

    7. Failure to transmit Unique Trade Identifiers (UTI)

    The issue of what to do if a counterparty is responsible for providing the UTI fails to provide it in a timely manner for reporting, remains an open question. The real question is how the party subject to late notification of the UTI by their counterparty can be excused from their obligation to submit timely reports.

    8. Availability & consistency of reportable data

    There are many concerns about the availability of data for reporting. The FSB themselves highlighted in their May 2019 document Thematic Review on Implementation of the Legal Entity Identifier that on aggregate only 55% of all financial instruments in scope have an LEI code (representing 78% of outstanding amounts) and that only 11% of all firms that are issuing securities have so far obtained an LEI. Mandating usage of issuer LEIs when firms that use securities as collateral have no contractual relationship with the issuer of the securities, appears a step too far. Solutions are to make the field conditional or apply a standard dummy issuer LEI.

    Other concerns persist around missing official CFI codes, ISIN codes, differences in credit rating assessments between firms and the collateral type field.

    9. The removal of ESCB transactions from the calculation

    Trade associations reiterated that removing ESCB transactions from both sides of estimated re-use calculations will be both difficult and misleading. Nonetheless, this is understood to be an FSB requirement rather than ESMA specific.

    10. Uncertainly around in-scope commodities financing transactions

    A number of trade associations and other respondents commented on the significant uncertainty felt by the commodities trading industry around the SFTR reporting scope of any of their transactions. Concerns were raised that while commodities financing transactions share attributes with SFTs, they are not executed for financing purposes. Disagreement exists as to which transactions constitute repos and which buy-sell backs, in general they were deemed hard to define under existing SFT definitions. There are also concerns that certain commodity transactions, believed to best fit the repo definition use pledge arrangements and not title transfer. Some power and gas contracts may also be reportable under SFTR as well as REMIT. While exclusions are in place for EMIR, they are not in place for REMIT.

    Did you know Jonathan provides CPD-accredited, CISI-endorsed training on the SFTR reporting requirements? Book your place on one of our upcoming courses here or get in touch for bespoke, in-house training.   

  • In the news: David Nowell speaks to Practice Insight on regulatory change

    In the news: David Nowell speaks to Practice Insight on regulatory change

    Senior Regulatory Reporting Specialist David Nowell spoke to Alice Tchernookova from International Financial Law Review’s publication Practice Insight about the future of regulation now that MiFID II has bedded down within the industry. 

    “We have almost reached a stage where we must ask ourselves whether being fully compliant is actually possible,” said David Nowell.

    Read the full article. 

  • Sunny ESMA provides some SFTR relief

    Sunny ESMA provides some SFTR relief

    ESMA published a Consultation paper “Guidelines for reporting under Articles 4 and 12 SFTR,” together with the latest consolidated SFTR validation rules. The deadline for responses is 29 July 2019. ESMA plan to consider feedback during Q3 2019 and the final report is scheduled to be published in Q4 2019. This does not give a lot of time, particularly for the 1st phase of reporting counterparties (Banks), due to go-live in April 2020.

    Nevertheless, ESMA provided clarity on many issues and gave reason to be cheerful as many SFTs executed on behalf of financial institutions through powers of attorney during the course of daily clearing, custody and settlement activities at CCPs, CSDs and ICSDs were ruled out of scope. This has undoubtedly removed a major operational headache from the SFTR reporting requirements and will assist regulatory authorities in gaining a better understanding of the data (as they will be significantly less overwhelmed with noise).

    • In particular, Chapter 5 (General Principles), paragraphs 25-27 rule out any reporting of short term credit lines for custody or CCP clearing.
    • Paragraphs 36-41 rule out reporting of any transactions relating to “fails-curing” services offered by CSDs.
    • Paragraph 43 rules out the need to report any transactions associated with Target 2 Securities Auto-Collateralisation.

    The guidelines also clarify the exclusion of the need to report under SFTR in relation to: Retail client lending (except when it is against an irrevocable trust), private banking & Lombard loans, syndicated lending and other corporate lending for commercial purposes, intermediate give-ups and take-ups (in the execution & clearing chain) and transactions involving emission allowances.

    In further points of clarification:

    • Buy-sellbacks and Sell-buybacks should be reported as such with the appropriate master agreement detail where applicable (overruling the original SFTR regulation) (paragraph 61).
    • Margin Loan reporting only applies to Prime Brokerage business (paragraph 11).
    • Modifications that are agreed but have not taken place should not be reported until the actual modification takes place (paragraph 117).
    • Margin loans – where the value of an existing margin loan hits zero, the transaction should be modified (MODI action type) rather than terminated (ETRM action type) (paragraph 83).
    • Securities lending and borrowing transactions can only involve a single ISIN being transferred between a given pair of counterparties (paragraph 65).
    • Backloading: ESMA advises that they like the idea of reporting all open and term transactions executed prior to the date of application whether they meet the requirements for backloading or not. This approach is seen as operationally simpler for many reporting parties and provides authorities with greater information in relation to variation margining (paragraphs 167-170).
    • When trading with sub-funds, each sub-fund should be treated as a counterparty if they have their own LEI (paragraph 52)
    • For cleared SFTs, each SFT between the CCP, its clearing members and the clients of those clearing members should be treated as separate SFTs with different UTIs (paragraph 53).
    • In relation to Repos, collateralised loans in more than one currency constitute separate SFTs. This doesn’t preclude a single SFT having collateral denominated in multiple currencies though
    • Small & medium sized non-financial counterparties trading with a non EU third country entity must either trade with an entity that has been granted equivalence (in which case there is no reporting obligation under SFTR), else they will need to delegate or self-report the transaction/s (paragraph 93).
    • Execution by a branch was clarified to cover the following: a) for a client in accordance with a discretionary mandate given to it by the client; b) where the branch has supervisory responsibility for the person responsible for the investment decision concerned; c) where the branch has supervisory responsibility for the person responsible for execution of the transaction; d) where the transaction was executed on a trading venue or an organised trading platform located outside the Union using the branch’s membership of that trading venue or an organised trading platform (paragraph 102).
    • Counterparties should not report the LEI of the CSD in which they are either a direct or indirect participant (paragraph 122) in the CSD participant field.
    • ESMA acknowledged that updating valuations of securities on loan or used as collateral may not be possible where pricing becomes stale. This can affect suspended shares and some illiquid fixed income securities. In these instances, reporting parties should use contractually agreed values and only update them if new price information becomes available (paragraph 155).
    • ESMA advises counterparties should always use official sources for CFI codes. Those who felt that it would be sufficient to just populate the first 2 characters are likely to be disappointed as ESMA states that X should only be used when a character is not applicable (paragraph 163).
    • Non-bank entities are permitted to start reporting earlier than their date of application if they find it easier (paragraph 188).   

    The consultation also contains an extensive set of sample reports for many different scenarios, detailing how each of the 4 reporting tables should be populated. Once we’ve had the opportunity to review these samples and the latest trade repository validation rules, we will produce a follow-up blog.

  • Lack of training results in transaction reporting breaches

    Lack of training results in transaction reporting breaches

    One of the most interesting statements from the FCA Final Notices following the recent fines for MiFID transaction reporting breaches concerned the general lack of expertise around transaction reporting in the industry. The firm impacted was clearly trying to do the right thing, but was hampered by “…a scarcity across the Firm and the industry of personnel with the expertise and systems knowledge required both to implement the enhanced controls and remediate the issues identified during the course of the project”¹ 

    It is difficult to understand why this lack of expertise should still afflict such an important area of compliance. Whilst it may not appear to be the most glamourous area of regulation, the FCA has shown a continued willingness to take action against firms for breaches. Many of the errors highlighted by the FCA appear to have been simple mistakes in the interpretation of the reporting requirements and might have been avoided through a more effective training programme. It should also be remembered that these fines relate to the old MiFID transaction reporting which is relatively simple compared to the greatly increased scope and complexity of the current MiFIR transaction reporting regime.

    Help is at hand

    At Kaizen, we believe effective training is an essential element in ensuring complete and accurate transaction reporting. We offer a half day CPD-accredited training course, endorsed by the Chartered Institute for Securities and Investment (CISI), which gives candidates a core understanding of the transaction reporting requirements and the fields that comprise a transaction report. The course can be taken at Kaizen HQ or at your own offices and is accompanied by an exam which enables you to demonstrate your understanding of the reporting requirements. Similar courses are available for EMIR trade reporting and SFTR. Visit our training page for further details and to book your place on one of our upcoming scheduled dates. 

    Are you a Transaction Reporting guru? Why not take part in #TransactionReportingTuesday over on LinkedIn.

    Every Tuesday, on the Kaizen LinkedIn we will be publishing a MiFIR Transaction Reporting question from our training exam. The answer will be posted a week later along with a new question. 


    ¹ FCA Final Notice to Goldman Sachs

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

  • Just a second…?

    Just a second…?

    MiFID II introduces the requirement to synchronise the business clocks of trading firms and their customers so that timestamps recorded are standardised across the industry. The idea is that regulators will be able to monitor for market abuse more accurately. Trading systems will need to synchronise themselves to a common source of time. But how will they do this? And what are the implications?

    On the back of the FCA’s MiFID II conference this week we were with the National Physical Laboratory (NPL) to find out. Their workshop, “UTC traceability for the global financial sector, realisation of a unified common clock” attempted to answer some of these questions. Taking the front seat was MiFID II’s RTS 25, which outlines the draft regulatory technical standards on clock synchronisation. The direct impact of this piece of regulation was apparent from the range of professionals from all aspects of the industry including financial firms, exchanges, consultants and scientific organisations.  Most notable was the presence of ESMA and the Bureau International des Poids et Mesures (BIPM) as both have a heavy hand to play in RTS 25. We suggest firms take a look at Table 2 in the Annex of RTS 25 which sets out the level of granularity applicable to their trading activities. It is important that firms are clear on what is expected of them and should be in advanced discussions around the technology to be adopted to meet the new regulatory obligations.

    Here are the key points we took away from the conference:

    1. The industry was concerned about deploying GPS as a means to synchronising their business clocks. It was felt that although it meets the regulators’ authorisation of “satellite systems” as a credited tool, it does not provide traceability back to UTC.  This was further supported by BIPM who claimed that due to the irregular leap second lag incurred through GPS signals, the only credible solution was a direct feed from a National Measurement Institute (NMI). ESMA was clear that both options remain and stood firm, stating that they must be realistic in what they ask from firms and not show any bias to any provider.
    2. The industry feels this needs to be part of the Level 3 discussions but it seems very unlikely that GPSs will be scrapped. We advise all firms to gear up based on the Level 2 RTS 25.
    3. The industry also showed concern around implementing the required technology and sought r advice from the regulator. However, ESMA’s view was very clear in stating it is up to the firm to implement what is required.
    4. ESMA highlighted the importance of firms reviewing their transparency systems on an ongoing basis once deployed. The type of review required is not clarified within the RTS, however we would recommend both internal and third party checks to ensure obligations are met.
    5. FIX is planning to update all versions of its protocol (back to FIX 4.2) to capture the accuracy of seconds in timestamps to 6, 9 or 12 decimal places.
    6. BATS Chi-X Europe is considering providing NPL time source feeds to its clients via a PTP feed if there is considerable demand.

    All in all, the industry is aware of the challenge in implementing this step and the effects it will have on their infrastructures. However, having the same “watch” is very much welcomed by all concerned, agreeing it will lead to better data publication and reporting, thus a more transparent industry as a whole.

    What do you think?  We would welcome feedback or comments about the issues raised in this blog and more broadly, about the MiFID II draft technical standards.

    We’ll be releasing further blogs around the finer details of MiFID II so stay tuned!

    In addition to our testing services, we are offering training courses for firms to help them prepare for the reporting elements of MiFID II. Please contact us to find out more. 

    Read our earlier blog on our reaction to the release of the draft RTSs.

  • ESMA writes the control section of your transaction reporting BRD…

    ESMA writes the control section of your transaction reporting BRD…

    ESMA has published its eagerly awaited regulatory technical standards (RTS) for MiFID II for consideration by the European Commission.

    Chapter 7, Market Data Reporting (RTS 22) outlines the obligations for transaction reporting. And for those responsible for drafting their firm’s control section of the Business Requirements Document (BRD) Article 15 of RTS 22 makes their job very easy! Recent regulation, whether it be the Dodd Frank Act (DFA) in the US or EMIR in Europe, has become increasingly prescriptive of the controls expected of participating firms. Article 15 takes this prescriptive nature into a different league, placing testing and reconciliations front and centre.

    MiFIR (Article 26(7)) requires firms to verify the completeness, accuracy and timeliness of the transaction reports they submit. RTS 22 expands on this and explains that complete and accurate reporting data is essential to market surveillance and outlines how that is to be achieved.

    Under the first section of Article 15 there are the usual requirements relating to the security and functionality of data and measures to enable timely resumption of reporting when reporting systems go down and measures to identify errors and omissions.  More specifically there is requirement on firms to have mechanisms to avoid duplicate reporting and under reporting.

    Whereas over-reporting is tolerated under current obligations, reporting transactions where there is no obligation is not permitted and Article 15 says firms will need to have mechanisms in place to identify over-reporting.  Over-reporting is the submission of a transaction report where it is not required under the reporting rules.  This can be reporting a trade on an instrument that is not reportable or reporting a transaction on a non-reportable event such as dividend reinvestment.

    When firms become aware of any of these types of errors or omissions they need to be reported to the relevant competent authority. To that end ESMA mandates not only reconciliations but specifies the data sources and fields to be included; reconciliations should be between front office trading records and information contained in transaction reports and checks should be in place to prove the timeliness of reports and the accuracy and completeness of all the individual data fields.

    In tandem with regular reconciliations, Article 15 states that firms are required to put in place a testing methodology and approach for their reporting processes. The multimillion pound fines issued by the Financial Conduct Authority for transaction reporting breaches over the last five years have often been on transactions which have been reported as valid and been through some form of reconciliation process but ultimately have still breached Chapter 17 requirements of the supervisory manual.  It is these breaches that your testing approach must be able to identify.  The often piecemeal, sample-based testing that is common in firms today will not be satisfactory.

    Kaizen Reporting’s testing approaches are setting the industry standard and will enable you to meet your MiFID II requirements efficiently and cost effectively. We combine unrivalled regulatory knowledge with the latest data analytics to provide the highest level of confidence in transaction reporting.