Skip to main content
BankFlow logoBankFlow

For bookkeepers

Month-end without the data entry.

Set a client up once, with a forwarding address and the rules their vendors need, and every month after that arrives, parses, and codes itself, leaving you the exceptions and the export.

50 free page credits · No card · Cancel anytime

  • Forward-to-import inbox
  • Rules per client
  • OFX/QBO & Excel export

Email imports

Settings
Your import addressForward any bank statement email here to import it automatically.
books-3f9c1a20@mail.bankflow.appCopy
Approved sendersMail from anyone else is discarded without being stored.
books@acme-bookkeeping.comAccountstatements@bank.com or @bank.com
Auto-importForwarded statements wait for review by default. Turn it on per sender to skip that.

Twelve months that are all the same month.

Bookkeeping repeats by design: the same clients, the same banks, the same forty vendors that always want the same category. Done by hand, that sameness is the whole cost. You retype January in February and again in March, and the hours land on transcription instead of the review and the questions clients are actually paying for. The way out is not typing faster. It is setting the repeating part up once, in January, so that by March nobody needs to be there when the statement arrives.

How it works

One client's year, from set-up to close

  1. 01

    January: give the client an address

    Each account gets its own forwarding address. The client sends statements to it, or sets a permanent auto-forward at the bank, and the chasing stops there. No mailbox access, no login for them to forget.

  2. 02

    February: the statement lets itself in

    A trusted sender's attachment imports without anyone opening the email. It is read, its transactions extracted, its bank detected, and its opening and closing balances reconciled against the rows before it counts towards anything.

    Activity panel showing a Chase statement processing, with the current stage and elapsed time.
    The queue names the stage it is on and the seconds elapsed, whichever way the file arrived.
  3. 03

    March: the rules have already coded it

    The rules you wrote in January run on arrival. Every category carries its own, so a vendor that matches lands coded without anyone opening the statement, and the month arrives mostly classified. What is left is the genuinely new: a vendor nobody has seen before.

    The Categories and Tags list, each category showing how many rules sit behind it.
    Each category carries the rules behind it, and what those rules have already classified.
  4. 04

    Any month: work the exceptions, not the ledger

    Open what was flagged, fix it in place or across a shift-clicked range, then turn the correction into a rule so it never comes back: include patterns, exclusions, an optional merchant, and which sources it may touch. Manual edits stay protected from every later automated run.

    The rule editor: include and exclude patterns, merchant scope, transaction type, and source scope.
    A correction becomes a rule: what to match, what to exclude, and how far it is allowed to reach.
  5. 05

    Close: export and move on

    Take a QuickBooks-ready OFX or QBO file, or an Excel sheet scoped to one account and one month, whatever this particular client's filing actually needs.

    Export dialog with QuickBooks selected, the field list on the right, and a live preview of the rows.
    QuickBooks selected. The preview is the same data you just reviewed, in the order the file will carry it.

The parts that stop the month repeating

An address per client

A private forwarding address for each account. Allow specific senders, opt into auto-import per sender, and give up no access to your own inbox to do it.

Rules that reach backwards

Inclusion phrases, exclusion keywords, a merchant, a category, and tags, then applied across every statement you have already imported, not just the next one.

Subscriptions found for you

Recurring charges are detected as recurring. That codes them faster, and it gives you something worth raising with the client.

Bulk editing that keeps up

Shift-click a range and recategorize, tag, flag, exclude, or turn the selection straight into a rule, from a toolbar that stays on screen.

A balance check at intake

Opening and closing balances are reconciled on every parse, so a client's missing page surfaces the morning it arrives rather than the afternoon you reconcile.

Exports scoped to the job

Filter to one account, one month, or one category and export exactly those rows: CSV, Excel, or a QuickBooks-ready OFX/QBO file.

FAQ

Common questions

Can I keep separate rules for different clients?

Rules live alongside the transactions they apply to, so each account's categorization logic stays its own. Rules can also be scoped to a specific merchant, which keeps a broad text match from spilling into unrelated vendors.

Do my clients need accounts?

No. They only need to forward statement emails to the import address you give them, or send you the files however they already do.

Does email import mean giving up access to my inbox?

No. You get a dedicated forwarding address and mail is sent to it. BankFlow never connects to or reads your mailbox.

What if the automated categorization gets something wrong?

Correct it in the ledger, individually or in bulk. Manual corrections are protected from later automated changes, and you can turn a correction into a rule so it never comes back.

Will this fit around QuickBooks?

It sits in front of it. You do the categorization work in BankFlow's ledger, where bulk editing is fast, then export an OFX/QBO file that QuickBooks Online or Desktop imports directly.

How do I try it on real client work?

New accounts get 50 free page credits with no card, which is enough to run a client's month end to end before committing.

Set January up once.

Give one client a forwarding address, write the rules their vendors need, and see what February costs you.