DPD in Credit Bureau Reports: A Lending Team’s Practical Guide
Most credit teams have a recognisable workflow when reviewing bureau reports: score first, NPA status second. The inquiry count gets a glance at most. The DPD section gets a cursory look at most, sometimes none at all if the score is above the internal threshold. That’s where risk slips through.
Days Past Due (DPD) is the month-wise payment history for every credit account a borrower holds, covering the past 36 months. Banks and NBFCs submit this data to credit bureaus fortnightly, on the 15th and last day of each month, and it appears as a grid beneath each credit facility in the report: home loans, personal loans, business loans, and credit cards. Each cell represents one month of payment behaviour.
The credit score is a composite number derived from several factors. DPD is the raw payment record underneath it. Both matter, but they don’t always tell the same story. When they diverge, the DPD is usually the more honest of the two.
Reading the DPD codes
The grid uses a combination of numeric values and short codes. Understanding each one is the starting point for any practical interpretation.
- 000 means the borrower paid on time for that month with no outstanding balance. This is the ideal value. Interestingly, some lenders approve applications with below-average scores if the DPD grid shows a consistent run of 000s, because clean repayment history directly offsets a weak score.
- XXX indicates the lender did not submit data for that month. Bureaus treat this as neutral. Lending teams should not.
- STD stands for Standard: the payment was made, but within 90 days of the due date rather than on the exact date. It reflects a delay, though the account has not yet been classified as an NPA.
- SUB is Sub-standard: the account was classified as an NPA and has been in that status for less than 12 months.
- DBT is Doubtful: NPA status extending beyond 12 months.
- LSS stands for Loss: the lender considers recovery unlikely.
Numeric values, such as 30, 60, or 90, appear when a payment is that many days overdue in a given month. Under RBI’s asset classification norms, any loan overdue by more than 90 days is classified as a Non-Performing Asset.
What the Pattern Tells You That the Score Doesn’t
A score of 740 looks acceptable on paper. But if the DPD grid shows 30, 60, 90 across three consecutive months 18 months ago, followed by a clean run since, the interpretation requires more work than a single number allows.
That pattern could reflect a genuine cash flow disruption that was resolved. It could also reflect a borrower who cleared dues specifically ahead of this application, knowing how bureau reporting cycles work. Both scenarios carry different implications for credit risk. The score has likely recovered. The pattern remains.
The other thing DPD reveals that scores can miss is the relationship between repayment behaviour across different facilities. A borrower who consistently maintains 000 on a home loan while showing periodic 30-day delays on a personal loan is almost certainly prioritising secured debt over unsecured. That’s a repayment hierarchy, not random behaviour. It tells you something about how this borrower will behave if cash flow tightens after disbursement.
Similarly, simultaneous delays across multiple loans in the same month are a stronger distress signal than a delay appearing in one account only. One missed payment could be an oversight or a technical issue. Across four facilities in the same month, it points to a cash flow event.
Where Lending Teams Commonly Misread DPD
The most frequent error is treating XXX as equivalent to 000. It is not. A string of XXX values means the lender failed to report data for those months. Under RBI’s Credit Information Reporting Directions 2025, the fortnightly submission requirement was formalised. Weekly incremental submissions become mandatory from July 1, 2026. Despite tighter requirements, reporting gaps still occur, particularly for older loans or accounts with smaller regional banks.
When you see extended XXX periods followed by a clean run of 000s, investigate when the account was actually opened and which bank holds it. A recently opened account with several XXX values followed by 000 is not the same as a long-standing account with the same pattern.
Another common misread: evaluating DPD without considering the inquiry count from the preceding months. High inquiry volumes in the months before this application, combined with an otherwise clean DPD, can signal loan stacking. The borrower may have already taken loans at other institutions. Those liabilities don’t yet appear on the bureau because reporting cycles haven’t caught up, but the DPD from older accounts will reflect the cash flow pressure those new obligations are creating.
DPD on Different Credit Types: Not All Delays Are Equal
Credit card DPD delays are often discounted because card payment dates can fall inconveniently, and delays don’t always indicate genuine financial stress. Many lenders apply a softer lens here.
DPD on a home loan or a secured business loan is a different matter. Borrowers almost universally prioritise secured debt because the asset at risk is tangible. When DPD appears on a home loan, it reflects a cash flow situation severe enough to override that priority. That deserves more weight in the assessment.
MSME borrowers present a specific complication. Their income is often seasonal or tied to payment cycles from clients. A DPD that consistently appears in the same two months every year could reflect a cash flow gap that’s entirely predictable and managed, rather than an accumulating default risk. Without the bank statement context, you can’t tell. Precisa’s cross-analysis of bureau reports and bank statements resolves exactly this: it maps whether the seasonal DPD aligns with actual cash flow dips in the account, or whether the pattern is more erratic.
All of these distinctions matter, but DPD read in isolation only goes so far. The bureau report shows what was reported to it. The bank statement shows what the account was doing during those same months.
Why DPD in Credit Bureau Reports Needs Bank Statement Context
The bureau report tells you what was reported. The bank statement tells you what happened in the account.
Precisa’s credit report analysis pulls bureau data and generates a cross-analysis alongside bank statements. When a borrower’s DPD shows delays in specific months, the bank statement reveals whether the account had funds during those periods or not. If the bank statement shows healthy inflows during the same months the DPD indicates delays, the discrepancy becomes a question worth asking before approval. If the bank statement shows declining balances and ECS bounce charges in the same period, the DPD pattern is explained by real cash flow gaps, and the risk assessment changes accordingly.
This cross-referencing also helps with FOIR (Fixed Obligation to Income Ratio) calculations. The bureau report lists all active loans. The bank statement shows all recurring outflows. Comparing the two identifies EMI obligations that appear in the bank account but are not reflected in the bureau file, which is a common indicator of informal or undisclosed debt.
A Practical Checklist for Reading DPD
When reviewing the DPD section of a credit bureau report, a few consistent checks add structure to the assessment:
- Any DPD value above 30 in the past 12 months should have a documented explanation before the credit decision is finalised.
- Consecutive escalating DPD (30 to 60 to 90 in sequence) in the past 24 months is a material risk factor, not historical noise.
- Simultaneous DPD across two or more facilities in the same months carries more weight than isolated delays in a single account.
- XXX values in a recently opened account should trigger a follow-up on reporting history from the holding bank.
- DPD on secured loans should be weighted more heavily than equivalent delays on unsecured credit.
Precisa’s credit report analysis flags these patterns automatically and generates a cross-analysis when bank statements are submitted alongside the bureau file. The Precisa Score incorporates repayment behaviour and cash flow data together, which means the manual reading exercise becomes a verification step, not the primary one.
If your credit team processes bureau reports as part of underwriting, try Precisa for free to see DPD cross-analysis alongside bank statements in action.
