Bank statement tax reconciliation for ITR filing
Don't wait for a notice under section 143(1). CleanStatement extracts your savings interest, separates FD maturity from accrued interest, and allows you to cross-check your bank statement against your AIS locally — entirely in your browser without uploading your sensitive data.
Why the AIS mismatch happens
The most common ITR mistakes involve missed interest income. Savings interest doesn't trigger TDS, so it often escapes the 26AS trail. FD interest might have TDS deducted, leading people to wrongly assume the tax liability is fully settled.
Mismatches against the Annual Information Statement (AIS) now generate automated notices. The fix today is manual statement archaeology — matching rows one by one.
The CleanStatement ITR Tax Pack
CleanStatement completely automates the preparation of your bank statement for tax filing:
- Savings-interest credits are totalled automatically, ready for your 80TTA (₹10k) or 80TTB (₹50k) deduction.
- FD interest and FD principal maturity are separated accurately so you don't overpay tax on principal returns.
- TDS debits and credits are itemized with dates, ready to check against your Form 26AS.
100% On-Device Privacy
Your financial records are sensitive. CleanStatement runs entirely in your browser — your bank statement is never uploaded to any server. You can even disconnect your internet while processing.
Frequently asked questions
Is CleanStatement really free?
Yes. Cleaning a bank statement, verifying its running balance and downloading the cleaned Excel are free, with no sign-up. Advanced features such as the ITR Workbench, multi-statement merge and accounting-software voucher exports are currently open to everyone during the launch period.
Is my bank statement uploaded to a server?
No. Every step — reading the PDF, detecting the bank, cleaning, verifying balances, classifying and generating the Excel — runs inside your browser tab using JavaScript. There is no upload, no backend and no third-party API. You can disconnect from the internet after the page loads and the tool still works.
Which Indian banks are supported?
Over 21 banks are detected automatically, including HDFC, ICICI, SBI, Axis, Kotak Mahindra, IDFC FIRST, IDBI, YES Bank, IndusInd, Federal, RBL, AU Small Finance, Bandhan and the public-sector banks PNB, Bank of Baroda, Canara, Union Bank, Bank of India, Indian Bank, Central Bank and UCO. Statements from banks without a stored profile still clean successfully because the columns are inferred from the data.
Can it convert a password-protected PDF statement?
Yes. If the PDF is encrypted, the tool prompts for the password and decrypts it locally in your browser. The password is never transmitted anywhere.
Does it work with scanned bank statements?
Not yet. CleanStatement reads text-based PDFs — the kind your bank generates when you download a statement. A scanned or photographed statement is an image and needs OCR, which is on the roadmap as a local, on-device step so the no-upload promise holds.
What does the balance verification actually check?
It recomputes the running balance row by row from the opening balance and every debit and credit, then compares each computed figure against the balance printed on the statement. If any row fails to reconcile, it is flagged. This is what catches both parsing errors and tampered statements.
How is this different from a generic PDF-to-Excel converter?
A generic converter gives you the same mess in a spreadsheet: junk rows, wrapped narrations split across lines, dates as text and amounts that will not sum. CleanStatement understands that the file is a bank statement — it strips repeated headers, re-joins wrapped narrations, normalizes Indian date and lakh/crore amount formats, re-orders newest-first statements, verifies the running balance and classifies every row to an accounting ledger head.