Form 26AS, AIS and ITR: What Each Proves When a Lender Verifies Income

Each tax document gives lenders a different level of evidence about borrower revenue.

Form 26AS is an annual tax credit statement generated on TRACES under Section 203AA of the Income-tax Act, 1961. It shows withholding tax, advance tax, and refunds on a PAN. Payers populate it through quarterly returns like Form 24Q and Form 26Q. Form 26AS proves that an entity with a valid TAN number deposited tax. But it cannot verify tax-free income or business legitimacy.

The Annual Information Statement, or AIS, tracks broader finances under Section 285BB of the Income-tax Act, 1961. As detailed in the Ministry of Finance rollout announcement, AIS captures transactions from banks and depositories. It reports interest, dividends, securities trades, property deals over thirty lakh rupees, and card payments. The Taxpayer Information Summary condenses these into category totals. Taxpayers can dispute entries online, with portal tracking showing responses. AIS reveals assets and debt, but cannot prove net cash flow due to duplicate entries.

An Income Tax Return is a self-declared statement of income filed under Section 139 of the Income-tax Act, 1961. The Central Processing Centre acknowledges filings on the e-Filing Portal with an ITR-V form. It confirms declared revenue. But an unaudited return remains a self-declaration that cannot prove declared revenue reached bank accounts.

Under tax rules reported by The Economic Times, Form 168 will unify Form 26AS and AIS starting in Tax Year 2026-27 under Rule 245. Form 26AS remains active for earlier filing cycles.

Underwriters verify repayment capacity by checking tax filings against bank cash flow.

Verification standards from Taxmann focus on cross-document triangulation. Lenders compare return revenue against Form 26AS tax deposits and AIS assets, matching them against operating bank credits.

For salaried applicants, credit teams verify bank account details by matching pay slips with bank deposits. They check these against employer tax deposits in Form 26AS. When an applicant claims salaried employment, Form 26AS typically reflects withholding under Section 192 from that employer. Discrepancies signal fabricated employment.

Mismatches across tax forms expose inflated income, concealed contracts, and synthetic tax records.

1. TDS Section Mismatches

Applicants often claim salaried roles, but Form 26AS shows deductions under Section 194J for professional fees or Section 194C for contractor work. Salary withholding confirms formal employment. Contractor deductions reveal gig fees that lack stability.

2. Shell Deductors

Rogue brokers register shell firms to deposit nominal withholding under professional fee codes against fake invoices. This creates an authentic Form 26AS credit on tax portals. Lenders spot this pattern by checking the deductor's corporate age, office address, and GST compliance.

3. Presumptive Turnover Inflation

Small businesses filing under Section 44AD presumptive rules do not maintain audited books. They declare an assumed profit on revenue. Rogue borrowers inflate turnover on form ITR-4 to raise borrowing limits. Credit teams catch this by comparing declared turnover with bank deposits.

4. Post-Sanction Revised Returns

Some borrowers file an initial return with inflated income to secure credit. After disbursal, the borrower files a revised return under Section 139(5) to cut declared income and taxes. Lenders defend against this by checking the assessment Intimation under Section 143(1), validating acknowledgment numbers, and running covenant audits.

Direct data integrations mitigate tampering risks common in manual reviews.

Scanned paper and PDF records are vulnerable to digital edits. Rogue applicants alter names, PANs, and income numbers. Lenders deploy automated workflows to catch bank statement fraud.

Under Reserve Bank of India rules described by Sahamati, Account Aggregators transfer banking data directly between institutions. Encrypted pipelines protect against document tampering and forgery.

Direct tax verification uses statutory pipelines. Section 138(1)(a) of the Income-tax Act, 1961 allows the tax department to share compliance data with commercial banks, as confirmed in Ministry of Finance verification directives. Automated tools verify return credentials. In flow-based MSME underwriting, lenders combine tax filings with monthly GST records and live bank feeds to assess repayment capacity.

A structured verification framework prevents credit teams from mistaking paper declarations for actual liquidity.

This suggests that treating an acknowledged tax return as complete proof exposes portfolios to paper inflation. An ITR acknowledgment confirms only that a filing was received. The practical implication is that credit policies benefit from requiring cross-matching declared revenue against Form 26AS deposits.

Read together, recurring withholding mismatches and shell deductor filings mean that tax deduction entries also require scrutiny. An authentic tax credit proves that money reached the government, but does not prove commercial substance. Underwriters typically confirm that deductors are genuine operating businesses and that withholding codes reflect stable employment.

The operational takeaway for risk heads is that tax forms and bank feeds measure different dimensions of borrower health. Tax filings show statutory compliance. Bank feeds verify daily liquidity. Automating this cross-check through direct tax interfaces and Account Aggregators helps catch discrepancies before funds disburse.