Most Indian lenders collect ITR as a compliance requirement. Upload the document, note the declared income, move on. The document is treated as evidence of income, not as a source of analytical signal.
That is leaving a significant amount of credit intelligence on the table.
An ITR document contains declared income by head — salary, business income, capital gains, other sources. It contains depreciation claims that reveal asset ownership. It contains interest income that indicates liquid savings. It contains loss carryforwards that tell you about the business's recent trajectory.
When you read an ITR properly, it tells you things the applicant may not have disclosed in conversation: multiple income sources, business losses in prior years, property income that suggests undisclosed liabilities, or capital gains that indicate asset sales the borrower hasn't mentioned.
More importantly, it gives you a third data point alongside the bank statement and the GSTR. In a clean application, all three tell the same story. In a fraudulent or misrepresented one, they diverge. The divergence is the signal.
We launched ITR analysis in Precisa because our lending clients kept telling us the same thing: they were collecting ITRs but not extracting value from them. Analysts were reading declared income from the summary page and ignoring everything else. Automation changed what was practical to extract.
If you are building lending workflows for Indian borrowers: treat ITR as a cross-verification tool, not a compliance box. The delta between what it shows and what the bank statement shows is where the credit decision actually lives.