Reconciliation
Classify deviations and resolve them in minutes.
SQACE compares records across multiple systems, classifies deviation patterns via a versioned rule library and traces from the KPI down to the individual record. Every run leaves a complete audit trail.
30 minutes, on your own use case.
The problem
Deviations without a cause are a reporting risk.
Classical reconciliations show that a difference exists. The cause then has to be reconstructed by hand, so resolution drags on and known deviation patterns get classified manually again and again.
When auditors and supervisors come calling, there is no consistent record of the recurring cases. In banks this affects treasury, risk and regulatory reporting; in insurers, policy administration, claims and the actuarial function; in critical-infrastructure firms, the reconciliation between the control and process data levels.
The SQACE solution
Classified deviations with drill-down.
SQACE compares records from two or more systems along a defined key. Deviations are checked against a classifying rulebook, so recurring patterns such as booking cut-offs, rounding rules, cut-off-date differences or known carry-over errors are marked and grouped automatically.
New patterns are classified once by the business and added to the rule library. Because the library grows user-driven and versioned, the resolution effort falls with every reconciliation. The drill-down goes from the aggregated KPI down to the causing individual record, in the same platform.
Scenarios
Where teams use reconciliation with SQACE.
Prove cross-system consistency
Positions in front office, risk system and accounting are reconciled daily, booking cut-offs included.
Reconcile KPIs, balances and aggregates
Reporting layers in the DWH and departmental systems are verified at the KPI level and at the movement level.
Classify deviations automatically
Routine cases are explained without human intervention. Genuine anomalies remain and are resolved with priority.
In concrete terms
- Minutes instead of hours for root-cause analysis.
- Reuse of classifications across days and quarters.
- The audit trail is created in the same run, not afterwards.
At a glance
| Aspect | SQACE reconciliation | Manual reconciliation |
|---|---|---|
| Resolution per deviation | Minutes | Hours |
| Classification | Versioned rule library | Tribal knowledge, undocumented |
| Drill-down | In a single run | Across several tools |
| Audit trail | Directly in the run | Created afterwards |
Compliance
Compliance evidence as a by-product.
Reconciliation requirements live in BCBS 239 (principles 6 and 7), MaRisk AT 4.3.4, Solvency II QRTs, IFRS reporting and the DORA requirements for ICT integrity. SQACE reports are directly usable for supervisory reviews, complete with the key, the rulebook version and classified hits.
How SQACE secures data access is described in Security & architecture.
FAQ
Frequently asked questions
Can existing reconciliation logic be reused?
Yes. SQL logic, Excel rules or interface scripts are migrated step by step into rule-based classifications.
What frequency is typical?
Daily runs are standard. When needed, reconciliations also run intraday or ad hoc, for example for quarter-end closings and reporting dates.
How many sources can be compared?
Two or more. In some setups, four to six sources are reconciled simultaneously.
What sets SQACE apart from classical reconciliation platforms?
Classical tools bring records together and show differences. SQACE classifies the differences from a business perspective via a versioned rule library and delivers an audit trail per run.
How are cut-off-date differences handled?
Cut-off-date and booking offset is modeled as its own class. Hits in this class are self-explanatory, without every record being checked manually.
Can reconciliation be embedded in scheduler setups?
Yes. Connection to Control-M, Airflow, Azure Data Factory or your own scheduler is via the REST API.