CIBIL Masterclass · Part 4 · Credit · 9 min read · July 2026
How to read your CIBIL report — like a credit officer does
Most people look at their credit report the way they look at a medical scan: they find the one big number, feel relief or dread, and close the tab. A credit officer barely glances at that number. The real reading happens in a grid of three-digit codes further down — and it takes about ninety seconds. Here is that ninety-second read, taught slowly.
- The score is a summary; the accounts section is the evidence. Officers read the evidence.
- The DPD (Days Past Due) grid under each account is the heart of the report: 000 or STD means paid on time, numbers like 030/060/090 count days late, and codes like SUB, DBT, LSS mark serious trouble.
- Every bureau must give you one free full report every year — and genuine errors can be disputed online, free, with the bureau typically responding in about a month.
First: get the real report, not just the score
The score you see inside banking and finance apps is fine for tracking, but it's a headline without the article. For the full document, go to the bureau directly — every credit bureau in India is required to provide one free full credit report per calendar year, from its own website. Download the PDF. That's the same underlying data a lender pulls, minus a few lender-only fields.
Now read it in the order an officer does — which is not top to bottom.
The sixty-second scan: accounts first
Skip your name and address for now. Go straight to the account information section — one block per loan or credit card you've ever held. Each block carries the lender's name, the account type, dates opened and (if applicable) closed, the sanctioned amount or credit limit, the current balance, and then the part that decides everything: the payment history grid.
Decoding the DPD grid
DPD stands for Days Past Due — for each month, how many days late the payment was. The grid shows up to 36 months, newest first. The vocabulary is small:
| Code | What it means | How the desk reads it |
|---|---|---|
| 000 / STD | Paid on time (or within the standard window) | Clean. This is what a whole grid should look like. |
| 030 / 060 / 090 | 30, 60, 90 days past due that month | A slip. One old 030 is survivable; a recent 090 changes the conversation. |
| XXX | Lender didn't report that month | Neutral — a gap, not a sin. |
| SMA | Special Mention Account — early stress | A yellow flag on its way to red. |
| SUB / DBT / LSS | Sub-standard / Doubtful / Loss | The account went bad. These codes dominate the whole file. |
Two reading rules the desk applies instinctively. Recency beats history: a 060 from four years ago is a scar; a 060 from four months ago is a wound. And trajectory matters: 030 → 060 → 090 across consecutive months tells a story of someone sinking; 090 → 030 → 000 tells a story of someone climbing out. Same codes, opposite files.
The status words that outrank the grid
Above each grid sits an account status, and a few specific words there override everything else on the page:
- Closed: repaid in full. The gold standard ending.
- Settled: the lender accepted less than it was owed. Reads as a broken promise, and follows the file for years — Part 5 covers this word in full.
- Written off: the lender gave up recovering and absorbed the loss. The heaviest single phrase a retail report can carry.
- Suit filed / Wilful default: legal action markers. At this point the score is the least of the problems.
The enquiry section: quiet, but read carefully
Near the end sits a list of every lender that has pulled your report — the hard enquiries. Each entry names the institution, the date, the loan type and amount applied for. Your own checks never appear here; those are soft enquiries, invisible to lenders and harmless to the score, as Part 1 established.
What the desk looks for is clustering. Five enquiries across five lenders in three weeks reads as someone being declined and reapplying — credit-hungry, in bureau language. Two enquiries for the same home loan while rate-shopping reads as normal diligence. The entries are identical in format; the pattern is what speaks.
The boring sections that quietly cause rejections
Now go back to the top — the personal information, contact and employment sections. Nobody reads these for character; they're read for consistency. A PAN mismatch, an old employer, a phone number you abandoned years ago — none of it hurts the score, but any of it can stall a file in verification, and a wrong PAN can even merge someone else's accounts into your report. Ninety seconds spent checking these fields is the cheapest file-hygiene available.
Found an error? The dispute process is free
Genuine reporting errors are common enough that every bureau runs a formal, free, online dispute process:
- 1. On the bureau's website, open the dispute form and identify the exact field — a wrong DPD entry, an account that isn't yours, a closed loan showing active.
- 2. The bureau routes it to the lender that reported the data — bureaus record what lenders send; only the lender can authorise a correction.
- 3. Expect a resolution or response in roughly 30 days. Keep every reference number.
- 4. If the lender stonewalls a genuine error, escalate in writing to the lender's grievance cell, and after that to the RBI Ombudsman — the paper trail you kept is exactly what makes that escalation work.
Make it a ritual
Pull your free report once a year — a birthday-month ritual works. Scan the DPD grids for anything that isn't 000, check the status words, skim the enquiries for strangers, verify the PAN. Ten minutes, once a year, and you will never again be surprised by your own file — which puts you ahead of most applicants who reach the desk.
And if the report shows the one word that outweighs every other — settled — the next part is written for you: Part 5 →