DPD in CIBIL Report: Meaning of 000, XXX, STD, SMA, SUB, DBT and LSS

If your CIBIL report shows entries such as 000, 030, 060, 090, XXX, STD, SMA, SUB, DBT or LSS, the key is to read them in context. DPD means Days Past Due: a numeric DPD value indicates how many days a payment was reported late for a particular reporting period. Other entries, such as XXX or asset-classification labels, communicate something different. They should not all be interpreted as a score or as proof of a missed payment.

In simple terms, 000 generally means no days past due were reported for that month, while XXX means the lender did not report DPD information for that period. Codes such as STD, SMA, SUB, DBT and LSS are asset-classification terms described in CIBIL's consumer guidance. The exact display can vary by report format, so use the legend in your own report and compare the entry with your lender's records before deciding what action to take.

What does DPD mean in a CIBIL report?

Days Past Due is a record of how late a scheduled payment was reported for a particular month. It appears in the account or repayment-history section of a Credit Information Report (CIR). The report may show a month-by-month sequence for a loan or credit card, allowing you to review the payment history rather than relying only on the headline credit score.

For example, if an instalment was due on the 5th and the lender's records show it remained unpaid for 30 days beyond the due date, the relevant month may display a value such as 030. A value such as 060 indicates 60 days past due for the reported period. The number is not a credit-score point change, a loan account number, or the date on which the report was downloaded.

TransUnion CIBIL's own guide to reading a CIBIL report explains that numeric DPD values indicate the number of days a payment was late. It also explains that XXX can appear when a bank has not reported information for those months. See the CIBIL report-understanding document for further context about the sections in a report.

Common numeric DPD values and how to read them

Numeric entries are best understood as a snapshot of the repayment information reported for a specific month. They are not predictions of what will happen to your credit score, and they do not by themselves explain why the payment was late.

The three-digit format is commonly used in CIBIL examples, but the presentation of a report can change. Read the value together with the month or date shown beside it. A single DPD value should never be interpreted without checking which account it belongs to and what period it covers.

What does 000 mean in a CIBIL report?

A 000 entry generally means that no days past due were reported for that month. It is a positive sign for that particular period, but it is not a guarantee that the entire report is error-free or that a lender will approve a new application. Your report may contain older late-payment entries, high outstanding balances, unfamiliar enquiries or other information that a lender considers.

For example, suppose a personal loan shows 000 for the last six months but 060 in an earlier month. The recent entries suggest no days past due were reported in those six months, while the older 060 remains part of the visible history. A later 000 does not automatically erase an earlier accurate late-payment record.

Also check the outstanding balance, amount overdue, last-payment date and account status. A DPD entry is only one part of the account record. If your payment was made on time but a month still shows a late value, collect evidence before raising a dispute.

What does XXX mean in a CIBIL report?

XXX does not mean that you were 30 days late, and it does not mean that your payment was definitely on time. CIBIL's published explanation says that XXX may appear when the bank has not reported information for those months. It is therefore a missing-reporting indicator, not a numeric DPD value.

There can be several reasons why a period has no reported DPD value, including the lender not supplying data for that month or the report format not displaying a numeric status. Do not assume the cause from the code alone. If XXX appears repeatedly on an active loan, or if the account details are inconsistent with your statements, ask the reporting lender to clarify the missing periods and verify the data supplied to the bureau.

Keep the report date in mind. Credit reports reflect information received and processed by the bureau, not necessarily every transaction made today. If you have recently paid an EMI or credit-card bill, an older report may not yet show the update. Our guide on when CIBIL reports update explains why timing differences can occur.

STD, SMA, SUB, DBT and LSS: classification labels explained

Some reports show short asset-classification labels in or near the repayment-history area. These are different from numeric DPD values. They describe how an account has been classified under the applicable reporting framework; they are not simply alternative spellings of 000, 030 or 090.

These labels should be interpreted using the explanation supplied with the particular report and the lender's applicable classification rules. Different credit products and reporting circumstances may not be identical. If a code appears unfamiliar, save the report page and ask the lender or bureau to explain the exact field rather than relying on an informal list found online.

One important distinction: STD is a classification label, whereas 000 is a numeric DPD entry. They may both appear in explanations of a regular account, but they are not interchangeable in every context. Likewise, XXX refers to missing DPD reporting for a period, not an asset classification.

How 30, 60 or 90 DPD may affect your credit profile

A reported late payment can matter because repayment history is one of the details lenders may review when assessing a credit application. A longer overdue period can be more concerning than a short delay, but there is no reliable universal rule that a particular DPD code will reduce every person's score by a fixed number of points. The impact depends on the complete credit file, the scoring model, the account type, the recency and frequency of late payments, and the lender's own policy.

A 090 entry deserves careful attention because it records a substantial reported delay. It may affect how a lender views the account, but it does not automatically mean every future application will be rejected. The decision to lend belongs to the lender and can involve income, existing obligations, documentation, collateral and other underwriting checks. For the specific process of addressing a 90 DPD entry, see our guide to checking and disputing a 90 DPD marker.

