NBFC AutoPay/eNACH collection software manages the full mandate-based EMI collection lifecycle: mandate registration → pre-debit notification → auto-debit → failed debit handling → retry → partial payment → Promise-to-Pay → field collection → bank reconciliation. FastFee is the collection layer that sits alongside your LMS — the LMS handles origination and accounting, FastFee handles every step from mandate to reconciliation in the repayment workflow.
NBFC AutoPay & eNACH Collection Software
Full mandate lifecycle for EMI collection: UPI AutoPay and eNACH mandate registration → pre-debit → auto-debit → failed debit handling → retry → partial/manual collection → PTP → field recovery → reconciliation.
The Full EMI Collection Lifecycle
From the moment a mandate is registered to cash reconciled in the NBFC's bank account — every step, automated or logged.
When the LMS confirms disbursement, FastFee triggers mandate registration. Borrower receives a UPI AutoPay or eNACH mandate request — one-time approval. Mandate status tracked: pending → active → registered.
EMI schedule from the LMS (amount, due date, frequency) is imported into FastFee. Each instalment is tracked independently — partial payments, moratoriums, and prepayments are recorded per EMI.
FastFee sends a pre-debit WhatsApp notification 2–3 days before the EMI due date (per NPCI mandate rules). Borrower is informed of the amount to be debited and the due date. Pre-debit notification reduces bounce rate.
On the due date, FastFee initiates the AutoPay/eNACH debit. The debit status comes back as: Success → EMI marked paid, receipt sent. Failure → failure reason captured (NSF, account frozen, mandate revoked, technical failure).
On failure: WhatsApp message to borrower with manual payment link → account tagged with failure reason → retry scheduled (D+1, D+3) per NBFC retry policy → partial payment accepted if borrower pays less than full EMI.
FastFee executes the retry debit on the scheduled date. If mandate has been revoked, a re-mandate request is sent to the borrower. Multiple retry attempts tracked with timestamps for NPA/audit trail.
If retries fail, the account enters PTP follow-up: agent calls borrower, records Promise-to-Pay date and amount. FastFee tracks PTP compliance — if promise is broken, account escalates to DPD bucket.
Accounts in DPD buckets are assigned to field collection agents. Agent visits, records outcome (paid/partial/refused/skip), generates receipt, and GPS-stamps the visit. Manager sees real-time field visit status.
Daily bank credits auto-matched to EMI records by mandate reference. NSF returns (NACH returns) auto-matched to failed debit records. Unmatched credits and returns surface as exceptions for the accounts team.
UPI AutoPay vs eNACH — Which to Use
- Borrower approves via UPI app — instant registration
- Debit limit: up to ₹1 lakh per transaction
- Supported by all 50+ UPI-enabled bank accounts
- Suitable for retail EMI, microfinance, personal loans
- Mandate approved and active within minutes
- Bank-level mandate — direct debit from bank account
- Higher ticket size support (above ₹1 lakh per debit)
- Registration: 1–3 working days (bank processing)
- Works for accounts without UPI — kisan accounts, cooperative accounts
- Suitable for NBFC vehicle, home, and business loans
FastFee supports both UPI AutoPay and eNACH mandates. Limits and timelines are per current NPCI and RBI guidelines — verify for your specific use case.
Failed Debit: What Happens Next
A failed eNACH or AutoPay debit is not the end of the workflow — it is the start of a structured recovery sequence. FastFee handles every step.
Debit returns with failure reason code: NSF, account frozen, mandate revoked, technical failure, account closed
WhatsApp message to borrower: payment failed + manual UPI payment link + amount + account details to check
First retry debit initiated per NBFC retry policy. Pre-debit notification sent if configured.
Second retry (if first retry also failed). Account tagged with consecutive failure count.
Re-mandate request sent to borrower via WhatsApp if mandate was revoked or expired.
Account enters PTP follow-up queue. Agent records Promise-to-Pay date and amount.
Account escalates to DPD bucket. Assigned to field collection agent.
Agent visits, records outcome (paid / partial / refused / skip trace), GPS-stamps visit, generates receipt.
Mandate & Collection FAQ
What is the UPI AutoPay mandate limit for NBFCs?
UPI AutoPay mandates support up to ₹1 lakh per transaction for recurring debits. For EMIs above this limit, eNACH is the appropriate mechanism. FastFee supports both. Verify current NPCI limits as they are updated periodically.
How long does mandate registration take?
UPI AutoPay mandate registration is typically near-instant — the borrower approves on their UPI app and the mandate is active within minutes. eNACH bank mandate registration takes 1–3 working days depending on the borrower's bank. FastFee tracks pending mandates and reminds the borrower to complete registration.
What happens when a borrower revokes the mandate?
If a borrower revokes an AutoPay or eNACH mandate, the next scheduled debit will fail with a "mandate revoked" reason code. FastFee captures this, notifies the NBFC operations team, and initiates a re-mandate request to the borrower via WhatsApp.
Can FastFee handle partial EMI payments?
Yes. When a borrower pays less than the full EMI amount (manually or via mandate), FastFee records the partial payment, calculates the shortfall, and keeps the remaining outstanding against that EMI record. Partial payments are reconciled to the correct EMI period.
How does FastFee integrate with an NBFC LMS or LOS?
FastFee works as a collection layer alongside any LMS. EMI schedules can be imported from the LMS via CSV or API. FastFee handles mandate, collection, and recovery; reconciled data and payment status can be exported back to the LMS or accounting system.
Automate your NBFC EMI collection lifecycle
Mandate setup, failed debit handling, retry, PTP, field recovery, reconciliation — live demo on your portfolio.
Book Free Demo →