Skip to content
SQACE SQACE

Regulatory reporting

Check supervisory reports before they are submitted.

SQACE verifies the business correctness of supervisory reports against an independent rulebook, from data delivery to the reported figure, with an audit-proof trail per reporting date.

30 minutes, on your own use case.

The problem

The report is valid, but are the figures correct?

Regulatory reporting routes are long: from source systems through preparation and aggregation into the reported figure. What usually gets checked is the format and technical completeness of the report, not whether the reported figure follows correctly from the input data.

Errors in scoping, classification or aggregation then only surface in reconciliation with the supervisor or at the next special audit. Explaining things to the examiner becomes laborious, because the derivation of the figure has to be reconstructed after the fact.

The SQACE solution

Recompute the reported figure against an independent rulebook.

SQACE independently recomputes the business reporting requirements on the input data and compares the result with the produced report. Deviations are classified and traced down to the causing individual record.

The rules are written in business-readable language, so business, regulatory reporting and internal audit work against the same versioned reference. Every run belongs to a reporting date and is reproducible.

Screenshot: Rule-breakdown Dashboard
Drill-down from the reported figure to the causing record.

Scenarios

Where reporting teams use SQACE.

Safeguard reported figures before submission

Before sending to the supervisor, SQACE checks whether the figures follow correctly from the input data. Anomalies appear with a reason and the triggering record.

Verify data delivery into the reporting route

Deliveries from upstream systems are checked against business scoping and classification rules before they flow into aggregation.

Establish reporting-date reproducibility for special audits

For every reporting date a complete record exists: input data, rulebook version, expected, actual and classified deviation, all without after-the-fact reconstruction.

In concrete terms

  • Errors in reporting logic become visible before submission, not only in supervisory reconciliation.
  • The derivation of every figure is documented defensibly per reporting date.
  • Reusable rulebooks across reporting periods and areas.

At a glance

Aspect With SQACE Status quo
Object of review Business correctness of the figure Format and completeness of the report
Derivation Traceable down to the individual record Reconstructed after the fact
Reporting date Reproducible per rulebook version Hard to reproduce
Supervisory review Evidence exists in the same run Manual preparation

Compliance

Compliance evidence as a by-product.

Supervisory data quality lives in BCBS 239 and MaRisk AT 4.3.4; in insurance, Solvency II QRTs are added. SQACE reports are directly usable for supervisory reviews, carrying the key, the rulebook version and classified hits per reporting date.

Audit trail per reporting date BCBS 239 MaRisk AT 4.3.4 Solvency II (QRT) DORA Versioned rulebooks

How evidence is stored in an audit-proof way is described in Security & architecture.

FAQ

Frequently asked questions

Which reports can be verified?

SQACE is report-agnostic and works on the data behind the report. In use are supervisory reports in banking (e.g. AnaCredit, COREP/FINREP) and in insurance (Solvency II QRTs), among others. It checks the business correctness of the figures, not the submission format.

Does SQACE replace our regulatory reporting software?

No. The reporting software produces and submits the report. SQACE independently checks whether the reported figures follow correctly from the input data, acting as a second instance separate from the production path.

How are reporting dates handled?

Every run is tied to a specific reporting date and a specific rulebook version. This makes every past report reproducibly traceable.

Can the business and the reporting team use the same rules?

Yes. The rules are written in business-readable language. Business, regulatory reporting and internal audit all work against the same versioned reference.

How large can the populations be?

SQACE verifies full populations of several hundred million records; the platform scales horizontally.

Can the verification be automated for the reporting date?

Yes. Via the REST API, SQACE connects to schedulers such as Control-M, Airflow or Azure Data Factory and runs automatically on the reporting date.

Put your reported figures to the test before submission.