Do not compare two people's DPD entries and assume the score impact will be identical. A report with a single old late payment is not the same as one with repeated recent delays, high balances and several overdue accounts. Review the full file before drawing conclusions.

How to check whether a DPD entry is correct

Use a methodical review instead of assuming that every adverse-looking value is a bureau error. Start with the latest full report and work account by account.

1. Identify the exact account. Note the lender name, masked account number, account ownership, account type and the month showing the DPD value.
2. Check the report date. A report generated before a recent payment or lender update may not show the latest information.
3. Compare the dates. Match the contractual due date with your bank statement, payment receipt, UPI or net-banking confirmation and the lender's loan ledger.
4. Check the amount overdue. Compare the reported overdue amount and current balance with the statement for the same period. Account for payment reversals, failed transactions or amounts allocated to a different due.
5. Review the full history. Look at the months before and after the entry. A sequence can help you see whether one value is inconsistent with the surrounding record.
6. Save evidence. Keep the relevant report page, statements, receipts, closure documents where applicable and previous complaint references. Share only what the official dispute process requires.

If you do not recognise the account at all, treat it as a possible ownership or identity issue rather than merely a DPD mismatch. Contact the lender through an independently verified official channel and raise a dispute with the bureau. Do not share OTPs, passwords or a complete report with an unsolicited caller who promises to fix your score.

What to do if the DPD is inaccurate

If the reported DPD does not match the lender's records, raise a specific dispute with the credit bureau and contact the lender that supplied the information. State the exact account, month and field you believe is wrong. Attach relevant evidence such as a payment receipt or statement, and ask the lender to investigate its records and submit corrected information if an error is confirmed.

Use the official TransUnion CIBIL dispute-resolution process if the issue is in your CIBIL report. You can also follow our detailed step-by-step guide to correcting CIBIL report errors. Keep the dispute reference number, filing date, documents submitted and every written response. If the first response does not explain the result, request clarification and use the lender's formal grievance channel.

A bureau generally relies on the reporting credit institution to verify account facts; it cannot simply change an accurate lender-reported payment history because a borrower dislikes the entry. The right outcome may be a correction, an update to the current balance or account status, or confirmation that the original information was accurate. The remedy depends on the evidence and the nature of the discrepancy.

What if the DPD is accurate?

If the payment was genuinely late, do not file a false dispute or pay an agent who promises to delete accurate history. Bring any overdue amount under control, contact the lender if you need repayment options, and obtain written confirmation of any payment, settlement or closure arrangement. Ask what account status the lender will report after the arrangement is completed.

Paying overdue dues may resolve the outstanding amount, but it does not automatically erase an accurate past DPD entry. A closed account can still show historical payment information. The aim is to make sure the current balance and account status are accurate and to build a consistent repayment record going forward—not to create a misleading report.

Be cautious of claims that a fixed fee will guarantee a particular score increase, remove all negative entries or secure loan approval. A legitimate correction should be based on the lender's records and supporting evidence, not a promise to bypass the reporting process.

How long does a DPD update take?

There is no single instant update that applies to every lender, bureau and account. Credit institutions submit information according to their reporting processes, and the bureau must receive and process the update. A payment made today may therefore not appear in a report downloaded today. Check the date of the reported information and allow the normal reporting cycle to pass before concluding that a recent transaction has been omitted.

If a value remains inconsistent after the lender should reasonably have reported the correction, raise a documented query rather than repeatedly purchasing reports or submitting the same complaint without new evidence. The bureau's own current guidance should be checked for the account and process in question, because reporting timelines can differ.

Common mistakes to avoid when reading DPD

• Treating XXX as 000: XXX means no DPD information was reported for that period; it does not certify an on-time payment.
• Assuming 000 cleans the whole account: it relates to a specific reported period, not every month in the account's history.
• Confusing DPD with score points: 030 means 30 days past due, not a 30-point score drop.
• Mixing up classification and delay codes: STD, SMA, SUB, DBT and LSS are classification labels, not simple numeric DPD values.
• Disputing without checking documents: compare due dates, payments and the report date first so the dispute identifies a real discrepancy.
• Expecting payment to erase accurate history: paying an overdue amount may update the current position, but it does not guarantee removal of accurate historical reporting.
• Trusting guaranteed repair promises: use official lender and bureau channels, keep evidence and avoid sharing security credentials.

Conclusion: read the code, then verify the account

When you see a DPD entry in your CIBIL report, first establish whether it is a numeric late-payment value, a missing-data marker such as XXX, or an asset-classification label such as STD or SMA. Then check the month, account, report date and supporting payment records. This prevents you from confusing a missing update with a genuine delay—or assuming that a correct entry is an error.

If the record is inaccurate, raise a documented dispute with the lender and bureau. If it is accurate, focus on resolving the current position and maintaining timely payments going forward. For a broader review, start with how to obtain your free credit reports from all four bureaus in India, then use official guidance to investigate any specific mismatch.

Educational information only. The interpretation of a report depends on its format, the lender's reported data and applicable rules. This guide is not a promise of a particular score change or loan outcome.