Every NACH moment, covered — from mandate to retry.
Thirteen capabilities, grouped into the three jobs your NACH desk actually does every day: run the cycle, stay compliant, and keep the member informed. No slideware — all of it is running right now.
Running the NACH cycle
File generation, return parsing, retry orchestration, holiday-aware scheduling — the four pieces your collections desk touches every single day.
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.
Smart retry scheduling
Bounced mandates re-queued automatically based on the return code — insufficient funds retries in 2 days, account closed goes to needs-attention, etc. Fully configurable.
RBI holiday-aware batch scheduler
Diwali, Ganesh Chaturthi, Good Friday, every state's gazetted holiday — the scheduler already knows. Batches never land on a non-banking day.
What an RBI or NABARD inspector expects to see
Maker-checker, immutable audit trail, tenant isolation, field-level encryption, 2FA for privileged roles and rate-limiting — the controls your IS audit asks for, built in.
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.
Field-level encryption for customer data
Account numbers and mobile numbers encrypted at rest with industry-standard AES-256. Still searchable via secure indexing. DPDP Act 2023 ready.
Mandatory 2FA for privileged roles
bank_admin and supervisor accounts require TOTP-based two-factor authentication. Enforced at the model layer — can't be disabled through the UI.
Rate limiting and brute-force defence
Layered throttles for logins, OTP requests, and API access — stops credential-stuffing, SMS abuse, and automated scraping before they affect your users.
How your member feels the difference
A mobile-first portal, trilingual interface (English, हिंदी, मराठी), and WhatsApp + SMS nudges in the member's preferred language — so a bounce doesn't become a branch visit.
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.
Trilingual interface
English, Hindi, Marathi throughout — with Indian number formatting (1,23,456.78) and date format (DD/MM/YYYY) everywhere.
WhatsApp + SMS notifications
18 pre-built notification templates across mandate lifecycle events — WhatsApp first with SMS fallback, in the customer's preferred language.
One NACH cycle, end to end.
From the moment a member signs a mandate to the day a bounced EMI is recovered — these five steps run every cycle, every month. No spreadsheets. No "where is the file?" WhatsApp messages at 10.55 AM.
- 01
Onboard the member
Capture mandate on paper or tablet. Maker keys in, checker approves, UMRN is generated. Customer notified in their language.
- 02
Build the presentation batch
Bucket EMIs by due date, skip holidays and retry windows, enforce NPCI's 11 AM IST presentation cut-off. Preview before submit.
- 03
Hand off to your sponsor bank
Generate the NPCI-compliant .txt file. Sponsor bank uploads to e-PACS on your behalf. Keep a signed copy for RBI inspection.
- 04
Settle and reconcile
Pull the return file next day. Every code (U004, U084, Z6, M035…) is parsed and translated into Marathi or Hindi for your ops desk.
- 05
Retry — in the same cycle
Bounces tagged "insufficient funds" auto-scheduled for a T+2 retry. Others escalated to collections. No one waits a week.
Every step writes to the same immutable audit trail. When your internal auditor asks "who approved batch #2048 on 17 October?", the answer is three clicks away — with timestamps, IP, and the maker-checker chain intact.
Aadhaar e-mandate and UPI AutoPay — honest answer
Both are on our published roadmap, not live today. Aadhaar e-mandate (Phase 2) needs UIDAI AUA accreditation — a six-month regulatory path we are on. UPI AutoPay (Phase 3) rides on NPCI UPI membership or a sponsor-bank integration. Phase 1 NACH already covers the overwhelming majority of recurring collections at cooperative banks — EMIs, society dues, kisan credit interest, utility linkages. Start with what works today; add e-mandate and AutoPay when your member volume justifies it.
See the full phase-wise roadmap →See all of this in a 20-minute demo
Against real seeded data for a fictional UCB — mandate creation, batch build, return parsing, retries, member portal, audit export. Ask any hard question.