The system that collects every client bank statement without you having to ask
What StatementFlow does: it connects each client's bank once through Plaid or Mastercard Open Banking, learns every account's statement-posting cycle, downloads the official PDF statements automatically, verifies each file with a SHA-256 hash, files it in your firm's own Google Drive by client and month, and alerts your team to any gap before it holds up close.
Five steps from bank connection to filed PDF
-
Connect: one secure link per client
You send a branded invite link. The client authenticates directly with their bank on their own device, so credentials never pass through StatementFlow. Staff-driven connect exists for firm-owned accounts, gated behind passkey step-up.
-
Learn: every account's real statement cycle
A statement that posts on the 3rd shouldn't be chased on the 1st. The system observes when each account's statement actually becomes available and schedules retrieval around it. That ends the calendar-month guessing and the premature "it's missing" noise.
-
Fetch: official PDFs, from the source
When the bank publishes, the statement is requested, confirmed by signature-verified webhook, and downloaded. Transient failures get automatic retries with backoff, and a second bank-data provider covers institutions the first can't reach.
-
Verify & file: hash-checked, filed by client and month
Every PDF is SHA-256 hash-verified on download, then routed to your firm's Google Drive under a consistent client/year/month structure. Each retrieval keeps a per-job event timeline you can audit later.
-
Watch: coverage, health, and alerts
The coverage board shows account × month status across the whole book. Broken connections, failed fetches, and statement gaps raise alerts to the right person, with guided fixes for banks' security step-ups.
Your whole book's statement status, one glance
Which client is missing which month? Which connection needs re-auth before the 31st? The board answers in seconds what used to take a spreadsheet, three inboxes, and a bad memory.
Filed like your best admin on their best day
Statements land in your firm's Google Drive, named and nested consistently, ready for reviewers, auditors, and lenders. We keep no silo of our own. Leave anytime; your archive stays yours.
Naming conventions and routing rules are configurable per client.
Clients spend two minutes on this, once
One clean invite link
The link arrives with plain-language guidance: use your own device, your usual network, have your phone handy. No portal accounts, no uploads, no PDFs to hunt down.
Their bank's own login
Authentication happens in the bank's flow via Plaid Link or Mastercard Open Banking. StatementFlow never sees usernames or passwords. It receives a scoped, encrypted access token instead.
Guided recovery when banks get picky
Some banks add extra verification holds. When that happens, the client (and your team) see exact, bank-specific steps to clear it. A support mystery becomes a two-minute phone call.
Who can do what, and an audit trail to prove it
- Roles that match a practice: admins govern the workspace, managers own client connections, staff view/download/tag/export. Connection changes are gated to the right people.
- Passkey (WebAuthn) step-up on sensitive actions, so a stolen password alone can't touch bank connections.
- Activity log & per-job timelines: who connected what, when each statement was requested, fetched, verified, and filed.
- Exports for handing evidence to reviewers, auditors, or lenders without granting system access.
Processor and marketplace statements run through the same pipeline
For clients who sell online, settlement and payout statements from payment processors and marketplaces flow through the same verify-file-alert pipeline, so "all the statements" finally means all of them.
Rolling out to early-access firms; availability by platform may vary during the pilot.
What StatementFlow is not
Our job is retrieval, done completely. Here is where it stops.
- It doesn't do OCR or data extraction. Dext, AutoEntry, and DocuClipper parse documents you already have. We fetch and organize the official documents in the first place, which is why they pair well with us.
- It won't touch your books. No journal entries, no feeds to babysit. Your ledger stays your ledger.
- It isn't a client upload portal. Portals move the chase to a nicer inbox; StatementFlow removes the ask entirely. See the comparison.
- US only, for now. Bank coverage is US institutions, depository accounts (checking/savings), via Plaid Statements and Mastercard Open Banking.
Product questions
Do my clients need to install anything or create accounts?
What happens when a bank connection breaks?
Which ledger does it work with?
Can it backfill history when we onboard a client?
See it on your own client book
Early-access firms onboard with hands-on setup: connect a few pilot clients, watch the statements arrive, then roll out the rest.