Supervisory reporting · COREP · FINREP · DORA
Every cell
accounted for.
Sigill is the reporting layer between financial institutions and their supervisors. Every datapoint validated against the EBA rulebook, every submission sealed.
Your figures, the frameworks, the national forms — three tracks to keep aligned.
One platform. The same figure, right in every report.
From first figure to sealed filing
Enter once
In the grid, or in a macro-free Excel template your team already understands — uploaded values land in the right cells, keyed by datapoint.
Validate before the supervisor does
The full EBA validation rule set, with the EBA's own severity levels. Blocking findings point at cells, not at line numbers in a rejection file.
Seal and submit
One click produces an xBRL-CSV report package that follows the EBA filing rules. On submission the report is sealed — the figures and institution data are frozen, exactly as filed.
| Row | Item | 0010 · Amount |
|---|---|---|
| r0010 | OWN FUNDS | 1 284 906 023 |
| r0015 | TIER 1 CAPITAL | 1 187 494 773 |
| r0020 | COMMON EQUITY TIER 1 CAPITAL | 1 090 083 523 |
| r0030 | Capital instruments eligible as CET1 Capital | 742 500 000 |
| r0130 | Retained earnings | 347 583 523 |
| r0180 | Accumulated other comprehensive income | 12 706 490 |
| r0200 | Other reserves | — |
The template, as the supervisor sees it
Rows, codes and headings are rendered straight from the EBA Data Point Model — the report view is the template. Values are keyed by datapoint, so a figure entered once is right in every template that shares it.
Validation runs while you type: sign rules, datatypes and the EBA's own consistency checks, pinned to the exact cell. Nothing waits for a rejection letter.
More than one person on the same return
Access is granted per report type, not per account. The people working on the anti-money-laundering return never need to see COREP, and the other way round. The levels build on each other — whoever may approve may also write and read.
Read
Follow the work and read the finished return. Management, the board and internal audit get access without anything being changed on the way.
Write
Enter values and generate the report file — everything up to the point where the return is ready to be filed.
Approve
Seal the submission. Put this level with someone other than the person who filled it in and every return is reviewed twice — or with the same person, so a one-person finance function is never stuck.
- Two-factor on every accountRequired at first sign-in. It is not a setting anyone can switch off.
- An audit trail that cannot be erasedEvery change is logged with who, when, and the value before and after. The product writing the trail can neither alter nor delete it.
- Users are includedPricing follows the reporting, not the number of seats. Inviting a colleague to review should never be a cost decision.
Three ways to become a customer
They differ in how much you automate and in who is filing — not in how correct the submission is. The engine underneath is the same in all three.
- Web & Excelavailable
Key figures in the report view, or fill a macro-free Excel template your team already understands and upload it — values land in the right cells, keyed by datapoint, not by position in a sheet. Nothing to integrate: you can file your first return without your systems changing at all.
- APIin development
Bring it in-house. Deliver datapoints straight from your core, ledger or consolidation systems and get back a validated, sealed report package — same engine, same rules, same severities. Suits institutions where the numbers already live in a system and the reporting work is reconciliation, not data entry.
- Partner licenceby agreement
For advisory firms filing on behalf of client institutions, and for software vendors building reporting into a product their customers already use. Many institutions under one agreement, strictly separated, priced per client institution. A licence is not a tier of the API — it sits on top of either route above, and an advisory firm may work entirely in the report view.
Built on the rulebook itself
Sigill does not re-implement supervisory reporting — it derives it. Templates, datapoints, validation rules and module versions come from the EBA's own Data Point Model, release by release.
See it on your figures- DPM-derivedTemplates and rules generated from the EBA Data Point Model — never hand-coded per template.
- Arelle-validatedFull taxonomy validation with the processor supervisors themselves use.
- EBA severityBlocking vs. warning straight from the EBA's validation rule list, filtered by your reference date.
- Live validationSign rules, datatypes and EBA consistency checks evaluated as you type — the full server run confirms, it does not surprise.
- xBRL-CSV outReport packages per EBA Filing Rules — file naming, structure and filing indicators included.
- National returnsThe returns each market layers on top of the EBA frameworks, carried from the same figures — a reporting year is only complete when both halves are.
The same product carries a two-person finance team and a group reporting function. The complexity is ours to absorb — that is the service.
Book a pilot
A free demo on your own figures: bring one reporting period, and we generate a real report package from it — validated, cross-checked and sealed. Before any commitment.