Set the context
Select tenant, report type, reporting date and taxonomy version clearly.
Software · RegTech
From reporting form to a valid XBRL filing.
A multi-tenant SaaS platform for a specialised banking technology provider translated complex regulatory logic into an understandable self-service process.
Reportingdelivered for the Bundesbank and European Central Bank
SaaSmulti-tenant platform from Excel import to XBRL export
2023–presentproduct, operation and security as one continuous lifecycle
Starting point
Regulatory reporting logic needed to be usable without a dedicated XBRL infrastructure.
Smaller banks and financial services institutions face the same formal reporting requirements as larger market participants. Taxonomy versions, data points, dimensions, validation rules and national filing rules therefore had to be translated into an economical and understandable workflow.
A technically generated file alone is not enough. Reporting date, taxonomy version, input data and validation logic need to be consistent and produce an instance that can technically be filed with the supervisory authority.
PERCEL role
Product, business logic and platform connected from the ground up.
- designed the multi-tenant SaaS product and user process
- translated EBA taxonomies into understandable reporting forms
- delivered regulatory reporting for the Bundesbank and European Central Bank
- connected Excel import, data entry and reporting history
- integrated a validation engine and traceable error handling
- included national filing rules and test submissions
- implemented XBRL generation and export as a self-service process
- supported pilot clients, tenant rollout and business and technical testing
The product process
Create. Validate. Export.
The technical complexity remained inside the system. Users received a traceable route from the report to a file ready for submission.
Enter data
Edit data in the form or import it from Excel in a controlled way.
Validate
Check taxonomy and filing rules and resolve errors traceably.
Export
Generate an XBRL file and prepare it for supervisory filing.
Product maturity
Test filings and pilot use brought the product to a robust operating state.
Feedback from test submissions, business testing and pilot use was consolidated in a prioritised issue log. Documented points included the frontend, data import, business functions, validation and the technical submission capability of the generated XBRL files.
New taxonomy versions, tenants, training, support and rollout were planned and supported as parts of a multi-year product lifecycle.
Operation and security
Operation, review and further development were managed as one lifecycle.
An independent grey-box web application assessment documented prioritised findings and measures. The application and its software dependencies continued to be monitored; available updates were assessed based on risk and possible regressions.
The documentation covers security assessments, recommended measures and continued vulnerability monitoring. The handling status of individual findings is considered separately.
Role today
PERCEL’s operational software background provides the technical foundation. Today, PERCEL deliberately no longer develops software itself. Small specialist teams are assembled to fit the task. PERCEL keeps product logic, requirements, quality assurance, handover and operation connected. This keeps decision paths short, responsibility clear and the solution close to the actual working reality.
Transferable value
Three worlds were made compatible in one product.
The particular contribution lay in translating between European regulation, technically demanding XBRL and the working reality of reporting institutions. This interface capability is equally relevant to other regulated software, data and transformation projects.
Regulated business logic?