# Bank Statement Analyzer: What to Look For Before Buying

- Author: TrueBankFlow (https://truebankflow.com)
- Published: 2026-10-16
- Category: Analysis software and reports
- Canonical: https://truebankflow.com/blog/bank-statement-analyzer

> What to look for in a bank statement analyzer before buying: traceable figures, layout coverage, exclusion rules and the real cost per loan file.
A bank statement analyzer should read a borrower's statements, sort the transactions, compute deposit averages and recurring income, and let a reviewer trace every figure to a statement line. Judge one on whether an underwriter can check its output quickly, how many layouts it reads, how it handles exclusions and what each file costs.

## Which bank statement analyzer features matter to underwriters?

The features that matter to underwriters are the ones that shorten review without hiding the math: traceable figures, editable exclusions, honest handling of unreadable pages, multi-account support, a report that fits the loan file, and a price you can predict. Use the ten points below as a scorecard on your own files.

### A ten-point evaluation scorecard

Score each point from 0 (absent) to 2 (clearly met) during a trial. A total near 20 means the tool fits the desk. The points are examples of what to test, not a standard.

| # | Point | What to test | Score (0-2) |
| --- | --- | --- | --- |
| 1 | Traceable figures | Click a monthly total. Does it list the statement lines behind it? | |
| 2 | Editable exclusions | Exclude one deposit. Do the averages change at once? | |
| 3 | Balance check | Feed in a statement with a missing page. Is it flagged, not averaged? | |
| 4 | Layout coverage | Run statements from the banks and credit unions you see most. | |
| 5 | Scanned pages | Run a phone photo or a scan. Is the output usable? | |
| 6 | Multiple accounts | Upload two accounts. Are transfers between them matched? | |
| 7 | Recurring income | Does it show source, cadence and average amount? | |
| 8 | Flags | Do large deposits, NSFs and overdrafts carry date and line? | |
| 9 | Report output | Does the report have your notes and the exclusions you chose? | |
| 10 | Cost per file | Can you predict next month's bill from your file count? | |

The rest of this post explains the three points that cause the most disagreement: traceability, layout coverage and cost. The others are quick to test in a single afternoon.

### Why exclusions belong in the top tier

Underwriting is full of judgment calls: whether a transfer counts, whether a one-time sale stays in. An analyzer that locks its answers forces the underwriter to rebuild the numbers in a spreadsheet, which defeats the purchase. Look for a tool that lets the reviewer include or exclude a deposit and recalculates the averages immediately, with the choice recorded in the report.

### Features that sound good and matter less

Dashboards, charts and score-style summaries make a good demo. They matter less than a plain table that reconciles to the statements. Ask what the reviewer will do with each output. If the answer is "look at it", it is decoration. If the answer is "put it in the file", it earns its place.

## Traceable figures in a bank statement analyzer

A traceable figure is a number the reviewer can follow back to the exact statement lines that produced it. Traceability matters because an underwriter signs off on the figure, not on the software, and a second reviewer or an auditor may ask where the number came from months later.

### What the test looks like

Pick any total in the output, such as the March qualifying deposits, and ask the tool to show its parts. A traceable tool lists the transactions with their dates, amounts and the page or line on the statement. An untraceable tool shows a total and a confidence indicator. The first lets you verify in a minute. The second asks you to trust it.

### The arithmetic check

Traceability has a second half: each statement's balances have to reconcile, and a statement that fails should be flagged rather than averaged. How that check catches misread pages is covered in [automated analysis errors on unusual statement layouts](/blog/automated-bank-statement-analysis#automated-analysis-errors-on-unusual-statement-layouts).

### Why it protects the lender

When an investor, a quality-control reviewer or a regulator asks how income was calculated, the answer is the trail. A report that cites statement lines is a document the lender can defend. A report that lists a number with no source puts the burden back on the underwriter to reconstruct it by hand. The post on [what goes in a bank statement analysis report](/blog/bank-statement-analysis-report) covers how citations should read.

### Questions to put to a vendor

- Can I see the source lines for every total, including the averages?
- If I change one deposit's tag, what updates?
- What does the tool do with a page it cannot read?
- Is the original statement kept next to the output, and for how long?

TrueBankFlow's homepage lists the last point as a setting: statements are encrypted in transit and at rest, access is limited to your team, and you choose how long files are kept after a report is exported. Ask every vendor for the same plain answer.

## Statement layout coverage in a bank statement analyzer

Layout coverage describes how many different statement formats an analyzer can read correctly. It matters because borrowers bank everywhere: large national banks, small credit unions and online banks each print statements differently, and a tool that handles only common formats leaves your hardest files for manual work.

### Two ways tools read statements

Some tools rely on templates, one per bank, and fail or degrade when a bank changes its design or when the file comes from a bank outside the list. Others read the layout itself: finding the transaction table, the columns and the balances on the page. TrueBankFlow takes the second approach for US checking and savings statements from banks and credit unions, digital or scanned. A vendor's list of supported banks tells you about templates. It tells you less about what happens to a bank not on it.

### How to test coverage fairly

Do not test with the statements the vendor suggests. Build a set from your own recent files: your five most common banks, two credit unions, one small regional bank and one scanned or photographed statement. Include a statement with a wrapped description and one that spans a year end. Count how many come back with a reconciling balance and correct dates.

### What to record

For each statement in the set, note whether it was read, whether the balance check passed and how many lines needed a fix. A result of "nine of ten clean, one flagged for a missing page" is a good result. A result of ten clean with no flags on a deliberately damaged file is a warning: the tool is hiding problems.

### Scans and phone photos

Borrowers do send photos. Quality varies, and no tool reads every one. The question is whether poor input produces a visible flag or a quiet error. Include one low-quality scan in the trial and watch how the tool reports it.

## What does a bank statement analyzer cost per loan file?

Cost per loan file is the monthly fee plus any per-file overage, divided by the files you actually run. It changes with volume, so a plan that looks cheap at 20 files can look expensive at 60. Calculate it from your own count before you compare headline prices.

### A worked example with TrueBankFlow's early pricing

TrueBankFlow is in early access, and its pricing may change before general release. At the time of writing, its homepage lists three monthly plans: $99 for 25 loan files (then $4 per file), $199 for 75 files (then $3 per file) and $299 for 200 files (then $2 per file). The table below applies those figures to four example monthly volumes.

| Files in a month | Cheapest plan | Monthly cost | Cost per file |
| --- | --- | --- | --- |
| 20 | $99 plan | $99 | $4.95 |
| 40 | $99 plan | $99 + 15 x $4 = $159 | $3.98 |
| 60 | $199 plan | $199 | $3.32 |
| 120 | $299 plan | $299 | $2.49 |

Two things stand out. At 40 files the $99 plan with overage ($159) beats the $199 plan ($199), and at 60 files the $199 plan ($199) beats the $99 plan with overage ($239). The break-even sits between those volumes. And the cost per file falls as volume rises, so unused included files in a quiet month raise your effective rate.

### Costs the plan price leaves out

- **Seats.** The plans list 1, up to 5 and up to 15 seats. A team of four on a single-seat plan pays for a tier it did not plan for.
- **Rework.** A tool that reads badly costs analyst time on every flagged file, and that time belongs in the cost per file.
- **Exports.** Check which report formats each tier includes. The listed plans differ between PDF only and PDF plus Excel.

### Compare against the manual cost

Estimate the minutes an analyst spends on a manual file, multiply by loaded hourly cost and compare to the per-file figure. Your own numbers decide this, not a vendor's. If you do not track minutes per file yet, time five files this week.

## Bank statement analyzer trials that test the wrong files

A trial tests the wrong files when it uses clean, recent statements from a bank the vendor handles well. Such a trial proves the tool works on easy input and tells you nothing about the files that actually cost your team time. A good trial uses your messiest real files.

### The usual mistakes

- **Vendor-picked samples.** Vendor sample files are chosen because they work.
- **One account only.** A single-account file never tests transfer matching.
- **Only recent months.** Statement layouts change over time, and a six-month file may span a redesign.
- **No expected answers.** If you have not computed the answer by hand, you cannot say whether the tool is right.

### How to build a useful trial set

Pick five to ten completed files whose answers you already know. Include a self-employed borrower with two accounts, a file with a one-time large deposit, a file with NSF fees, a scan and a statement from a small bank. Run the files, then compare the qualifying average, the NSF count and the flagged items against your earlier work. Differences are findings. Decide whether each one is a tool error or an earlier mistake of yours.

### Judge the review time, not just the numbers

Time how long a reviewer needs to check the output against the statements. A tool with accurate numbers and no trace can take longer to verify than to compute. A tool with the same accuracy and line links can be checked in minutes. That difference is the real product.

### Know what you are not buying

An analyzer organizes statements. It does not decide credit. [Which steps automation hands to a human](/blog/automated-bank-statement-analysis#where-does-automated-bank-statement-analysis-need-a-human) is worth reading before you set expectations with your team, and the same applies to [mortgage broker bank statement reviews](/blog/mortgage-broker-bank-statements-review), where the broker still reads the file before submission. If a vendor promises to remove the underwriter, treat that as a red flag.

When you are ready to test on your own files, you can [request a spot with TrueBankFlow](/get-started). The software is onboarding lending teams in small groups, and [cash flow analysis software for lenders, compared](/blog/cash-flow-analysis-software-for-lenders) shows the other tool types to weigh against it.