An enterprise reconciliation platform for banks, fintechs and payment institutions — transaction matching, automated fee & tax assurance, governed break management, and regulator-ready reporting.
Opdrik Recon is built on a declarative, config-not-code design. New workflows are defined in a functional UI with strict four-eyes publication — no long-cycle development. Every configuration compiles into efficient, set-based SQL.
A new "rail" is stood up through the UI with maker–checker publication, eliminating bespoke development for each workflow.
The same declarative config runs natively on both PostgreSQL and Microsoft SQL Server, verified for byte-identical results by a cross-engine test suite.
Matching executes as set-based SQL in the data layer — incremental, so already-matched rows are never rescanned.
Figures below come from large-scale synthetic test runs with hard, embedded ground truth. We publish empirical numbers rather than theoretical ceilings.
Out-of-the-box support for 20 foundational rails: General Ledger and suspense accounts, card networks (3-way core-banking × switch × scheme), instant payments, ACH, RTGS, cheque clearing, and biller networks.
Rows are never rescanned once matched — processing cost is restricted to new arrivals plus residual breaks, so run times stay flat as monthly data grows.
Fee schedules and tax matrices are versioned, effective-dated data. The engine recomputes every expected fee rather than trusting provider statements, matching monthly invoices to three decimal places.
An automated Input Tax Credit recovery mechanism: monthly supplier-invoice audits run against effective-dated GSTR-2B datasets to isolate mismatches and leakages.
Discrepancies become persistent, uniquely tracked cases carrying exact monetary exposure. Aging buckets, priority queues (overdue → age → exposure) and per-band SLA alerts are fully configurable — including RBI Turnaround-Time penalty clocks (e.g. ₹100/day).
An append-only, hash-chained audit trail. Every run auto-generates a single immutable Attestation Pack PDF with the active rule version, maker≠checker approvals, break evidence, and the full audit log.
External pipelines (e.g. Apache Hop or your existing corporate ETL) feed a strict staging contract — zero custom client code inside the core engine.
Declarative rules compile into set-based SQL, executing high-speed incremental N-way matching inside the database layer.
Unmatched exceptions instantiate persistent cases, assigned to prioritised queues by aging threshold and financial risk band.
Actioned items pass through configurable maker-checker gates, compiling into a tamper-evident, auditor-friendly Attestation Pack.
An imminent, concrete architectural extension — designed to reconcile high-volume mobile payments as the governed tier of record beneath wire-speed auto-match.
Technical evaluation groups and architecture panels can request access to complete benchmark and attestation evidence.