Bank-feed file · the universal format

PDF to OFX converter

Convert PDF bank statements into .OFXfiles that import into almost any accounting or personal-finance app — no CSV, no column mapping. FlowParse AI reads any bank's statement and builds a ready-to-import bank-feed file, with .QBO (QuickBooks) and .QFX (Quicken) on the same download.

Any bank · scanned or digital · balance-validated · unique transaction IDs

FlowParse
app.parseflow.io

One open format, almost every finance app

OFX (Open Financial Exchange) is the open bank-feed standard the whole industry agreed on — the format banks use to send transactions to your software. If your bank only gives you PDF statements, an .OFX file is the most portable way to get that history into your books, because the long list of apps that read it includes GnuCash, MoneyDance, Banktivity, Sage and many more.

FlowParse extracts every transaction from your PDF statement and writes a valid .OFX you import in one step — no columns to map. Need an Intuit-tagged variant? The same engine builds .QBO for QuickBooks and .QFX for Quicken.

In the file

Signed amounts (DEBIT/CREDIT)
Unique transaction ID (FITID)
Account number & currency (CURDEF)
Opening / closing balance
OFX 1.0.2 (Web Connect compatible)
Any bank, scanned or digital

Imports into

GnuCash
MoneyDance
Banktivity
Sage
AceMoney
Many bank portals

Why an .OFX beats a CSV import

A CSV is just raw text: your app has to be told which column is the date, which is the description and which is the amount — every single time. Day-first dates, split debit/credit columns or currency symbols inside the amount all break the mapping and send you back to cleaning a spreadsheet.

An .OFX file is already structured the way finance software expects. Date, signed amount, description and a unique transaction ID are all tagged, so your app just reads it — no mapping, no guesswork — and the transaction IDs give you duplicate protection for free.

 CSV import.OFX file
Column mappingManual, every timeNone — auto
App compatibilityVaries per appUniversal standard
Duplicate protectionNoYes (FITID)
Debits & creditsYou fix the signsPre-signed
Import speedMinutes of fiddlingOne step
FlowParse
app.parseflow.io
FlowParse
app.parseflow.io
The formats

.OFX, .QBO and .QFX — which one?

All three are the same OFX family. Plain .OFX is the generic file most apps read; the .QBO and .QFX variants add an Intuit identifier so QuickBooks and Quicken accept them as Web Connect downloads. Pick .OFX unless your software specifically asks for one of the Intuit variants.

FormatUse it for
.OFXGnuCash, MoneyDance, Banktivity, Sage & most apps
.QBOQuickBooks Online & Desktop (Web Connect)
.QFXQuicken (Web Connect)

Prefer a spreadsheet? The same data also exports to Excel and CSV.

From PDF to bank feed in three steps

1 · Upload the PDF

Drop your PDF bank statement — digital or scanned, any bank, any number of pages.

2 · AI builds the file

FlowParse extracts every transaction, signs the amounts, validates balances and writes a valid .OFX / .QBO / .QFX.

3 · Import anywhere

Open your app's File → Import → OFX and select the file. Transactions post automatically — no mapping.

FlowParse
app.parseflow.io
The import

How to import the .OFX

GnuCash: File → Import → Import OFX/QFX → choose the file → map it to the right account on first import.

MoneyDance / Banktivity: File → Import → select the .OFX → confirm the account.

Sage / Wave: import the .OFX (or the spreadsheet export) under the matching bank account — see bank statement to Sage and bank statement to Wave.

Because each transaction carries a unique ID, re-importing or overlapping statements won't create duplicates.

FlowParse
app.parseflow.io
FlowParse
app.parseflow.io
Any bank, any format

Works with any bank's PDF

Because extraction is AI-based rather than template-based, FlowParse reads layouts it has never seen — so you don't need a converter per bank:

US banks (Chase, BofA, Wells Fargo…)
UK banks (Barclays, HSBC, Lloyds…)
Neobanks (Revolut, Wise, Monzo, N26…)
Digital & scanned PDFs
Multi-page statements
Credit-card statements

Converting a whole year across several accounts? Use Smart Merge to consolidate first.

Trustworthy import

Validated before it reaches your books

A bad import is worse than no import. Before the .OFX is built, FlowParse checks the data so what lands in your software is complete and correct:

Opening + transactions = closing
Continuous running balance
Duplicate detection
Missing-page detection
Unique FITID per transaction
Per-field confidence scores

See the validation engine for how the checks work.

FlowParse
app.parseflow.io

Any bank → one portable bank-feed file

Upload statements from every account you have — FlowParse turns each into a clean .OFX you can import anywhere.

FlowParse
app.parseflow.io
FlowParse
app.parseflow.io
Not only OFX

Need Excel or CSV too?

The same extraction powers every export. If you'd rather work in a spreadsheet or import elsewhere, take the same statement to Excel, CSV, or Xero — no need to re-upload.

.OFX
.QBO
.QFX
Excel
CSV
Xero

Who converts PDF statements to OFX

GnuCash & open-source users

Get PDF history into GnuCash, MoneyDance or Banktivity with a single OFX import.

Accountants

Move client transactions into whatever ledger they run, without re-keying.

Bookkeepers

Catch up months of statements in minutes — upload, download .OFX, import.

Small businesses

Import old or missing statements your bank only offers as PDFs.

Sage & Wave users

Bring bank history into Sage or Wave via OFX or the spreadsheet export.

QuickBooks & Quicken users

Get the Intuit-tagged .QBO or .QFX from the same upload instead.

Frequently asked questions

FlowParse
app.parseflow.io

One file, every finance app

Convert your PDF bank statements straight to .OFX (or .QBO / .QFX) and import them anywhere in one step.