Service · Web development

Custom regulatory reporting platform development.

A custom platform that automatically generates compliance reports from your source systems and submits them to DNB, AFM, ECB or any other supervisory authority. With a solid data foundation, an audit trail for every figure and a review flow that enforces the four-eyes principle.

XBRL & SBRDNB DLR submissionData lineageFour-eyes review

Regulatory reporting is no longer a spreadsheet job.

Regulatory pressure increases every year. Banks, insurers, pension funds, asset managers and, increasingly, energy and large industrial companies must submit standardised reports at fixed deadlines. These are often in XBRL, iXBRL or SBR format, often with in-depth validations, and always with the expectation that the figures are correct and traceable to the source.

Since 2015 we have been building custom software for sectors where that data foundation never fits one-to-one into an off-the-shelf package. No loose macros in Excel, no manual copy-and-paste from the ERP, but one continuous line from source data to submitted report, with data lineage per line item, a review flow per report and an audit trail that records every change.

The difference between a good and a bad reporting platform is rarely in the export layer. Generating XBRL or SBR is a solved problem. It lies in everything that comes before: how cleanly the source data is loaded, how transparent the calculations are, how quickly a variance can be traced back to the transaction, and how easily an internal audit can work through your figures. That is where the value lies, and that is where we spend most of the sprint budget.

Three flavours of regulatory reporting platform.

It depends on your sector, the number of reports and how deep the integrations with source systems need to go. We advise on which form fits in the first conversation.

Compact project · fixed sprint budget

Reporting add-on for your existing stack

A module that plugs into your current data warehouse or ERP. It calculates the figures according to a specific reporting template (Solvency II QRT, a COREP statement, a CSRD annex), generates the XBRL or SBR file and offers a review flow before you submit.

One report typeXBRL/SBR exportReview flowAudit log
Mid-sized project · fixed sprint budget

Reporting platform with a data foundation

A central reporting warehouse that pulls data from multiple source systems (ERP, core banking, custodian, transaction system, accounting) and builds a set of reports on top of it. Including variance analysis, dashboards for submission deadlines and compliance mapping so that one control feeds multiple reports.

ETL & warehouseMultiple reportsData lineageCompliance mapping
Larger project · fixed sprint budget

Enterprise reporting platform

A mission-critical platform with deep integrations to regulator portals (DNB DLR, ECB SDW, EBA, AFM, NZa), four-eyes sign-off per report, automated submission, and variance analysis against historical periods. For organisations with dozens of reports per year.

A sanctions hit does not call for periodic reporting but for a notification at the moment it happens. See Sanctions Act software.

DNB DLR submissionFour-eyes sign-offVariance analysisMulti-entity

What we typically build in a regulatory reporting platform.

The building blocks differ per sector, but this is the toolbox we draw from, combined into a platform that fits your reporting landscape.

Data foundation

ETL and reporting warehouse

Ingestion from ERP, core banking, CRM, accounting, transaction systems, custodians and brokers. A clean data model with version history so that every period can be reproducibly recalculated.

Calculations

Reporting templates per type

Formulas and validations per report: Solvency II QRT, COREP, FINREP, NICA, MiFID II transaction reporting, SFDR, EMIR, IFRS 9, BCBS 239, EBA stress testing, FATCA, CRS, CbCR, BEPS Pillar 2, SBR tax.

Export

XBRL, iXBRL and SBR

Generators for the current taxonomy years. Validation against the official schemas before the file enters the submission flow, so that technical rejection on the portal is virtually ruled out.

Submission

Integrations with regulator portals

Where APIs are available: direct submission to DNB DLR, ECB SDW, AFM, EBA, NZa. Where that is not possible: a validated file ready in the portal, with a log record of who uploaded what and when.

Workflow

Data entry, review and sign-off flow

Preparer, reviewer and approver roles with clearly defined permissions. Including notifications, deadlines per report, and a dashboard that shows, for each cycle, which reports are on track and which need attention.

Control

Variance analysis and data lineage

