Most of the conversation around RBI’s Digital Lending Directions focuses on FLDG caps and KFS requirements. These matter. But the compliance gap I see most often is in a different clause entirely: DLA registration on CIMS.
Every Digital Lending Application used by an NBFC must be registered on RBI’s CIMS portal. This includes third-party apps, loan sourcing apps operated by LSPs, and white-label origination platforms. The penalty isn’t a fine. It’s invalidation of digital loans originated through an unregistered DLA, which creates retroactive liability on your book.
The Diagnostic Checklist
List every app through which you originate or source loans digitally. Check each against your CIMS registration records. For LSP-operated apps, your agreement must confirm the LSP has registered. Verbal confirmation isn’t enough. For white-label platforms, ask your vendor explicitly and get it in writing.Â
The KFS Timing Issue
Beyond DLA registration, the KFS requirement has a timestamp problem most NBFCs haven’t noticed. The KFS must be delivered and acknowledged before sanction, not before disbursement. Before sanction. Many origination systems trigger KFS generation at the disbursement stage. That’s a violation of the timing requirement, even if the content is completely accurate.Â
In arbitration disputes over loan terms, the KFS timestamp is the first thing an adjudicator checks. If it post-dates the sanction, your position is weakened, even if everything else is correct.Â
The FLDG Cap in Practice
With FLDG capped at 5% of outstanding covered portfolio, NBFCs with existing arrangements above that threshold need to restructure their agreements. The invocation window is 120 days from NPA classification. If your ops team doesn’t have a calendar trigger for this per active FLDG arrangement, set one today.Â
The combinations risk is real too. If you have multiple co-lending and FLDG arrangements, the 5% cap applies to the aggregate, not per arrangement. Tracking this manually is where things go wrong.Â
What UltraBanker Builds
UltraBanker’s Compliance AI Agent maintains an active registry of your DLAs cross-referenced against CIMS, tracks FLDG utilisation in real time across all arrangements, and generates a monthly compliance scorecard mapped to the exact clauses in the Digital Lending Directions. It doesn’t replace your compliance team. It gives them a real-time dashboard instead of a manual spreadsheet.Â
The audit-readiness gap most NBFCs have isn’t a knowledge gap. It’s a workflow gap. Compliance by design means building RBI’s requirements into your operational system, not onto a checklist.Â
Explore LMS early warning features at Compliance AI Agent – UltraBanker.