A quarterly report to the financial regulator means days of collecting data from Sage, the core system and registers into Excel and checking it by hand. AI assembles a draft from your template and flags fields where data disagrees or is missing, and finance and compliance managers review and approve.
Built for ISO 27001NIS2 DORA
Before each reporting period, the finance team exports balances and expenses from Sage, payment volumes and customer counts from the core system, the incident count from the register in SharePoint and complaint statistics from Dynamics 365, and puts them into the financial regulator's report form in Excel. Some numbers do not match, because the systems count on different dates or in different currencies, and reconciliation in spreadsheets begins. For the internal risk report to the board, the same data is collected again with a different cut. In the last week before the deadline, finance and compliance managers work evenings, and an error usually hides where a number was retyped by hand.
The solution connects to Sage, the core system and the incident register with read-only access through agreed queries, via an API, a database or a periodic export, depending on your version. Claude, running in an Amazon Bedrock EU region, puts the data into your report template, calculates derived indicators using the documented formulas, compares them with the previous period and flags fields where Sage and the core system disagree, data is missing or a change is unusually large. Every number has a link to its source query. The draft appears in SharePoint, the finance manager and the compliance officer review, correct and approve it, and submission through the regulator's reporting portal stays in their hands. Data does not leave the EU, and every query and change is logged in line with DORA requirements.
Four steps from input to a record in your system, with human approval wherever there is risk.
On a calendar schedule or when a manager starts it, the solution runs pre-agreed read-only queries against Sage, the core system, the incident register in SharePoint and the complaint cases in Dynamics 365 for the reporting period. The query text is approved by your finance department and does not change without your knowledge.
The model puts the data into the fields of the financial regulator's report form, calculates derived indicators using the formulas you documented and compares them with the previous period. Fields where Sage and the core system disagree, data is missing or a change is unusual are flagged with an explanation and a link to the source query.
The draft appears in your SharePoint environment with flagged fields. The finance manager and the compliance officer review it, correct it, adding a comment to each changed field, and approve it. Submission through the financial regulator's reporting portal is done by a person in the usual way; the solution does not upload the file there.
If Sage or the core system is unavailable or the period is not yet closed, no draft is created and the responsible person gets a notification. The log keeps the queries, results and all changes. When the financial regulator changes the form or you change an internal template, we update the fields and formulas.
Read-only access to Sage, the core system and registers, with approved queries for every field of the financial regulator's report.
Templates for your periodic regulatory and internal risk reports, with documented formulas and a source map down to the specific system.
A draft in SharePoint with flagged mismatches between Sage and the core system, changes and a place for comments, approved by two managers.
A log of queries, changes and approvals for audit, and template updates when the financial regulator's forms or the Sage structure change.
Claude via API in an Amazon Bedrock EU region + read-only data from Sage, the core system and registers. We connect to Sage through a database or an export, and to the core system through an API or a periodic file export, depending on your version; we choose the method after a check. Learn more about this service and its limits on the service page.
No. The solution prepares a draft and flags doubtful fields, while a finance or compliance manager approves it and submits it through the regulator's reporting portal. The log shows who changed and approved the draft and when.
Yes. From Sage we take data only through read-only database queries or from a periodic export, and from the core system through an API or an export, depending on the version. Calculations follow the formulas you documented, and the model puts in the results and explains the changes, so every number can be checked in a few minutes.
The model runs in an Amazon Bedrock EU region, access to Sage and the core system is read-only, and all queries and changes are logged. We add the solution to your register of ICT third-party providers and describe it in the risk assessment.
Complaints arrive in a shared Outlook inbox, ICT incident reports come from monitoring and Teams, and deadlines run from receipt.
What is the contract termination procedure, when is enhanced customer due diligence required, who approves an exception: staff ask colleagues in…
Where is my payment, what is my limit, how much does a transfer cost: the answers are already in your core system.
The customer passes the Onfido or Sumsub check, but someone still retypes the business register extract, proof of income and beneficial owner…
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
