How a Pune UCB cut NACH bounce-to-retry from 7 days to 1
An Urban Cooperative Bank with ₹220 Cr loan book was leaking ~₹40L/year to preventable NPAs because bounced mandates sat in an Excel queue for a week before retry. BQT closed that loop.
The situation before BQT
A 12-branch UCB in Pune, operating across Maharashtra with a ₹220 Cr loan book. NACH was the dominant collection channel for loan EMIs — roughly 3,500 active mandates, ~₹1.8 Cr collected monthly. The ops team was competent but the process was stuck in 2010: Excel-based mandate tracking, weekly batch runs, a two-person email-and-PDF workflow with the sponsor bank.
What broke
The return file from NPCI was the choke point. Return codes like “U004” or “Z6” arrived as opaque strings; the operator had to cross-reference a printed NPCI code sheet. Average triage took 2 days. By the time a “insufficient balance” bounce was understood and the retry scheduled, the customer’s salary had cleared and been spent again. Compounding week after week.
What changed with BQT
Return file upload became a one-click operation. All 88 NPCI return codes translate into plain Marathi for the operator. Retries schedule themselves — “insufficient balance” gets T+2 automatically, “account closed” gets flagged for customer outreach, “signature mismatch” goes to the supervisor for manual review. The member portal cut inbound “status of my EMI?” calls by about 40%, freeing branch staff for real customer service.
The measurable impact
The hero number is the retry-cycle compression: from 7 days average to under 24 hours. On the ₹220 Cr loan book, that shaved roughly ~60% off the preventable portion of monthly NPAs — recovered in the same collection cycle rather than slipping to the next one.
The operator can now generate a NACH batch, submit for supervisor approval, download a validated file, and get it to the sponsor bank inside a 30-minute morning window. Same-day batches are routine.
What was failing
- Operators hand-assembling NACH files in Excel every Monday, emailing them to sponsor bank
- Return file arrived 2 days later as a PDF — parsed line by line, often miscategorised
- By the time a bounce was understood and retried, the customer's next salary had already been spent
- No customer-facing visibility — branch phones flooded with "has my EMI gone through?" calls
- Audit trail was a shared Excel that got overwritten
Outcomes
~60% reduction
Preventable NPAs on the retry window — recovered within the same collection cycle
40% fewer branch calls
Customers self-serve mandate status via the member portal
100% of batches
Auto-scheduled around RBI + state holidays; zero manually-skipped days
7 years
Immutable audit trail retained — comfortably exceeds RBI requirements
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.