How it works
- 1
Convert the statement
Upload the PDF and review the extracted rows. Correct anything flagged before exporting.
- 2
Map the CSV columns
Use your accounting tool's import wizard to map date, description, debit, credit and balance. Save the mapping if the tool supports it.
- 3
Import and reconcile
Import the file, then reconcile the imported total against the statement's closing balance before posting.
What an accounting import actually needs
| Requirement | Export behaviour |
|---|---|
| A predictable header row | Same column names across statements |
| Unambiguous dates | ISO 8601 (YYYY-MM-DD) |
| Numeric amounts | Plain decimals with a dot, no currency symbols |
| Transaction direction | Separate debit and credit columns |
| Safe text | Commas and quotes escaped; formulas neutralised |
| A reference for reconciliation | Running balance included when the statement has one |
Map once, reuse the mapping
Most accounting tools let you save an import profile or mapping. Because FlowParse does not rename columns between statements, the same profile keeps working. The review step happens before the export, so the file you import is the file you checked.
Dates, decimals and signs
A statement printed in the UK might show 03/04/2026 meaning 3 April. An accounting tool set to US conventions may read it as 4 March. FlowParse normalises dates to ISO format to remove that ambiguity.
Amounts are exported as positive values in separate debit and credit columns. If your tool expects one signed amount column, combine them in a spreadsheet formula before import rather than guessing the tool's sign convention.
Avoiding duplicate imports
- Import each statement once and keep the original PDF with the workpaper.
- Reconcile the imported closing balance before posting.
- If an import fails partway, check what the tool actually accepted before retrying the whole file.
- Keep the statement period in the file name so an overlap between statements is obvious.
Tools that accept CSV
FlowParse is not affiliated with any accounting vendor. Its CSV export is intended for software that provides a CSV import wizard, including cloud accounting platforms, desktop bookkeeping packages and spreadsheet-based ledgers.
If your tool requires OFX, QIF or a proprietary format, FlowParse is not the right converter. If it accepts CSV, the import is a mapping exercise rather than a conversion problem.
Where the CSV fits
Cloud accounting imports
Import historical statement transactions into a cloud ledger.
Desktop bookkeeping
Feed a desktop package that accepts CSV transaction files.
Spreadsheet ledgers
Append a normalised month to an Excel-based bookkeeping file.
Data migration
Move historical transactions into a new system during a software change.
Questions
Does FlowParse integrate directly with Xero or QuickBooks?
No. There is no native integration and no FlowParse app in those marketplaces. FlowParse exports CSV, which those tools can import through their own import wizards.
Which CSV format does it use?
UTF-8, comma-delimited, with a header row and one transaction per line. Fields containing commas, quotes or line breaks are quoted and escaped.
Can I get a single signed amount instead of debit and credit?
The export separates debit and credit to avoid sign conventions. If your importer needs one column, combine them in a spreadsheet formula before importing.
Will the import duplicate transactions already in the ledger?
Your accounting tool decides that. Import only statements that are not already in the ledger, and reconcile the closing balance after each import.
Can I import a scanned statement?
Yes, after review. Scanned statements use OCR and are flagged, so clear the review notes before exporting to your accounting software.