API Category · Financial Assessment
Reading a statement tells you what it says. Analysing it tells you what it means for a lending decision. Document Analyzer does the second part, so your credit team starts from an assessment instead of a spreadsheet.
Trusted Across Indian BFSI
Banks, NBFCs, housing finance companies and co-operative banks run verification, Aadhaar masking and document workflows on FinHub, inside their own compliance and audit requirements.
Prüfens Advisory
In short
A document analyzer goes beyond extraction. Where OCR returns the contents of a financial document, an analyzer returns an assessment of it for underwriting. FinHub's Document Analyzer covers bank statements from one bank or several, income tax returns and credit card statements. It supplies the analysis, and the credit decision stays with your policy.
- Bank statement analysis, for a single bank or across several
- ITR analysis for income tax returns
- Credit card statement analysis
- Part of the same API platform as Smart OCR and the verification APIs: one key, one SLA
2 APIs
Every API in Document Analyzer
One integration, one authentication and one response shape across the whole category.
Reference
What Each API Returns
The endpoint and the fields that come back, so you can size the integration before you write any code.
| API | Endpoint | Key fields returned |
|---|---|---|
| Bank Statement Analysis | POST /v1/financial/bank-statement/analyze | Income & salary estimate · Average balance & cash flow · Bounce & obligation signals · Tampering / fraud flags |
| ITR Analysis | POST /v1/financial/itr-analysis | Gross total income · Tax paid · Income trend · Filing status · Extraction confidence |
Reading a Statement Is Not the Same as Analysing It
Where Smart OCR stops and Document Analyzer starts
Take a twelve-month bank statement with a few hundred transactions. Smart OCR can lift every row into structured data: date, narration, amount, running balance. That is a good start and a long way short of a decision.
Someone still has to work out what those rows add up to for the loan in front of them. That interpretation is the step Document Analyzer is built for.
Use Smart OCR when you need the contents of a document in your system. Use Document Analyzer when you need to know what those contents mean.
Where It Sits in a Lending Journey
From documents to a decision
Four steps, and only the last one is yours alone.
01. Collect. The customer provides the statements, returns or card statements your policy asks for, through your app, your branch or a link.
02. Read. Where a file arrives as a photograph or a scan, Smart OCR reads it into structured data first.
03. Analyse. Document Analyzer works through the document and returns its assessment.
04. Decide. Your credit policy takes it from here, with your own thresholds applied to what the analyzer returns.
- consent.capture
Consent captured · DPDP Section 6(1)
- pan.verify
PAN verified against ITD
- aadhaar.ekyc
Aadhaar eKYC · OTP consent
- face.match
Face match · liveness passed
- decision.rule
Auto-approved · low risk
Why Look at Statements When There Is a Bureau Score?
History tells you how someone repaid. A statement shows what is happening now.
A credit bureau report records how a borrower has handled credit in the past. It says little about this month's income, this month's obligations or whether the account is running dry. For borrowers with a thin bureau file, it may say very little at all.
A bank statement fills that gap with current cash flow. Most underwriting teams read the two together rather than choosing one. For more on how lenders use the statement side, see the blog on bank statement analysis for credit decisions.
What to ask every vendor
Same questions · every shortlist
- API breadth and catalogue coverage
- Depth of DPDP consent governance
- Audit evidence and data residency
- Uptime, SLA and support model
- Commercials and contract shape
Compare approaches, not adjectives
Reference
Every Analyzer in the Category
One integration, one authentication and one response shape across the whole category. See the Bank Statement Analyzer page for the single-bank analyzer in detail.
Financial assessment
| API | Tag | Works on |
|---|---|---|
| Bank Statement Analyzer | Financial · Underwriting | A bank statement from a single account |
| Multi-Bank Statement Analyzer | Financial · Underwriting | Statements from more than one bank, assessed together |
| ITR Analyzer | Financial · Underwriting | Income tax returns |
| Credit Card Analyzer | Financial · Underwriting | Credit card statements |
Terms
Terms Worth Getting Right
The distinctions that decide whether a flow stands up under examination.
- FOIR (fixed obligations to income ratio)
- The share of a borrower's monthly income already committed to fixed repayments such as existing EMIs. Lenders set a ceiling for it, and it is one of the most common checks run on a statement.
- Average monthly balance
- The typical balance an account holds across a month. A steady figure suggests a borrower with room to absorb an EMI. A balance that drops to near zero soon after each credit is a different story.
- Inward return
- A cheque or auto-debit instruction against the account that came back unpaid, usually for insufficient funds. One may be an accident. A pattern is a signal.
- Declared income
- The income a borrower reports to the tax authorities in an ITR. It is worth setting against what the bank statements show coming in.
FAQ
Document Analyzer, Common Questions
A document analyzer API reads a financial document and returns an assessment of it rather than just its text. FinHub's Document Analyzer covers bank statements, multi-bank statements, income tax returns and credit card statements, and is built for underwriting.
Related categories
Nearby on the API Platform
Last updated · 12 October 2026
Run it on your own statements
Bring a handful of real statements and ITRs, and see what the analysis returns on your borrowers' documents rather than on a demo file.