- About Riskpro Technology — who we are and what we do
- What is the Bank Statement Analyser? — overview and purpose
- Core Features — the full capability set
- How BSA Works — the step-by-step workflow
- Output Formats & Reports — what you receive
- How BSA Helps Investigators — real-world investigative value
- Strengthening Forensic Auditors — audit-grade analysis
- Compliance & Regulatory Use Cases — AML, KYC, regulatory reporting
- Supported File Formats — what can be ingested
- Frequently Asked Questions
Automate Forensic Audit Reporting
Forensic audit reports are driven by trends and patterns in transaction data. BSA automates the extraction of those patterns — fund flows, related party exposures, timing clusters — making forensic reporting dramatically faster and more cost-effective than traditional manual analysis.
Red-Flag Reports for Compliance Teams
Compliance professionals simply upload their bank statements and receive automated red-flag reports that surface potential anomalies — unusual transaction volumes, structuring patterns, related party flows, and transactions lacking any identifiable counterparty — without manual review of every row.
Any Format In, One Format Out
Upload bank statements in any format — PDF, scanned image, Excel, CSV, text file — from any bank. The output is always a single, clean XLSX or CSV Consolidated Ledger with a uniform column structure, regardless of how many different banks or formats were in the project.
About Riskpro Technology
“Riskpro Technology builds intelligent analytical tools that transform raw financial data into court-ready evidence, actionable compliance intelligence, and clear forensic narratives.”
Riskpro Technology is an Indian financial technology firm specialising in forensic analytics, compliance intelligence, and investigative tools for the financial services sector. Founded to bridge the gap between raw banking data and meaningful financial intelligence, Riskpro serves a diverse clientele including banks and NBFCs, insolvency resolution professionals, government investigating agencies, forensic accounting firms, and compliance consultants.
Riskpro’s philosophy is that financial data should speak for itself — given the right analytical framework. The Bank Statement Analyser (BSA) is the flagship expression of this philosophy, purpose-built to do in minutes what a team of analysts would take days to accomplish manually.
Financial Forensics
Deep investigative tools built for banking-sector complexity and Indian financial market realities.
Compliance Intelligence
AML, KYC and regulatory reporting support aligned to RBI, SEBI and PMLA frameworks.
Investigation Support
Purpose-built outputs for ED, CBI, SFIO, IRP and bank fraud investigation units.
What is the Bank Statement Analyser?
The Bank Statement Analyser (BSA) is a cloud-based, multi-format bank statement processing engine that ingests raw bank statement files — in any format a bank might produce — and converts them into a standardised, analysis-ready financial dataset enriched with entity identification, transaction tagging, and investigative reporting.
In a typical investigation or audit, an analyst receives bank statements from dozens of different banks in incompatible formats: some are scanned images, some are machine-generated PDFs, some are Excel exports, some are plain CSV files. Every bank formats its statements differently. Reconciling them manually is error-prone, slow, and expensive.
BSA eliminates that problem entirely. It ingests all of them, normalises them into a single unified ledger, identifies who each party in the transactions is, and generates reports that an investigator or auditor can act on immediately.
💡 Key distinction from generic accounting software
BSA is not bookkeeping software. It does not post journal entries or produce balance sheets. It is an investigative intelligence tool — designed to reveal relationships, patterns, and anomalies hidden within raw bank transaction data.
Core Features
Multi-Format Ingestion
Accepts PDF (digital and scanned), XLSX, XLS, CSV, TXT, and scanned image files. No reformatting required before upload.
Normalisation Engine
Maps every bank’s unique column structure to a single canonical format: Date, Particulars, Debit, Credit, Balance.
Entity Extraction
Automatically identifies counterparty names from narrations using multi-pass extraction: RTGS/NEFT codes, UPI IDs, cheque patterns, and direct name detection.
Confidence Scoring
Every extracted entity carries a confidence score (0–100%) so analysts know which identifications are certain and which require human review.
Related Party Detection
Build a Knowledge Base of companies, directors, and bank accounts. BSA automatically tags every transaction involving a related party.
Multi-Statement Projects
Group all statements for one client or investigation into a single Project. Analysis and reports span the entire dataset, not just one statement.
Anomaly Flagging
Identifies blank records, round-figure transactions, unusual volume days, and transactions with no matching entity — all surfaces for investigation.
Branded PDF Reports
Every report is generated as a professionally branded, confidential PDF, XLSX, or CSV — ready for inclusion in audit files or court submissions.
API Access
Full REST API for integration with case management systems, banking platforms, and compliance workflows. Includes rate limiting, key management, and webhook support.
How BSA Works — Step by Step
From raw file upload to a complete investigative report, BSA follows a structured five-stage workflow.
Create a Project
Each investigation or audit engagement is managed as a Project. Projects hold all the bank statements for one subject entity and define the Knowledge Base (companies, directors, related parties) against which transactions will be matched. A project can span multiple banks, multiple accounts, and multiple time periods.
Upload Bank Statements
Upload statements in any supported format — PDF, XLSX, XLS, CSV, TXT, or scanned image. Each file is tagged with its Bank Name, Account Number, Account Name, and Account Type (Current, Savings, CC, OD, Term Loan, etc.) at upload time. Multiple statements from different banks can be uploaded into the same project simultaneously.
Map & Process
BSA’s Column Mapper presents the raw file and asks the analyst to identify which columns correspond to Date, Particulars, Debit, Credit, and Balance. For standard bank formats, this is a one-click operation. Once mapped, BSA processes the entire statement, normalising dates, cleaning amounts, and running the entity extraction engine on every narration.
Entity Tagging & Related Party Matching
BSA’s three-pass matching engine runs against the project’s Knowledge Base: first an exact match (account numbers, CINs, DINs, known aliases), then a fuzzy match using Levenshtein distance and abbreviation expansion, then a pattern match for RTGS/NEFT IFSC codes. Every transaction is tagged with the identified counterparty and a confidence score. The ML engine also suggests new aliases for analyst review, learning as the project grows.
Generate Reports
With the project fully processed, generate any of the seven available report types in PDF, XLSX, or CSV. Reports are branded with the Riskpro Technology mark, timestamped, and marked CONFIDENTIAL. The consolidated XLSX export can be downloaded at any time and contains the complete ledger for all statements in the project.
Output Formats & Reports
from any bank, in any layout
with a uniform structure across all statements
Consolidated Ledger — the master output
Regardless of the format you upload — scanned PDF, Excel, CSV or image — the output is always a single XLSX or CSV Consolidated Ledger that unifies every statement in the project into one analysis-ready file. The ledger carries the following standardised columns for every transaction:
Analytical Reports — 7 types, 3 formats each
How BSA Helps Investigators
Financial investigators — whether from the Enforcement Directorate, CBI, SFIO, SEBI, income tax departments, or private fraud investigation units — routinely face the challenge of making sense of thousands of bank transactions spread across multiple accounts, banks, and years. BSA is designed specifically for this environment.
From weeks to hours
- What once required two weeks of analyst time is now done in hours
- Instant normalisation removes the manual reformatting bottleneck
- Automated entity extraction eliminates manual narration reading
Reduce human error
- Consistent rule-based processing removes transcription errors
- Confidence scoring highlights where human review is still needed
- Variant name consolidation prevents double-counting
Follow the money
- Entity report maps the full network of counterparties
- Related party tagging surfaces director/group transactions instantly
- RTGS/NEFT IFSC extraction traces funds to specific banks
Specific investigative applications
Layering Detection
Multi-account analysis reveals circular fund flows — money that leaves account A, passes through B and C, and returns to A — a classic money laundering layering pattern.
Loan Diversion
When a borrower receives a loan disbursement and immediately routes it to related parties, the entity report and largest debits report together surface this within minutes.
Timing Analysis
Busiest days report reveals if large transactions are clustered around specific dates — financial year-end window dressing, pre-NPA settlement payments, or coordinated fund movements.
Related Party Flows
Transactions with entities listed as promoters, directors, or group companies are automatically tagged, making it straightforward to quantify the full related party exposure.
✅ Evidential integrity
BSA does not modify source data. The original narration is always preserved in the Particulars column. The Extracted Entity Name is an additional analytical layer, never a replacement. This maintains a clear chain of custody between the original bank record and the analytical output.
Strengthening Forensic Auditors
Forensic auditors engaged under IBC assignments, bank-appointed forensic investigations, or SFIO/SEBI directed audits face specific professional and legal obligations that BSA is designed to support.
Built for the Indian forensic audit environment
BSA is built around the realities of Indian banking formats, RTGS/NEFT narration structures, IFSC coding, and multi-lender consortium environments.
Consortium Accounts
Upload statements from all consortium banks into one project. BSA produces a single consolidated ledger covering the entire credit exposure across all lenders simultaneously.
Long-Period Analysis
No restriction on the date range. A forensic audit covering eight years of banking across five banks and twelve accounts is handled identically to a single statement.
Related Party Mapping
Build the Knowledge Base from the company’s ROC filings — directors, subsidiaries, associate companies — and BSA quantifies every rupee that moved to or from connected entities.
Court-Ready Reports
All reports are dated, project-labelled, and marked CONFIDENTIAL. PDF reports are suitable for inclusion in forensic audit reports submitted to courts, NCLT, or regulators.
How BSA maps to standard forensic audit procedures
Fund flow analysis
The Entity Extraction Report and consolidated ledger together provide the complete fund flow picture required under forensic audit standards. Every counterparty is identified, every amount is traceable to its source narration, and the entire dataset is exportable for further analysis.
Diversion of funds
By tagging related parties against the loan disbursement dates and amounts, BSA produces a direct answer to the core forensic question: “Where did the money go after disbursement?” The Largest Debits report sorted by date shows the sequence of outflows in the days following each disbursement.
Genuine business activity verification
The entity extraction and bank summary reports allow auditors to assess whether the volume of transactions, counterparty diversity, and transaction sizes are consistent with the company’s stated business activity — or whether the account shows signs of a shell company or conduit account.
Reconciliation of balance sheet
The consolidated ledger provides a transaction-level basis for reconciling balance sheet items with actual bank movements, supporting the verification of trade creditors, debtors, and unsecured loans claimed in financial statements.
Compliance & Regulatory Use Cases
Compliance professionals in banks, NBFCs, and financial institutions face increasing regulatory scrutiny around transaction monitoring, AML compliance, and KYC verification. BSA provides the analytical backbone for these requirements.
Anti-Money Laundering
- Identify structuring (transactions just below reporting thresholds)
- Detect layering across multiple accounts
- Quantify total flows to/from high-risk entities
- Surface unusual transaction timing patterns
Enhanced Due Diligence
- Verify account activity matches stated business purpose
- Identify counterparties the customer is transacting with
- Establish a normal transaction profile for anomaly detection
- Support periodic review of high-risk accounts
Credit Assessment
- Cash flow verification from bank statements for lending decisions
- Identify circular transactions that inflate apparent turnover
- Verify utilisation of existing credit lines
- Assess actual vs. claimed business activity
Insolvency Resolution
- Trace assets moved before insolvency filing
- Identify preferential transactions under Section 43/66 IBC
- Map related party payments in the vulnerability period
- Produce NCLT-ready fund flow reports
⚠️ PMLA alignment
BSA’s entity extraction and transaction tagging capabilities directly support the reporting and record-keeping obligations under the Prevention of Money Laundering Act, 2002. Suspicious transaction patterns surfaced by BSA can form the factual basis for STR filings with the FIU-IND.
Red-Flag Anomalies — what BSA surfaces automatically
Compliance teams do not need to read thousands of rows. After uploading bank statements, BSA’s automated reports flag the following categories of potential anomaly for review:
Supported File Formats
BSA accepts bank statements in every format commonly produced by Indian and international banks. There is no need to pre-convert files before uploading.
ℹ️ File size limit
Individual files up to 50 MB are supported. There is no limit on the number of files per project. Consortium cases with hundreds of statements are handled routinely.
Frequently Asked Questions
Yes. Because BSA uses a column mapper rather than bank-specific templates, it works with statements from any bank in any format. The analyst maps the columns once per statement type, and BSA handles the rest.
For RTGS and NEFT transactions with standard narration formats, accuracy is typically 90–95%. For UPI and IMPS transactions, 85–90%. For cheque transactions and non-standard narrations, 70–85%. The confidence score on every row tells the analyst exactly how reliable each extraction is.
All uploaded files and processed data are stored in a secured environment with access controls at the project level. Each project is owned by the user who created it. The Admin role has visibility across all projects; the Author role can only see their own projects. Data is not shared between organisations.
BSA reports are analytical outputs derived from the original bank statements, which are themselves the primary documents. The reports are suitable for inclusion in forensic audit reports, NCLT filings, and regulatory submissions. Consult your legal counsel for jurisdiction-specific admissibility advice.
Yes. BSA has a full REST API with API key management, rate limiting, and webhook support. This allows integration with existing case management systems, loan origination platforms, and compliance workflows.
Currently, projects are owned by the user who creates them. Administrators have full access to all projects. Multi-user project sharing within a team is on the product roadmap.
The Knowledge Base is the project’s registry of related parties — the companies, directors, subsidiaries, and group entities connected to the subject account. When populated, BSA runs a three-pass matching engine that tags every transaction involving those parties, regardless of how the name is spelled in the narration. A project with an empty Knowledge Base still performs entity extraction but cannot perform related party matching.
Riskpro Technology — Bank Statement Analyser
This document is for training and informational purposes. Contents are confidential and proprietary to Riskpro Technology. © Riskpro Technology. All rights reserved.