Turn a PDF or scanned bank statement into a clean OFX file that imports into GnuCash, Moneydance, and modern finance software. The tool extracts date, description, and amount and writes a spec-correct OFX file.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
This converter reads the transactions in your PDF statement and writes a clean OFX file that GnuCash, Moneydance and modern finance programs import directly. Upload the statement, let the tool extract each date, description, and amount, then download the OFX. QIF is the older, plain text Quicken format some legacy setups still require; this page explains when you actually need it and where it fits, since this converter produces OFX and CSV rather than QIF.
QIF is older than OFX, some setups still require it, and hand building one from a statement is fiddly and error prone.
Quicken documents QIF import for asset, liability and cash accounts, and states it is not available for checking, savings or credit card accounts, which need a QFX (Web Connect) file instead.
GnuCash and several older or niche finance programs still accept QIF imports, but most of them read OFX directly too, so QIF is rarely the only option.
Banks almost never offer QIF anymore, so if your software specifically needs one you have to build it yourself or find a tool that supports that output.
QIF uses a specific line by line syntax with date, amount, and payee codes. One malformed line and the whole import fails.
QIF date handling varies between programs, so the wrong format quietly imports transactions on the wrong day.
QIF has no transaction IDs, so re importing can double up entries. OFX solves this with a unique FITID on every transaction.
Upload a statement and get a spec-correct OFX file with dates, amounts, and payees coded correctly, ready for GnuCash, Moneydance, MS Money and most accounting software.
Writes valid OFX with date, amount, payee, and memo fields so the import does not fail on a malformed entry.
Reads the PDF your bank issues, including image only and scanned statements, and writes the transactions straight into a clean OFX file.
Formats dates the way OFX importers expect so transactions land on the right day.
Debits and credits are coded correctly so your balance stays accurate after import.
Export the same statement as a plain CSV in one click for a quick review or a spreadsheet.
256-bit encryption in transit and you can delete your uploaded statement at any time.
No install, no bank download, no credit card to start.
Drop in the PDF or scanned statement from your bank or card.
Tip: Multi page and multi month statements are fine.
The tool extracts every transaction and writes a valid OFX file automatically.
Tip: Need QIF for a legacy program? See the QIF file format guide below for what the format requires.
Download the OFX and import it into GnuCash, Moneydance, or your accounting software, then pick the account.
Tip: Import to a test account first if you are unsure how the program handles the import.
Most people converting a bank statement today want OFX. A smaller group is stuck on software that only takes the older QIF format.
Import into the Quicken asset, liability or cash accounts where QIF is the documented route and QFX is not offered.
GnuCash reads OFX directly, so this converter's OFX output works there without needing QIF at all.
Convert statements to OFX for most clients; only fall back to hand-built QIF for legacy software that cannot take OFX.
Convert statements to OFX for most ledgers, and use the QIF format guide below when a program strictly requires the legacy format.
OFX has largely replaced QIF, but QIF still matters for specific programs. Quicken keeps QIF import for asset, liability and cash accounts while refusing it for checking, savings and credit card accounts, and GnuCash and Moneydance can accept QIF as a fallback import path, though both also read OFX directly. If your software reads OFX, prefer it, since it carries transaction IDs that prevent duplicates. Use QIF only when a program specifically requires it or when it is the only import your tool offers. If you are on modern Quicken, export CSV instead and follow the Quicken import guide.
QIF is a plain text format with a strict line by line syntax, and a single malformed line can make the whole import fail. Each transaction is a block of coded lines: a date line, an amount line, a payee line, and an optional memo line. The table below explains what each code represents.
| QIF field | What it represents |
|---|---|
| D (date) | The transaction date |
| T (amount) | A signed amount, debits negative |
| P (payee) | The transaction description or payee |
| M (memo) | Any extra detail from the statement line |
This converter does not generate QIF. If your software accepts OFX, the same statement exports to OFX for MS Money and open tools here, or follow the Quicken import guide. OFX is worth using when available because it protects against duplicate imports the way QIF cannot.
Upload the PDF or scanned statement to the converter above and download the OFX. The tool extracts every transaction and writes a spec-correct OFX file, formatting the dates so it imports cleanly into GnuCash, Moneydance, or accounting software.
QIF stands for Quicken Interchange Format, an older plain text format Quicken used before OFX and QFX. It stores each transaction as coded lines for date, amount, payee, and memo. Many legacy programs still import QIF even though banks rarely offer it as a download anymore.
Use OFX when your software accepts it, because it carries transaction IDs that prevent duplicate imports. Use QIF only when a program specifically requires it, such as an older Quicken account type or a legacy GnuCash setup; in that case you will need a QIF built by hand or by a tool that supports it, since this converter produces OFX and CSV.
No. Quicken states that QIF import is not available for checking, savings or credit card accounts, a restriction that dates back to the 2006 version. QIF still imports into asset, liability and cash accounts. For a bank or credit card account, export the statement as CSV instead, since Quicken cannot import OFX either, and use File, then File Import, then Banking Transactions, then From (.CSV) File.
QIF has no built in transaction IDs, so re importing an overlapping period can double up entries. Import each period once, and if you need duplicate protection, use OFX instead, since it includes the unique IDs finance software uses to skip duplicates.
Your upload is protected by 256-bit encryption in transit and you can delete the file at any time. Before sending any financial document to an online tool, confirm it encrypts uploads and lets you control deletion, and review its privacy and retention policy.
Odoo Accounting reads OFX and QIF natively. The import steps.
The QIF format, its field codes, and an annotated example.
Produce the OFX file MS Money, GnuCash and Moneydance accept.
Export the open OFX format instead.
Get any statement into Quicken.
Turn a CSV export into an account file.
Convert a PayPal statement PDF to OFX or CSV.
Get started converting bank statements to OFX.
USD
per month
per month
$294 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion with bulk upload, custom templates and reports.
USD
per month
per month
$894 charged today
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
per month
$ charged today
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
