Overdue loan accounts don’t all look the same. A borrower who missed their Equated Monthly Instalment (EMI) by nine days is in a very different situation from one who hasn’t paid in four months. That difference matters for collections strategy, provisioning calculations, and regulatory reporting. Delinquency buckets give lenders a structured way to classify these accounts, track their movement, and decide what to do next.
Key Takeaways
- Delinquency buckets classify overdue loan accounts by DPD into four operational stages: 1–30 DPD (early delinquency), 31–60 DPD (soft delinquency), 61–90 DPD (serious delinquency), and 90+ DPD (Non-Performing Asset).
- Each bucket triggers a different collection response, provisioning treatment, and escalation level. A lender that treats all overdue accounts with the same urgency will consistently recover less and spend more.
- Once a loan crosses 90 DPD and becomes an NPA, income recognition stops and provisioning requirements increase significantly under the RBI’s IRACP Directions.
- DPD data accuracy depends on real-time reconciliation between your payment gateway, LMS, and reporting system. Stale classifications create provisioning gaps that surface at month-end audits.
- Under the RBI’s weekly bureau reporting mandate effective July 2026, any lag between a DPD threshold crossing and the bureau submission is a compliance exposure, not just a data quality issue.
What Are Delinquency Buckets?
A delinquency bucket is a category that classifies a loan account based on how long a repayment is overdue. The standard measure is Days Past Due (DPD), which counts the number of calendar days since a scheduled payment was due but not received.
Most lenders organise accounts into the following progression:
- 0 DPD: Current. Payment received on time.
- 1–30 DPD: Early delinquency.
- 31–60 DPD: Soft delinquency.
- 61–90 DPD: Serious delinquency.
- 90+ DPD: Non-Performing Asset (NPA). A separate regulatory framework applies here.
The exact boundaries can vary by product type or internal policy, but the 30/60/90 progression is the regulatory and operational standard across Indian lending.
Why the Classification Matters
Collections are not a single-speed process. The right intervention at 20 DPD is a reminder call. At 75 DPD, you are looking at field visits, legal notices, and collateral valuation. Running both with the same urgency, or with no differentiation at all, is how lenders lose accounts that could have been recovered early and spend resources on accounts that needed structured resolution weeks prior.
Delinquency buckets serve two connected purposes. Operationally, they tell your collections team what type of action to take and how urgently. On the regulatory side, they determine provisioning requirements under the RBI’s Income Recognition, Asset Classification and Provisioning (IRACP) Directions 2025.
Breaking Down the 30/60/90 DPD Classification
The four classifications below aren’t administrative labels. Each one is an operational trigger that determines what the collections team does, which communication goes out to the borrower, what gets documented, and what provisioning the finance team needs to book.
1–30 DPD: Early Delinquency
At this stage, most missed payments are still recoverable without significant friction. The borrower may have forgotten, had a temporary cash flow gap, or experienced a payment failure they’re unaware of. Automated reminders via WhatsApp, SMS, and email resolve a large proportion of these accounts without human intervention. The cost of resolution is low, which is exactly why acting early preserves the most value.
From a provisioning standpoint, standard accounts require minimal provisioning at this stage. The operational risk is letting accounts sit here without follow-up. Early-stage delinquency hardens when it’s ignored.
31–60 DPD: Soft Delinquency
Once an account crosses 30 DPD, the probability of spontaneous self-cure drops. Persistent non-payment at this point usually signals something more than a one-off lapse: a cash flow problem, a disputed transaction, or the beginning of genuine financial stress. A collections agent gets involved, contact frequency increases, and the conversation shifts from a reminder to understanding what is actually happening with the borrower.
Internally, this bucket triggers a case escalation in your Loan Management System (LMS). The account moves from a digital follow-up queue to a human-assigned collection case. For secured products, this is also when preliminary checks on collateral health become relevant.
61–90 DPD: Serious Delinquency
This is the last classification before an account crosses into NPA territory. The window is narrow. Once a borrower reaches 90 DPD, regulatory reporting obligations intensify and internal write-down processes begin.
Field visits, payment restructuring conversations, and legal warnings are standard at this stage. Your LMS should be generating daily task lists, logging every borrower touchpoint, and tracking promises to pay (PTPs). Manual tracking at 60+ DPD is a material operational risk, because accounts in this bucket require precise documentation for both collections management and potential legal proceedings.
90+ DPD: Non-Performing Asset
An account that crosses 90 DPD becomes an NPA under the RBI’s IRACP Directions. Income recognition on that loan stops, provisioning requirements jump significantly, and the account moves into a separate loan recovery framework. Collections here is no longer about EMI recovery; it’s about debt resolution, settlement negotiation, or legal enforcement depending on the loan type and borrower situation.
Bureau reporting is also directly tied to this classification. Under the RBI’s weekly bureau reporting mandate effective July 2026, lenders must report to credit bureaus on a weekly basis. Any lag between when an account crosses a DPD threshold and when it’s reported creates compliance exposure and can affect the accuracy of borrowers’ credit records.
How Delinquency Buckets Drive Daily Operations
In practice, bucket classification shapes the daily mechanics of a lending operation in ways that are easy to underestimate.
The most immediate effect is on case ownership. Field agents, telecallers, legal teams, and write-off desks all have different mandates and different tools. Without automated bucket-based routing, supervisors end up manually assigning cases, and that delay compounds across an entire portfolio.
Communication logic matters just as much. A digital prompt works at 20 DPD. A structured field visit report is what you need at 75 DPD. These shouldn’t be governed by the same workflow rules, and yet in many manually managed portfolios they are.
Provisioning is where stale data causes the most damage. Moving an account from standard to sub-standard to doubtful has direct profit and loss (P&L) implications. Finance teams need accurate, timely bucket data to compute provisions correctly at month end. Stale DPD classifications create provisioning gaps that surface at audits and show up in bureau reporting accuracy reviews.
Finezza’s LMS handles bucket-based case assignment automatically, routing accounts to the appropriate team based on DPD movement and triggering communication sequences calibrated to each stage. This removes the manual escalation step that typically delays intervention by one to three days per account.
What Lenders Often Get Wrong
The most common operational failure isn’t misunderstanding the buckets; it’s the data pipeline that feeds them. DPD classification is only as accurate as the reconciliation between your payment gateway, your LMS, and your reporting system. When a payment clears on one system but doesn’t reflect immediately on another, an account that’s technically current gets misclassified as delinquent, or vice versa.
The second common gap is consistency across loan products. An MSME term loan, an education loan, and a working capital line of credit can have different DPD calculation rules if your LMS isn’t configured to handle product-specific loan structures. That inconsistency doesn’t just affect internal operations; it shows up in bureau reporting and creates regulatory exposure.
If your collections team is still manually escalating delinquency cases or running DPD calculations in overnight batch cycles, the risk compounds as your loan book grows. Finezza’s Loan Management System handles bucket-based case routing, automated communication triggers, and bureau-ready DPD reporting without manual handoffs at each stage. Book a demo to see how it works in practice.
Frequently Asked Questions
The questions below address what lenders most commonly ask about DPD classification, particularly around NPA definitions, provisioning, and bureau reporting obligations.
1. What is the difference between DPD and NPA?
DPD is a running count of how many calendar days a repayment is overdue. NPA is a regulatory classification applied once an account crosses 90 DPD under the RBI’s IRACP Directions. Every NPA has a DPD count, but not every overdue account is an NPA. Before 90 DPD, income recognition on the loan continues; after 90 DPD, it stops and significantly higher provisioning applies.
2. How do delinquency buckets determine provisioning requirements?
Provisioning requirements increase as an account ages through the DPD buckets. Standard accounts attract minimal provisioning. Accounts reclassified as sub-standard or doubtful attract progressively higher rates under the RBI’s IRACP norms. The exact percentages depend on whether the loan is secured or unsecured and how long it has remained in NPA status.
3. Can a loan account move back from a higher DPD bucket to a lower one?
Yes. If a borrower makes a payment that brings the account current, the DPD resets. This is called a cure or rollback. Tracking cures accurately matters because systems running DPD calculations in overnight batch cycles can lag on rollbacks, creating provisioning and bureau reporting errors if not reconciled in real time.
4. Does DPD classification vary across loan products?
The 30/60/90 threshold structure is standard, but the underlying calculation logic can differ across products. Working capital facilities, education loans, and MSME term loans each have different payment cycles, moratorium periods, and repayment structures. An LMS not configured for product-specific DPD logic will produce inconsistent classifications across your portfolio, which surfaces in bureau reports and internal audits.




Leave a Reply