A new version of ESMA guidelines, an updated decision of the financial regulator, changed stock exchange rules, a changed internal policy: the compliance officer reads the whole document to find a few changed clauses. A private model in Lithuania (EU) flags what changed and links it to your SharePoint procedures that may need updating.
Built for ISO 27001NIS2 DORA
The compliance officer in an investment management firm tracks EU regulations and ESMA guidelines, decisions and letters of the financial regulator, stock exchange rules and internal policies and procedures. When a new version arrives, it has to be read in full and compared with the previous one, to work out which clauses changed and to decide which internal procedures are affected: suitability assessment, trade approval, periodic reports to the regulator, disclosure to clients. That is a day of reading for one document, and there are dozens of documents a year. Sometimes a change is noticed only in a query from the regulator or during an internal audit.
The solution runs on a private model in the MDP CLOUD GPU cloud in Lithuania (EU), so documents do not leave our data centre and do not reach any external platform. The flow picks up a new document version from the compliance mailbox where notices from the financial regulator and the stock exchange arrive, from the SharePoint policy library or from the legislation sources you specify, and compares it with the previous version in your archive. The model flags changed, new and deleted clauses, summarises the substance of the change and links each clause to the records in your procedure register, in a SharePoint list or an Excel table, where that topic is described. The compliance officer gets a list of changes in Teams with links to both versions and the affected procedures, instead of the whole document again. The officer decides whether and how to change a procedure. Every comparison stays in the log.
Four steps from input to a record in your system, with human approval wherever there is risk.
The flow watches the compliance mailbox that receives letters from the financial regulator and stock exchange notices, the policy library in SharePoint and the legislation and ESMA sources you specify. The new version is assigned to the document in your archive, and the previous version is retrieved for comparison. The document is passed to a private model in the MDP CLOUD cloud.
The model compares the two versions clause by clause, flags what was changed, added or deleted and briefly describes the substance of the change: a deadline, a threshold, a new obligation, a changed definition, a new field in a regulatory report. Editorial corrections that do not change the meaning are flagged separately so they do not get in the way.
Each change is linked to the records in your procedure register, in a SharePoint list or an Excel table, where that topic is described. The compliance officer gets a list in Teams with links to both versions and the procedures, marks which ones are really affected and creates tasks for the update. What to change and how is for the officer to decide.
If the previous version is not in the archive, the model prepares only a structured summary and says so. Comparisons and decisions are in the log for internal audit. We maintain the model and the GPU environment in Lithuania (EU), and we extend the list of sources (financial regulator, ESMA, stock exchange) and the procedure links when your register changes.
A model in the MDP CLOUD GPU cloud in Vilnius, with no external APIs, accessible only to your compliance team through Entra ID.
A versioned archive of policies and legislation in SharePoint, with automatic intake of new versions from financial regulator, ESMA and stock exchange notices and from the sources you specify.
A list of changed clauses with summaries, links to both versions and the affected procedures from your register in SharePoint or Excel.
A log of comparisons and decisions, maintenance of the model and environment, and updates to the source list and procedure links.
A private model in the MDP CLOUD GPU cloud in Lithuania (EU) + a document flow from financial regulator, ESMA and stock exchange notices by e-mail and from the SharePoint policy library, with the procedure register in a SharePoint list or Excel. We connect to the sources through an e-mail flow, file export or an API, depending on the version, and we choose the method after a check. Learn more about this service and its limits on the service page.
No. The model flags the changes and suggests links to procedures, and the compliance officer decides whether and how to change them. The officer's decisions and tasks are written to the log.
Yes. We read the procedure register from a SharePoint list or an Excel table in an agreed folder, notices from the financial regulator and the stock exchange from the compliance mailbox where they already arrive, and ESMA documents from the sources you specify. If the register is in Dynamics 365 or another system, we connect through an API, file export or an e-mail flow, depending on the version.
Internal policy and risk documents are confidential, and DORA requires you to manage ICT third-party risk. A model in the MDP CLOUD data centre means the documents stay in Lithuania (EU) and are not in an external provider's chain. You decide which sources are tracked.
What is the limit per issuer, who approves a trade above the limit, how do I declare a conflict of interest: the answers are in the policies in…
In a day, an analyst receives more reviews, issuer reports and prospectuses from Bloomberg Terminal, LSEG Workspace and e-mail than anyone can read.
After a client meeting, the manager writes notes into Salesforce or Dynamics 365 from memory, and some of the agreed actions get lost.
At the end of the month, the portfolio manager prepares dozens of reports and letters from the same Euroclear statements and Excel tables.
This service is delivered by specialists with valid international certifications. Their expertise is confirmed by independent organisations, not by us.
AI systems are deployed with protection against data leakage and model abuse.
The AI security programme and its controls are managed following the ISACA methodology.
AI risks are identified and managed like any other IT risk.
We reply within 1 business day
