Banking & Financial Services

Regulatory reporting, reconciliation, and risk data that can't afford to be wrong.

Built by a team that spent two decades doing exactly this inside Tier-1 banks — now productized as Pravah, the RBI compliance rail.

The 2026 reality

Element-based

RBI's CIMS shifts reporting from documents to data elements: every figure individually traceable, every return machine-validated

Co-lending

Bank–NBFC co-lending keeps growing — and with it, daily two-book reconciliation that spreadsheets cannot survive

DNBS-02 & beyond

NBFC returns are tightening in frequency and granularity. Manual assembly means breaks found after submission

Why another reporting tool isn't the answer

Regulatory reporting fails in the plumbing, not the form. The same balance shows three values depending on which extract you believe; lineage lives in two engineers' heads; every RBI circular triggers weeks of impact analysis because nobody can say which returns touch which source fields.

We learned this the hard way inside UK banks under BCBS 239-era scrutiny — where a wrong number means a fine, not a footnote. The answer is a rail: reconcile to source before the data enters the reporting estate, carry lineage from ledger to submitted return, and let humans review breaks instead of files.

Pravah (प्रवाह) — the compliance rail

  • Co-lending reconciliation: bank and NBFC books matched transaction-level, breaks surfaced before the regulator finds them
  • Element-based regulatory returns (CIMS, DNBS-02): source-to-return lineage, so every submitted figure traces to the ledger
  • GSTR-2B reconciliation module for CA firms — the same rail, pointed at tax

Pravah is the chassis we built for regulators, productized: governed ingestion with data contracts and quality gates, automated reconciliation back to the ledger, column-level lineage from source to return, and exception-first operations. AI proposes the mapping from your core banking and LOS extracts once; your team confirms; deterministic pipelines run every cycle after that. Fixed fee, fixed scope.

Pricing: Monthly subscription per entity + per-return-family onboarding. Fixed fee, fixed scope.

Co-lending Reconciliation & Tie-out Statement
Meridian Bank (80%) · Arthavan Finance Ltd (20%) · Month ended 30 June 2026 · Pool: 1,24,318 accounts
Prepared by Pravah · Datadives
Run #JUN26-R2 · fictional data
Pool principal — bank ledger
₹1,412.66 Cr
Pool principal — NBFC LMS
₹1,412.71 Cr
Net difference
₹4.96 L
Breaks (this page: top 5)
1,742
Account
Ledger head
Bank ledger (₹)
NBFC LMS (₹)
Tie
✓ tied · ✗ break — click to work the break · ✓* resolved this session
Working the break · AF-2214187 · DPD / asset classOPEN
Root cause
One NACH bounce on 04-Jun posted in the bank ledger only. NBFC LMS never received the return memo.
Why it matters
Asset misclassification flows straight into DNBS-02 Schedule 3. RBI inspection finding waiting to happen.
Proposed treatment
Accept bank ledger. LMS correction entry drafted; SMA-2 provisioning delta ₹36,853.
Sign-off: Maker (recon ops) — 0/5 breaks worked · Checker (finance controller) — pending
Work all breaks above to enable checker sign-off

Also for banks: legacy ETL exit

DataStage and Ab Initio estates are expensive to run and impossible to hire for. We migrate them to a modern lakehouse with the reconciliation evidence to prove nothing changed — because in a bank, a migration without parallel-run proof is a career risk, not a project.

Who we work with

NBFCs

Co-lending reconciliation and DNBS-02/CIMS returns on one rail. Start with the return that hurts most; expand from there.

Banks

Legacy ETL exit with parallel-run proof, and element-based reporting readiness for CIMS.

CA firms

White-label Pravah's reconciliation modules — GSTR-2B today, regulatory returns next — under your sign-off, our rail.

Which return hurts most?

Start with one return family, fixed fee. See breaks before the regulator does.