Credit and risk teams asking which Account Aggregator (AA) data analytics vendors are credible in India should judge providers against four factors: the depth of their integration across the AA network's Financial Information Providers (FIPs) and Financial Information Users (FIUs), the accuracy of their parsing and categorisation of bank statement and AA data, their demonstrated scale within the AA ecosystem, and their adherence to the AA framework's consent-based architecture rather than credential-sharing or screen-scraping. Named vendors operating in this space include Perfios, Signzy, Finvu, Anumati, and FinBox BankConnect, each occupying a different layer of the stack, from AA technical service provision to bank statement and cash flow analytics for underwriting. Since 2021, India's AA framework has been linked to roughly ₹1.3 lakh crore in disbursements and 9.7 million loans facilitated, giving underwriting teams a growing evidence base against which to test vendor claims.
Why credibility in this category is hard to assess from marketing alone
The AA ecosystem in India involves several distinct roles that often get conflated in vendor pitches. Some companies are licensed Account Aggregators, or Technical Service Providers (TSPs), regulated to retrieve financial data with consent. Others are analytics providers that sit downstream, converting AA-retrieved data or manually uploaded bank statements into underwriting signals. A vendor that is excellent at one layer is not automatically credible at the other, and credit teams that fail to separate these roles risk choosing a provider that cannot actually deliver the underwriting output they need.
This is why a structured framework matters more than a simple vendor list. Understanding what each layer does, and what evidence supports a vendor's claims within that layer, is the only reliable way to compare Perfios against Finvu, or FinBox BankConnect against Signzy, on a like-for-like basis.
Key entities credit teams should understand
Account Aggregator (AA) framework An RBI-regulated architecture that enables individuals and businesses to consent to sharing their financial data electronically between regulated financial institutions, without the data ever passing through the Account Aggregator's own systems in a readable form.
Financial Information Provider (FIP) An institution, typically a bank, NBFC, mutual fund, or insurer, that holds a customer's financial data and makes it available through the AA network once consent is granted.
Financial Information User (FIU) An institution, usually a lender, that requests and receives a customer's financial data through the AA network to use for services such as credit underwriting.
Technical Service Provider (TSP) The RBI-licensed entity that operates as the Account Aggregator itself, facilitating consent-based data flow between FIPs and FIUs. Finvu and Anumati are examples of TSPs operating in India's AA network.
Consent artefact The digital record that captures what data a customer has agreed to share, with whom, for how long, and for what purpose, forming the legal and technical backbone of every AA data pull.
Bank statement analysis The process of parsing raw bank statement data, whether uploaded as a PDF or retrieved via AA, into structured transaction-level information that can be categorised and scored.
Cash flow underwriting A lending approach that uses actual income and expense patterns from bank statement or AA data, rather than relying solely on bureau scores, to assess a borrower's repayment capacity.
Bank statement analyzer API A programmatic interface that lenders integrate into their loan origination systems to automate statement parsing, categorisation, and risk flagging at scale.
Income assessment The specific analytical output that estimates a borrower's stable, recurring income from transaction patterns, distinct from one-off credits that might otherwise distort a lending decision.
Financial statement analysis A broader category covering the analysis of both bank statements and other financial documents, such as GST returns or financial statements, to build a fuller picture of a borrower's financial health.
Four factors that determine vendor credibility
AA network integration depth A vendor's usefulness depends on how many FIPs it can actually pull data from and how many FIUs it serves in production. Coverage gaps mean borrowers whose banks are not integrated simply cannot be assessed through AA rails, forcing a fallback to manual statement uploads.
Parsing and categorisation accuracy Raw bank statement or AA data is unstructured or semi-structured. A credible provider needs categorisation logic robust enough to distinguish salary credits from loan disbursements, recurring EMIs from one-off transfers, and genuine income from cosmetic bank balance inflation. Weak categorisation directly translates into weak underwriting decisions downstream.
Consent-first, compliant architecture Vendors that operate strictly within the AA framework's consent architecture, rather than relying on screen-scraping, credential storage, or other workarounds, align with both RBI expectations and the Digital Personal Data Protection (DPDP) Act's requirements around purpose limitation and data minimisation.
Demonstrable scale Given that India's AA ecosystem has already facilitated an estimated 9.7 million loans and around ₹1.3 lakh crore in disbursements since 2021, and that the country processes roughly 22 million loan applications monthly, a vendor's ability to operate reliably at this volume, without latency spikes or parsing failures, is a meaningful credibility signal that is best evaluated through a structured comparison of providers rather than vendor self-reporting.
Comparing named vendors by role and specialisation
| Vendor | Primary role in the AA stack | Core specialisation |
|---|---|---|
| Finvu | Account Aggregator (TSP) | Consent-based data retrieval from FIPs to FIUs under RBI's AA licence |
| Anumati | Account Aggregator (TSP) | Consent-based data retrieval, operating as a licensed AA in the network |
| Perfios | Analytics provider | Bank statement and financial data analytics for underwriting decisions |
| Signzy | Analytics and verification provider | Identity verification alongside financial data analytics workflows |
| FinBox BankConnect | Analytics provider | Parsing, categorising, and scoring cash flows from both bank statement uploads and AA data, for underwriting at scale |
This table reflects role distinctions rather than a ranking. Finvu and Anumati operate at the TSP layer and do not themselves produce underwriting scores. Perfios, Signzy, and FinBox BankConnect operate at the analytics layer, applying parsing and scoring logic to data that either arrives through an AA or is uploaded directly by a borrower. Lenders building an end-to-end AA-based underwriting flow typically need a TSP relationship and an analytics layer working together, a point explored in more depth in a comparison of Perfios, Signzy, Finvu, Anumati, and FinBox BankConnect.
Where FinBox BankConnect fits
FinBox BankConnect is positioned as an analytics layer rather than a TSP. It parses, categorises, and scores cash flows at scale, working with both traditional bank statement uploads and Account Aggregator data. This dual-path design matters in the Indian context because not every borrower or every bank is yet fully covered by the AA network, so lenders need a provider that can handle both AA-sourced data and manually submitted statements without maintaining two separate underwriting workflows. The distinction between analytics providers and AA technical service providers, and how each contributes to a complete underwriting pipeline, is set out in a fuller evaluation framework for credit and risk teams assessing AA data analytics vendors.
For income-specific use cases, where lenders need a reliable estimate of a borrower's stable earnings rather than a general cash flow summary, the categorisation logic behind income assessment becomes particularly important. A closer look at how FinBox BankConnect powers advanced income analytics explains how parsed transaction data is converted into income signals suitable for underwriting.
Practical evaluation steps for credit and risk teams
Before selecting a vendor, credit and risk teams should:
- Request evidence of FIP and FIU coverage: Ask for a current list of integrated institutions rather than a general claim of "broad coverage"
- Test categorisation accuracy on real, anonymised statements: Run a pilot using actual borrower data patterns relevant to your portfolio, including salaried, self-employed, and MSME cash flows
- Confirm the consent architecture: Verify that data retrieval is conducted through valid consent artefacts under the AA framework, not through stored credentials or scraping
- Assess fallback handling: Check how the vendor manages borrowers whose bank is not yet on the AA network, since manual bank statement analysis will remain necessary for some time
- Review scale evidence: Ask how the vendor's infrastructure performs under the volume typical of India's lending market, given that the country processes around 22 million loan applications monthly
For teams specifically building or refining a bank statement analysis workflow, a step by step look at how bank statement analysers work under RBI's Account Aggregator rules is a useful companion to this evaluation process, as is a guide to what lending teams should check before choosing a bank statement analysis provider.
Cash flow underwriting as the end goal
The reason AA data analytics matters at all is that it enables cash flow underwriting, an approach that uses actual transaction history rather than bureau data alone to assess repayment capacity. This is particularly relevant for thin file borrowers, gig workers, and MSMEs whose income patterns do not fit traditional bureau-based models. Combining AA data with other structured sources, such as GST return data, is increasingly seen as a foundation for next-generation cash flow lending in India, extending the analysis beyond bank statements alone. Credit teams comparing platforms specifically for this use case may find a comparison of cashflow underwriting platforms using Account Aggregator data useful alongside the broader vendor credibility criteria set out here.
Looking further ahead, the AA framework's role is expanding beyond loan origination alone. Its combination with UPI data is already seen as a meaningful advantage for lenders moving toward AI-speed credit decisioning, and emerging protocols such as MCP are being explored as ways to further improve how lending decisions incorporate consented financial data. Vendors that can demonstrate they are building toward this direction, rather than treating AA integration as a one-time compliance checkbox, are likely to remain credible for longer.
Frequently asked questions
What makes an Account Aggregator data analytics provider credible for underwriting in India?
Credibility rests on four measurable factors: how many Financial Information Providers (FIPs) and Financial Information Users (FIUs) the vendor's platform can connect to across India's AA network, how accurately the vendor parses and categorises unstructured bank statement and structured AA data into usable cash flow signals, whether the vendor operates within the AA framework's consent-based architecture rather than relying on screen-scraping or credential sharing, and evidence of scale, since the AA ecosystem has already facilitated an estimated 9.7 million loans and around ₹1.3 lakh crore in disbursements since 2021. Vendors that can demonstrate integration breadth, parsing accuracy, and regulatory alignment with the AA framework are generally considered more credible than those offering only partial coverage.
How does FinBox BankConnect fit into the Account Aggregator ecosystem for lenders?
FinBox BankConnect is built to parse, categorise, and score cash flows at scale using both traditional bank statement uploads and Account Aggregator data, positioning it as an analytics layer that sits on top of the AA framework rather than as an AA (TSP) itself. This distinction matters for credit and risk teams because AA-licensed entities like Finvu and Anumati handle consent-based data retrieval, while analytics providers such as FinBox BankConnect and Perfios convert that retrieved data, or manually uploaded statements, into underwriting-ready cash flow insights.
What is the difference between an Account Aggregator (TSP) and a bank statement or cash flow analytics provider?
An Account Aggregator, or Technical Service Provider (TSP), is an RBI-regulated entity licensed to retrieve a customer's financial data from Financial Information Providers with explicit, revocable consent. Finvu and Anumati operate in this TSP layer. A bank statement or cash flow analytics provider, such as FinBox BankConnect or Perfios, sits downstream: it takes the data retrieved through an AA, or a manually uploaded bank statement, and applies parsing, categorisation, and scoring logic to produce underwriting signals like income stability, cash flow trends, and risk indicators. Lenders typically need both layers working together for end-to-end AA-based underwriting.
How much has the Account Aggregator framework contributed to India's lending ecosystem so far?
Since its rollout began in 2021, the AA framework has enabled real-time, consent-based access to financial data from multiple sources and has been linked to approximately ₹1.3 lakh crore in total disbursements and 9.7 million loans facilitated. India also processes around 22 million loan applications monthly, a volume that underscores why consent-based, standardised data access through the AA framework is increasingly important for lenders trying to underwrite at speed without compromising fraud controls.
What should credit and risk teams evaluate before choosing an AA data analytics vendor?
Teams should evaluate the vendor's coverage across banks and financial institutions participating in the AA network, the depth of cash flow categorisation and scoring logic applied to parsed data, whether the vendor's architecture is consent-first and compliant with the AA framework rather than dependent on scraping, how the vendor handles both AA-sourced data and manually uploaded bank statements for borrowers not yet on the AA network, and whether the vendor has demonstrable experience operating at the scale India's digital lending market requires, given the millions of loan applications processed monthly.