For every figure in the report you can see which source transaction, which calculation, which previous value, and which explanation was given for the change. Essential for internal and external audit, and for your own quality assurance.

Sectors in which we build regulatory reporting.

Reporting pressure runs through almost all regulated sectors. Here is a selection of the types of organisation we work with, and the reporting landscape that goes with them.

Financial sector

Banks and payment institutions

COREP, FINREP, NICA, MiFID II transaction reporting, BCBS 239 data quality, IFRS 9 expected loss, EBA stress testing and ECB reporting. Often combined with a deep core banking system and multiple custodians.

Insurers

Solvency II and international reporting

Solvency II QRT, ORSA substantiation, FATCA, CRS and CbCR. With platforms that bring the actuarial calculation and the reporting layer into a single lineage trail, so the external auditor can easily follow the figures.

Pension funds

DNB statements and Wtp reporting

The statements to DNB (the Dutch central bank) plus the additional reporting introduced by the Future of Pensions Act (Wtp). With integrations to the pension administrator and the asset manager where the investment data comes from.

Investment management

SFDR, EMIR and MiFID II

SFDR sustainability templates, EMIR transaction reporting, MiFID II best execution. For asset managers and fund houses that work with multiple brokers and custodians and want to unlock the data before they report on it.

Energy, industry and multinationals

ACM, EU Taxonomy, BEPS and CbCR

For energy companies: ACM/CBS reporting and the EU Taxonomy. For multinationals: BEPS Pillar 2, CbCR and transfer pricing documentation. For manufacturing: REACH and RoHS, where product data has to meet compliance requirements.

Healthcare and the public sector

NZa, IGJ and Woo

For healthcare providers: NZa billing reports, IGJ reporting and EHR connections. For government: Woo (Open Government Act) reporting and annual report requirements that need to be underpinned by a reporting layer rather than compiled by hand.

What you get at the end.

A production-ready reporting platform plus everything around it, so you can manage and extend it yourself, together with your compliance and IT team.

  • The reporting platform itselfProduction and staging environments in your cloud (GCP, AWS, Azure) or with us, with encryption in transit and at rest.
  • Data foundation and lineage layerETL from your source systems, a central reporting warehouse, and a lineage overview that shows, for each figure in the report, where it comes from.
  • Report templates per typeCalculations, validations and XBRL/iXBRL/SBR export for the reports relevant to your entity. Templates are version-proof, so you can introduce new taxonomy years.
  • Codebase and documentationFull source code, build instructions, architecture diagrams and a functional description per report (which formula, which source fields).
  • Admin guide for compliance and ITHow a report is submitted, how a variance is investigated, how roles are assigned, and how the audit log is read by internal and external auditors.
  • Managed service contract (optional)Ongoing maintenance: new taxonomy years, adjusted validations, integrations, monitoring and security patches. Fixed monthly price, four response-time levels.
Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

When a custom platform is the right choice.

Four patterns in which clients come to us. If you recognise one, we would be glad to talk further.

Off-the-shelf package does not fit

OneSumX or Adenza is too heavy

Large enterprise packages such as Wolters Kluwer OneSumX, AxiomSL/Adenza or Moody's BankBeyond suit the very largest institutions, but for mid-sized banks, insurers and pension funds they quickly become a clumsy solution for a specific set of reports.

No data foundation

The figures are pulled together manually

Many reporting projects start not with the report but with the data. If your figures currently travel from controllers to compliance in Excel files every month, a shared data foundation, with lineage, is the first step.

New obligation

CSRD, DORA or MiCA is coming

Reporting requirements are changing faster than most standard packages can keep up with. For new obligations such as CSRD, DORA incident reporting or MiCA market data, a custom solution is often the fastest route to something that works.

Integration depth

Many source systems, one report

When a report combines data from core banking, custodians, brokers, transaction systems and ERP, standard connectors reach their limits. A platform built around your architecture can handle the variance analyses and data quality checks on top of that integration properly.

How a reporting project works.

1

Introduction and scoping

