CortexData
For Co-operative Banks (UCBs & DCCBs)

The lending OS for India's co-operative bank movement.

UCBs and DCCBs deserve modern technology that respects how they actually run — and what RBI actually requires.

CortexData was built with co-op banks at the design centre. We've architected the platform around the operational reality of UCBs and DCCBs: branch-anchored decisioning, head-office consolidation, RBI-grade compliance, multi-language artefacts in EN / ಕನ್ನಡ / हिंदी, and deployment patterns that work in tier-2 and tier-3 cities — including air-gapped on-prem.

The problems we keep seeing in UCBs.

If two or more of these sound like your bank's reality, CortexData is built for you.

Pain

Branch-by-branch processes. Each branch maintains its own Excel for sanctioned book, SI register, NPA tracker. Reconciliation to head office is monthly at best — and the IRACP return takes a week to compile.

What CortexData does

One platform, real-time consolidation across branches. Daily IRACP classification runs automatically; the monthly RBI return is generated in seconds, not days. Branch operations stay branch-controlled, but reporting stays centralised.

Pain

Vendor LOS quoted ₹3-5 Cr for a 5-year licence, plus ₹50 lakhs/year support. Most of the features were generic — built for global banks, with India compliance bolted on as an afterthought.

What CortexData does

RBI Master Directions are not afterthoughts in CortexData — they are the platform's design centre. KFS, IRACP, PSL, DSB, OSS-3, audit chain, cooling-off all ship as core. Pricing is structured for UCBs, not Tier-1 banks.

Pain

Borrowers in tier-2 / tier-3 Karnataka, Maharashtra, Tamil Nadu speak ಕನ್ನಡ, मराठी, தமிழ். The vendor product is English-only, and the local Excel templates the branch uses for KFS aren't legally airtight.

What CortexData does

EN, ಕನ್ನಡ, हिंदी customer artefacts ship as core. KFS, sanction letters, payment receipts, NPA notices — all rendered in the customer's language with the same legal and arithmetic guarantees. Other Indian languages on roadmap.

Pain

Co-op governance: dual-control on every sanction above ₹X, board resolution for write-offs above ₹Y, related-parties scrutiny on every loan to a director. Today this lives in policy documents and email threads.

What CortexData does

Sanction matrix encodes authority limits, dual-control gates, board-resolution requirement above threshold. Related-parties register cross-references every application against directors and key managerial personnel. Policy as code, not policy as PDF.

Pain

RBI inspection means weeks of pulling files, reconstructing decisions, hoping the audit trail is complete. Sometimes a sanction note is missing; a customer query reply has been deleted; a KFS copy was never archived.

What CortexData does

Every event is in the immutable audit chain. Every loan can be reconstructed end-to-end. Every customer artefact retains a stable document ID. RBI inspection becomes a query, not a fire-drill.

What changes after CortexData goes live.

  • Daily IRACP classification across the entire book, not monthly
  • RBI returns (DSB, IRACP, PSL Form A, OSS-3) generated, not assembled
  • 8 retail / MSME products on day one — including Gold and CC/OD
  • Customer artefacts in EN, ಕನ್ನಡ, हिंदी with legal parity
  • Branch ops digitised: PDC stack, cash + cheque receipts, SI mandates
  • Audit chain that survives an RBI inspection
  • Deployable on AWS Mumbai or your existing on-prem servers
  • Pricing structured for UCBs, not for the Tier-1 banks the global vendors target

Run a 90-day pilot with one branch.

We'll deploy CortexData LOS + LMS for one of your branches in 90 days, end-to-end. You'll see live origination, daily IRACP, the monthly RBI return, and a working audit trail before committing to the full network rollout.