B BQT Small Banks
For Urban & District Central Cooperative Banks in India

Stop losing customers to bounced EMIs.

The NACH mandate and collection platform purpose-built for Urban Cooperative Banks and District Central Cooperative Banks. Generate NPCI-compliant files for your sponsor bank, read every return code in Marathi or Hindi, and retry bounced EMIs in the same cycle — not next week.

On a ₹200 Cr loan book, closing the retry gap recovers ~₹40L/year of otherwise-preventable NPA slippage.

0

NPCI return codes parsed

3 langs

English · हिंदी · मराठी

0h

Bounce-to-retry cycle

0 yr

Audit trail retention

₹1.8Cr Monthly collection 96.4% Success rate 3,542 Active mandates
EN · हि · मर
✓ Audit-ready

Built for the realities of cooperative banking

RBI IT Directions ready
NPCI NACH-spec compliant
DPDP Act 2023 aligned
Data stays in India
Who this is for

Whichever hat you wear, there's a path through this site.

How NACH works at a cooperative bank

You don't submit to NPCI directly. Your sponsor bank does.

Most cooperative banks aren't NPCI members. They route NACH files through a sponsor bank (typically a public-sector bank) that has NPCI membership. The sponsor bank uploads the file to NPCI's e-PACS portal on your behalf and passes the return file back to you.

BQT plugs into that workflow — your ops team generates a compliant file, downloads it, hands it to your sponsor bank, and uploads the return file we give back to them. No change to your sponsor arrangement, just a faster and cleaner loop on your side.

The problem

A ₹200 Cr loan book leaks ~₹40L/year to preventable NPAs.

Most cooperative banks run NACH manually — Excel mandates, hand-assembled files, return codes looked up against a printed sheet. The average bounce-to-retry cycle stretches to 5–7 days. By then, the customer's salary has cleared and been spent again. The bounce becomes an NPA.

It's not a customer quality problem. It's an operations cycle-time problem.

Without BQT

Excel-assembled files Return codes triaged manually PDF reports from sponsor bank Retries slip into next cycle

With BQT

One-click file generation Plain-language return codes Auto-parsed return files Retries fire in the same cycle
What you get

Six things every cooperative bank's NACH team needs.

Each of these is in production today. Not a roadmap, not a slide — the software our pilot banks use.

NPCI-compliant NACH file generation

Generate 200-character fixed-width NACH files ready to upload to your sponsor bank's e-PACS portal — CRLF line endings, MD5 checksums, paise conversion all correct.

Return code translation in your operator's language

When "U004" lands in your return file, it reads "खात्यात अपुरी शिल्लक" (insufficient balance), flags the customer for a T+2 retry, and moves on — no cross-referencing a printed NPCI code sheet.

Maker-checker enforcement

Operators create, supervisors approve — enforced at the database and policy layer, not just UI. No one can approve their own work.

Immutable audit trail

Every action — mandate created, approved, revoked, return processed — logged with user, IP, timestamp, and diff. Database trigger prevents tampering even by DBAs.

Clean separation between banks and societies

Your Kolhapur PACS can't see your Sangli PACS. Your central DCCB ops desk sees both. Data walls are enforced by the platform — your staff can't accidentally (or deliberately) cross them.

Mobile-first member portal

Your customers log in via OTP, see their mandate status, payment history, and raise support requests — all on their phone, in their language.

Solutions

Built differently for UCBs and DCCBs.

The two bank types have different operational realities. Pick the path that matches yours.

Case studies

Problems we close, by bank type.

All case studies

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.