A conversation with your compliance, finance and IT teams in which we map out which reports are in play, which source systems you have, and where the pain is right now. By the end, we know whether an add-on is enough or whether the data foundation needs to come first.

2

Data model and report analysis

We map the reporting templates (COREP, FINREP, Solvency II QRT, SBR tax, ESG annexes) to your source fields. For each figure we record the formula, the validations and the exceptions. That document later doubles as your audit evidence.

3

Building in sprints

A working build every two weeks. Compliance officers, controllers and internal audit test alongside us on real (anonymised) data. The first report is ready after a few sprints, and further reports are added in phases.

4

Parallel run, rollout and maintenance

We run at least one reporting cycle in parallel with your current process. Differences are investigated and documented. Then we go live, with a maintenance agreement covering new taxonomy years and further development.

Frequently asked questions.

What clients usually want to know before we start.

Do you replace Wolters Kluwer OneSumX, Adenza or another enterprise package?
For the largest banks and insurers already running fully on OneSumX, Adenza/AxiomSL or Vermeg: no, that would not be wise, as those packages are built for exactly your scale. We more often build custom software where a standard package doesn't fit: for mid-sized organisations, for specific reports alongside the main package, or for sectors where standard software isn't available (such as parts of energy, healthcare or crypto).
How can I generate compliance reports automatically?
The core is a data foundation into which source figures are loaded with lineage, plus calculation templates per report that run on that foundation. With every run, the XBRL or SBR file is generated, including validations. The reviewer sees which figures changed compared with the previous period (variance analysis), signs off in a four-eyes flow, and the file can then go to the regulator. So: fully automated, with human sign-off.
What do you mean by a "data foundation for compliance and reporting"?
A solid data foundation is the only lasting solution for compliance reporting. In practice, that means a centralised reporting warehouse, with standardised ETL from your source systems, data quality checks at load time, and data lineage so that for every figure in a report you can see which source transaction lies behind it. Without this foundation, every report becomes another manual reconciliation.
Do you support SBR, XBRL and iXBRL?
Yes. SBR is the standard in the Netherlands for tax filings and annual accounts submissions; XBRL and iXBRL are used for the European taxonomies (ESEF, EBA, EIOPA). We build report generators that know the right taxonomy version, run validations and prepare the export file for the submission portal.
Can you submit automatically to DNB DLR, ECB SDW or the AFM?
For DNB DLR (Digital Reporting Portal) and similar portals, we build a direct submission integration wherever the supervisor technically allows it. Not all portals offer an API for automated submission; in that case, the platform provides a validated file ready for manual upload by the authorised user, with a log of the upload confirmation.
What is the difference from DORA compliance, KYC or CSRD software?
Regulatory reporting is specifically about the legally required reporting to supervisors. Alongside it, we also build DORA compliance software for operational resilience, KYC/AML software for customer onboarding, and CSRD/ESG reporting software for sustainability reporting. The platforms can feed each other through a shared data foundation.
How do you handle the audit trail and the four-eyes principle?
Every change in a reporting cycle, whether a recalculation, a manual correction or a sign-off, is recorded with the user, timestamp, and old and new value. The four-eyes flow is built into the submission process as standard: a preparer drafts, a reviewer approves and an approver signs off. External auditors get read-only access to the audit log for their review.
How long does a project like this take?
For a single report type with a reasonably clean source system, a working platform is achievable in a few sprints. For a multi-report platform with a data foundation, we plan for a project of several sprints, often rolled out in phases so the first reports are already running while the next ones are being built.
What determines the cost of a reporting platform?
The biggest factors are the number of reports, the complexity of the calculations per report, the number of source systems the data comes from, and how clean that source data is. Ask us for a no-obligation estimate based on your specific situation; it will give you more direction than a general price range.

Talk to us about your regulatory reporting platform.

A no-obligation introductory call of half an hour. We listen to which reports you currently produce, where it chafes and which new obligations are coming. We then give you direction you can actually use, even if that direction isn't "build custom software". Also take a look at management reporting if your need is internal, or enterprise software development for a broader project.

Edit content