For District Central Cooperative Banks
Built for DCCBs running payments across 10–50 affiliated societies (PACS, dairy, sugar, weavers) with seasonal lending cycles that don't fit the usual NACH retry assumptions.
Typical impact
20+ societies onboarded in 3 weeks — each isolated, each branded, centrally overseen
What's broken today
- Every society's paperwork comes to the DCCB ops desk — no distinguishable by-society view
- Seasonal (kharif / rabi) lending cycles don't match default retry schedules
- Society secretaries can't answer member queries without calling the DCCB
- Consolidated NACH file has no inherent society breakdown — reconciliation is manual
- Reporting to NABARD / state cooperative registrar is hand-assembled per quarter
- Multi-society RBAC not supported by typical single-bank platforms
How BQT solves it
True multi-tenant isolation per society
Each society is its own namespace — own users, own members, own branded URL, own mandate queue. Data from one society invisible to another. DCCB supervisors see everything; society admins see only their scope.
Seasonal mandate windows as a first-class concept
Configure a mandate with kharif (Oct–Nov) or rabi (Mar–Apr) window. Batch scheduler automatically only presents it inside its season. No more manual pause / resume cycles.
Society-level member portal
Each society gets its own branded URL on the member portal. Members enter a society code + mobile number to log in. Cross-society identity isolation guaranteed.
Central oversight, local control
Five distinct staff roles cover every level — bank administrator, supervisor, operator, read-only auditor, society administrator — each with strictly-enforced access boundaries. DCCB staff see across all societies; society staff see only their own members.
Regional language operations
Tri-lingual UI and notifications — society staff often work in Marathi / Hindi natively. Number + date formats in Indian standards everywhere.
Single platform, many federations
One BQT instance can host the DCCB + its 20–50 affiliated societies cleanly. No duplicate infrastructure to maintain.
Ready to see it with DCCB-specific flows?
Our demo includes a seeded Kolhapur DCCB tenant with 3 affiliated societies and seasonal mandates — end-to-end walkthrough.