LenderAnalyzer reads the bank statements your applicants upload and returns true revenue, average daily balance, NSF and negative days and existing loan payments, by upload or REST API, so your decision rules run on clean numbers. From $99 a month, API on the Pro plan.
Upload a document to extract
Drop files here or click to upload
Up to 50 files
Uploading...
Upload a bank statement and watch the analysis run live, free, no signup required.
A fintech lender lives or dies on how fast it can turn an applicant's PDF statements into numbers its decision rules trust. Most online small business lenders, revenue-based financing providers and embedded lenders still have an ops team keying deposits into a spreadsheet, or they rely on raw deposit totals that count owner transfers and other funders' advances as revenue. LenderAnalyzer does the reading. Post the statements by upload or through the API and get back monthly true revenue net of transfers and loan proceeds, average daily balance, NSF and negative-day counts and the recurring debits of existing lenders, with every figure tied to the transaction it came from and exportable to CSV and XLSX.
Bank connectivity tools pull transactions when the applicant links an account. Many applicants will not link, or the bank is not supported, so the PDF remains the fallback that decides whether the file moves today or sits in a queue. That fallback is the job this tool is built for. It does not score applicants, approve loans or replace your decision engine; it feeds them.
Here is the kind of file an online small business lender sees every day. The numbers are illustrative, not a real applicant, but the arithmetic is exactly what a rules engine runs.
A landscaping company applies online for a $40,000 advance and uploads three months of business checking statements. Total deposits are $186,400, so a rule that reads raw deposits sees $62,133 a month. Two existing funders debit $310 and $305 every business day, which is $615 a day or about $12,915 a month across 21 business days. Against raw deposits that is a 20.8% holdback, under a typical 25% stacking cap, and the file passes automatically.
LenderAnalyzer separates $22,600 of transfers from the owner's personal account and $30,000 of loan proceeds from another funder. True revenue is $133,800, or $44,600 a month. The same $12,915 of daily debits is now 29.0% of true revenue, over the cap. Average daily balance comes back at $8,950 with four NSF items in the most recent month, and the second funder's debits started six weeks ago, a stacking signal the raw total hides.
The automated approve becomes a counter or a decline, depending on your policy. At a 25% cap, total holdback on $44,600 can be $11,150 a month, and existing debits already exceed it, so there is no room for a new daily payment until one position pays off. Funding this file on raw deposits is how an online lender buys a loss it could have seen in the PDF. Every figure above is traceable to a line on the statement, so an underwriter can check the call in a minute.
Small ops teams use the web app: drop the PDFs, read the metrics, export CSV or XLSX into the file. Engineering teams on the Pro plan call the REST API, upload the statements, request extraction and fetch the structured results and income calculation by document hash, then map the fields into their own decision engine. Requests are rate limited per account, so batch large backfills.
Building an in-house parser means handling thousands of bank layouts, scanned pages, multi-account statements and running balance checks, then maintaining it every time a bank redesigns its PDF. That is a permanent engineering line item. Buying the analysis layer lets the team spend its sprints on credit policy, pricing and the borrower experience, and keep the option to bring parsing in-house later if volume ever justifies it.
Most vendors in this category sell by quote. Confirm current pricing and coverage with each one before you sign.
Swipe sideways to see the full comparison
| Option | What it does | Works without account linking | Pricing | Best for |
|---|---|---|---|---|
| LenderAnalyzer This page | Reads PDF statements, returns true revenue, ADB, NSFs, negative days and existing debt payments | Yes, PDF upload or API | Published, from $99/mo, API on Pro | Online small business, RBF and MCA fintechs that want clean metrics fast without a sales cycle |
| Ocrolus | Document capture and cash flow analytics with human review options | Yes | Per vendor quote | High-volume lenders that want a large enterprise vendor and can run a procurement process |
| Plaid | Bank account connectivity and transaction data when the applicant links | No, needs a linked account | Usage based, per vendor | Lenders whose applicants reliably link accounts |
| Inscribe | Document fraud detection with credit analysis features | Yes | Per vendor quote | Teams whose main loss driver is altered documents |
| In-house parser | Whatever your engineers build and keep maintaining | Yes, for the layouts you support | Engineering salaries | Very high volume lenders with a dedicated data team |
Comparison compiled by LenderAnalyzer from public vendor materials; see the date noted above each table. Competitor names are trademarks of their respective owners; figures may change, so verify current details with each vendor.
Computed deterministically from every extracted transaction, every figure traceable to its source line.
Computed across the full statement period, carried forward day by day.
Deposits vs withdrawals and net flow, broken down month by month.
Every insufficient-funds and overdraft incident counted, with fees totaled.
Recurring deposits grouped into income streams with estimated monthly amounts.
Debits to other lenders and funders detected and totaled per month.
Days below zero across the period, a direct stress signal.
The biggest credits with dates and sources, concentration flagged.
Automatic red and yellow flags your analysts can review in seconds.
Drop in PDFs, scans or photos, one statement or a multi-month package, from any bank.
Every transaction is extracted, then cash flow, balances, income streams, NSF activity and debt payments are computed.
Read the underwriting snapshot, download the Excel report, or pull structured JSON into your LOS via API.
28 lending document types extracted out of the box, build the complete picture of an applicant's financial situation.
Common questions from lending and credit teams.
The best fit returns decision-ready metrics, not just extracted rows, and works when the applicant will not link a bank account. LenderAnalyzer reads PDF statements and returns true revenue, average daily balance, NSF and negative days and existing loan payments, by upload or REST API, with published plans from $99 a month.
They pull three to six months of business statements, remove transfers and loan proceeds from deposits to get true revenue, then measure average daily balance, NSF and negative days and the debits of existing funders. Those numbers feed the decision rules, such as minimum revenue, maximum holdback and stacking limits.
Usually yes. A share of applicants will not link, their bank is not supported, or the connection drops before funding. PDF statements are the fallback, and if your team keys them by hand those files are the slowest in the queue. Analysis software handles the PDFs so every applicant gets the same speed.
Yes. On the Pro plan you can upload statements, request extraction, fetch the structured results by document hash and pull the income calculation through a REST API, then map the fields into your own decision engine. Smaller teams use the same analysis in the web app with CSV and XLSX export.
Enterprise vendors usually quote per document or per year after a sales process. LenderAnalyzer publishes its prices: Starter $99, Plus $199 and Pro $399 a month, with volume plans up to $3,990 a month and a discount on annual billing. API access is included from the Pro plan.
It lists the recurring debits of existing lenders and funders, with amounts and start dates, so you can see a new position that appeared in the last few weeks and measure total holdback against true revenue. Whether a file is declined for stacking stays a decision for your credit policy.
How credit teams run these calculations by hand, so you can see exactly what the software automates.
Pricing models and who each option fits.
Endpoints, fields and how the JSON maps into a decision engine.
Spot existing funders' daily debits before you add another.
Size remittances on true revenue, not raw deposits.
Underwrite thin-file borrowers on what moves through the account.
What an in-house parser really costs to maintain.
Analyze your first statements free, plans from $99/month, 50% off billed annually.