How a Kolhapur DCCB gave 20 PACS their own mandate workflow
A District Central Cooperative Bank with 20+ affiliated Primary Agricultural Credit Societies ran all mandate paperwork centrally. BQT's multi-tenant isolation gave each society its own workspace without the DCCB losing oversight.
The situation before BQT
A DCCB in Kolhapur district, chartered under the Maharashtra Co-op Societies Act, with direct relationships to roughly 20 Primary Agricultural Credit Societies and agri-co-ops (sugar factories, dairy unions). Every society’s mandate paperwork came through the DCCB’s central ops desk — a small team trying to serve a federation of cooperatives with different lending cycles, different member bases, and different reporting needs.
What broke
Everything was routed centrally but nothing was distinguishable centrally. When a dairy co-op chairman called the DCCB to ask about his society’s outstanding mandates, the ops desk had to filter a consolidated NACH file and do arithmetic. When a kharif-season borrower had a bounce in November, the “retry in 2 days” default didn’t fit — the next debit attempt should wait for March (rabi), not tomorrow.
What changed with BQT
BQT’s multi-tenant model treats each society as its own namespace inside the DCCB’s platform instance. The sugar co-op’s secretary logs into her own branded portal showing only her members’ mandates. The PACS’s society_admin role lets her add new member mandates without needing the DCCB ops desk. The DCCB’s supervisors retain read-write oversight across all 20 societies from a single dashboard.
Seasonal lending cycles are first-class: mandates can be configured with frequency: seasonal and an explicit seasonal_window of kharif (Oct–Nov) or rabi (Mar–Apr), so the batch scheduler only presents them inside their window.
The measurable impact
20 societies onboarded in 3 weeks — most of that time was spent on society-by-society branding and user lists, not technical setup. Members across all societies access a single shared member portal URL; they identify their society by entering a society code plus their mobile. 10,500+ total members now have self-service access to their own mandate status.
The DCCB’s ops desk has gone from data janitor to control tower — they see everything, intervene only when policies trip, and spend their time on exception handling rather than assembly line work.
What was failing
- 20 affiliated societies (sugar, dairy, PACS) all routing mandate requests to DCCB's central ops desk
- Society-level reconciliation was a monthly reverse-engineering job from a single consolidated NACH file
- Society secretaries couldn't answer member queries without phoning the DCCB
- Seasonal crop loan patterns (kharif / rabi) didn't fit a one-size retry schedule
- No separation between society-level staff access and DCCB-level oversight
Outcomes
20 societies
Each with isolated data, their own users, their own branded member portal URL
Kharif + Rabi
Seasonal mandate windows configured per crop cycle; mandates pause + resume automatically
Central + local
DCCB supervisors retain oversight of all societies; society admins see only their own members
10,500+
Members across all societies accessing self-service on a single shared member portal
Ready to automate NACH at your cooperative bank?
Book a 20-minute demo with real data from your bank's segment. First 3 pilot banks get 3 months free.