Use cases: Start from the job, not the file.
The same bank statement is read for different reasons: to reconcile a ledger, to prepare a return, to see how long the money lasts, or to bring years of history into new software. Each page here starts from one of those jobs and shows which parts of Bankflow do the work.
- 5Jobs
- 12Export formats
- 0Bank connections needed
- 50Free pages
What changes between jobs is what has to be true at the end.
Reconciliation needs every row to walk from the opening balance to the closing one. Tax preparation needs every line in a category the return recognises, with the doubtful ones marked. A forecast needs history clean of transfers and one-offs. A payables run needs line items and accounts, not a total. A backfill needs years of statements, each one proven complete. The parser underneath is the same for all of them; the checks, the edits, and the export that matter are not.
By job
Which job are you doing?
Each page walks the job from the first file to the finished output.
Bank Reconciliation
Month-endBalances checked against the statement before anything posts.
OpenTax Preparation
Year-endA year of statements, tagged and totalled for the return.
OpenCash Flow Forecasting
Forward viewRunway, monthly P&L, and what-if scenarios from real history.
OpenAccounts Payable
BillsInvoices and receipts read into QuickBooks and Xero bills.
OpenHistorical Data Import
BackfillBackfill the years your bank feed never reached.
Open
Looking for your role instead?
Bookkeepers, accountants, firms, small businesses, freelancers, lenders, and developers each have a page written for the way they work.
What each job depends on
The one check or output that decides whether the job is done.
| Job | What has to be true | What does it |
|---|---|---|
| Bank reconciliation | Every statement ties to its printed balances. | Running-balance validation and the opening and closing tie-out on every parse. |
| Tax preparation | Every line sits in a category the return uses. | Categories, tags, rules, and a date-range export for the tax year. |
| Cash flow forecasting | History reflects real income and spending. | Exclusions, recurring detection, runway views, and scenarios. |
| Accounts payable | Each invoice's lines and tax agree. | Arithmetic checks and QuickBooks or Xero bill-import files. |
| Historical data import | Years of statements, none of them short. | Per-statement reconciliation, duplicate detection, and OFX or QBO export. |
FAQ
Common questions
Do I need a different plan for different jobs?
No. Every plan includes every feature; plans differ only in how many page credits they include each month.
Can one account cover several of these jobs?
Yes. The statements you reconcile are the same ones a forecast reads and a tax export draws from. Folders keep accounts, entities, or clients apart.
Does any of this need a connection to my bank?
No. Everything starts from statements the bank has already issued, which is why closed accounts and years-old history work the same way as last month.
What does it cost to try one?
New accounts get 50 free page credits with no card, enough to run a real month of any of these jobs from first file to export.
The rest of the site
Convert
Every format a statement can become, and the bank pages behind each one.
Integrations
Which accounting tools need a converted file, and which format each one takes.
Solutions
The same statements, read for the role you actually have.
Features
The product in full, and a page for each part worth its own.
File formats
What a QIF, QFX, OFX, QBO, or IIF file actually is, what opens one, and what to do when a program refuses it.
Free tools
Bookkeeping and statement tools that run in your browser: month-end, PDFs, import files, and the numbers.
Comparisons
Five head-to-heads, each checked against the other product's own pages.
Pick the job that is waiting.
Upload the statements it needs, and see how much of it is done before you open a spreadsheet.