CIBIL Masterclass · Part 4 · Credit · 10 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 numbers beside the grid
Each account block carries a handful of figures that the eye skips over, and two of them do a great deal of work in an assessment.
On a credit card, the block shows the sanctioned limit and the current balance, and the ratio between them is your utilisation on that card. The desk reads it per card as well as across all cards together, because a portfolio at 30% overall can still contain one card sitting at 95% — and a single maxed card reads as stress even when the total looks comfortable. The figure reported is the balance as on the lender's reporting date, not your average through the month, which is why paying a card down a few days before the statement generates a materially better-looking report than paying it a few days after.
On a loan, the block shows the sanctioned amount, the current balance and usually the EMI. That EMI figure is what a new lender adds up to compute your existing obligations, and it is taken from the report rather than from what you tell them. A loan you closed months ago that still reports a balance and an EMI is therefore not a cosmetic error — it is actively reducing the amount a lender will offer you.
There is also a date of last payment and, on troubled accounts, a date reported and an amount overdue. On an account you believe is settled or closed, those three fields together tell you whether the lender has actually updated its reporting or simply stopped sending fresh data.
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.
How current the report you are reading actually is
A credit report is not a live view. It is an accumulation of files that lenders send in on their own cycle, and understanding that lag explains a lot of the confusion people have about their own report.
Since January 2025, lenders report to the bureaus fortnightly — generally around the fifteenth and the last day of each month — replacing the older monthly cycle. That is a meaningful improvement: a payment made today shows up in weeks rather than potentially a month and a half. It is still not instant, and it explains the two questions that arrive most often. A loan you closed last week almost certainly has not updated yet. A payment you made yesterday will not have moved your score today.
It also means different accounts on the same report are current to different dates, because lenders do not all report on the same day. When you pull a report to verify a correction, look at the date reported on that specific account rather than the date on the report itself — if it predates your payment, the lender simply has not sent the updated file yet, and waiting one more cycle is the correct response rather than raising a dispute.
One consequence worth planning around: if a lender has told you a correction is done, allow at least one full reporting cycle plus a few days for bureau processing before you check, and pull a fresh report rather than refreshing an app score. App scores refresh on their own schedules and are frequently older than the report you can download yourself.
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.
Accounts that are not yours
The entry that unsettles people most is a loan or card they have never held. It happens for three quite different reasons, and the right response differs for each.
Most often it is a data mix-up — a common name, a mistyped PAN, a shared address, and someone else's account attached to your file. This is a straightforward dispute, and the PAN field is usually where the evidence lies.
Sometimes it is an account you genuinely have, in a form you do not recognise: a card issued as part of a loan, an overdraft attached to a salary account, a co-applicant loan taken years ago for a relative, or a guarantee you gave and forgot. Guarantees in particular appear on the guarantor's report and are counted against them, which surprises people who thought of it as a signature rather than an obligation.
The third possibility is identity misuse, and it is the one that justifies raising the matter urgently. If an account is genuinely fraudulent, dispute it with the bureau and report it in writing to the lender named, keeping every acknowledgement. Then check the enquiry list for pulls you did not authorise, because an application made in your name usually leaves a footprint there before the account appears.
In all three cases the mechanism is the same and it is free. What matters is not letting an unrecognised entry sit for a year because it seemed too odd to be real.
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 →
The tool for this
Once you have read the report, tap what it shows and see which entries are doing the most to your score.
Written at the MoneyClarityTech desk — by a working retail-credit professional in Indian banking who reads loan files, credit reports and bank statements every working day. Patterns from hundreds of real cases; every identifying detail removed. More about MoneyClarityTech →