How it works
- 1
Upload the client's PDF
Digital or scanned, one statement or a batch within your plan's limits.
- 2
Clear the review flags
Check the reconciliation, resolve flagged rows and correct anything the statement made ambiguous.
- 3
Export and code
Download CSV for your accounting tool or Excel for a coding sheet. The column layout stays the same next month.
When you need the PDF workflow
Bank feeds are excellent when they exist and the client has connected them. They do not cover every situation: a closed account, a legacy statement, a client who will not share bank access, or a period that predates the current software.
The PDF workflow is also useful for one-off checks: a loan application, a landlord's rental accounts, or a set of statements that needs to be reviewed before anything is posted.
From statement to coded ledger
FlowParse does not categorise transactions or suggest nominal codes. It extracts the transaction fields and leaves the judgement to you. That is intentional: coding rules depend on the client, the chart of accounts and the accounting policy.
What you get is a ledger with consistent descriptions, real dates, positive debit and credit amounts, and a running balance when the statement provides one. That is the input a coding workflow needs.
A clean import file
- CSV with a stable header row, so an import mapping can be reused.
- UTF-8 text for merchant names and currency symbols.
- Descriptions quoted when they contain commas or quotes.
- Formula-like text neutralised against spreadsheet injection.
- Separate debit and credit columns instead of ambiguous signed values.
Recurring monthly work
The page allowance resets on the first day of each calendar month. A typical bookkeeping client with a two-page statement uses two pages per month; a larger client with several accounts uses more.
Keep one FlowParse document per statement. The history view lets you reopen a month, re-export it, or check what was flagged at the time.
Quality checks that save time later
- Reconcile the statement before coding. A mismatch is easier to investigate at conversion time than after posting.
- Review flagged rows first; they are the most likely source of a later difference.
- Check the opening balance against last month's closing balance.
- Keep the original PDF attached to the client file.
Bookkeeping work that fits
Monthly bookkeeping
Convert the same client's statement every month with a stable export layout.
Catch-up work
Process several months of statements before a deadline.
Sole traders
Turn personal and business statements into a transaction list for self-assessment preparation.
Landlords and rental accounts
Extract property income and expenses from statements without bank access.
Questions
Does FlowParse categorise transactions?
No. It extracts and validates the statement data. Coding and nominal selection stay with the bookkeeper or accountant.
Can I reuse an import mapping each month?
Yes, if your accounting tool saves mappings. FlowParse keeps the CSV header row stable so the mapping still applies.
What if a client sends a photo of a statement?
Ask for a PDF. If they only have a photo, convert it to a PDF and expect OCR-quality output; review the confidence flags carefully.
Can I process several clients in one day?
Yes, within the plan's monthly page allowance. Each statement is a separate document, so client data does not mix within a conversion.
Does the Free plan work for real bookkeeping?
It is useful for a trial on one short statement: 3 processed pages per month, one file per batch and a 25 MB limit. Recurring client work generally needs Starter or above.