Upload any US bank or credit card statement as a PDF, scan or phone photo and download a spec correct OFX file. The extraction reads date, description, amount and running balance from every transaction, so the import reconciles instead of needing cleanup.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
A PDF to OFX converter reads the transaction table inside a PDF or scanned bank statement and writes an OFX file that finance software imports directly. Upload the statement, let the extraction pull the posting date, description, amount and running balance from every line, then download the OFX. Because OFX is the open Open Financial Exchange standard rather than a vendor format, the same file imports into Quicken, MS Money, Xero, GnuCash, Moneydance and most accounting tools. A PDF cannot be imported on its own, so this conversion step is what turns a document you can only read into transactions you can categorize and reconcile.
The transactions are visible in the statement, but a PDF describes where ink sits on a page, not what a transaction is. Finance software needs structured fields, and that gap is where the manual typing usually starts.
Quicken, Xero and MS Money expect dated, signed amounts in defined fields. A PDF has none of that, so there is nothing for the importer to read even though you can see every line.
Most US banks only offer an OFX or Web Connect download for recent activity, sometimes 90 days. Anything older is available as a PDF and nothing else.
Selecting a PDF table and pasting it usually jumbles descriptions into amounts and drops the running balance, which is worse than starting over.
A scanned or photographed statement is an image. There is no text layer to copy, so without OCR the only route is retyping every row.
Writing OFX by hand is easy to get subtly wrong. A missing LEDGERBAL block or a duplicate FITID is a common reason an import fails with an unhelpful error.
A manual process tuned to one bank layout breaks the moment you handle a second bank, a credit card, or a statement that spans several months.
One upload produces a valid OFX file with the fields the specification requires, so it loads without warnings.
Writes the signon, account and transaction blocks with a unique FITID per line and a closing LEDGERBAL, the parts hand built files most often miss.
Templates tuned to US checking, savings and credit card layouts, with AI extraction handling formats it has not seen before.
OCR reads image based statements in PDF, JPG, PNG, BMP, HEIC and TIFF, so paper copies convert as easily as digital downloads.
Date, description, signed amount and running balance carry through, so the imported register balances against the statement total.
Need Quicken Web Connect instead, or a spreadsheet to review first? Export the same statement in another format in one click.
256-bit encryption in transit and you can delete an uploaded statement at any time.
No bank feed, no Direct Connect setup, no credit card to start.
Drop in a PDF, scan or photo of a bank or credit card statement. Multi page and multi month files are fine.
Tip: Password protected PDFs are supported.
Every transaction is extracted and written into a valid OFX file with the required identifiers and balance block.
Tip: Most statements finish in under a minute.
Download the OFX and import it through your program's file import menu, then pick the matching account.
Tip: Reconcile against the statement ending balance to confirm nothing dropped.
Anyone whose software reads OFX but whose bank only hands over a PDF, which after a short download window is nearly everyone.
Load a client's back catalog of statements without retyping a single transaction.
Rebuild a clean, reconcilable transaction history from PDFs for tax prep and cleanup work.
Get bank and card activity into Xero, Quicken or your ledger from the statements you already have.
Backfill months or years of history that the bank no longer offers as a download.
OFX is an open standard, so it is the most portable choice when you are not sure what the destination will be. A few programs want a vendor specific variant instead, and picking the wrong one is the single most common reason an import fails. The table below covers the destinations people ask about most.
| Destination | Accepts plain OFX? | What to export |
|---|---|---|
| Xero | Yes | OFX. Xero accepts OFX, QFX, QIF, CSV and QuickBooks files for manual import, and recommends OFX where possible |
| Microsoft Money | Yes | OFX, the format it was designed around |
| GnuCash | Yes | OFX, through the OFX/QFX import menu |
| Moneydance | Yes | OFX |
| Quicken | Version dependent | QFX (Web Connect) imports most reliably for bank and card accounts |
| QuickBooks Desktop | No | QBO, its own Web Connect variant |
If Quicken is the destination, export the Quicken flavor instead using the PDF to QFX converter. If you want the differences between the three variants in one place, read OFX vs QFX vs QBO.
Convert the PDF statement to OFX here, then in Xero go to the bank account, choose to import a statement and upload the file. Xero accepts OFX, QFX, QIF, CSV and QuickBooks files for manual import and recommends OFX where it is available, because an OFX carries typed dates and signed amounts rather than columns Xero has to be told how to read. A CSV import needs at least a date and an amount column and is capped at 100,000 rows, and it leaves you mapping fields by hand every time. The Xero bank statement converter covers the Xero side of the workflow in more detail, and there is a step by step walkthrough of how to import bank statements into Xero.
No. Adobe Acrobat exports a PDF to Word, Excel, PowerPoint, plain text and image formats, but OFX is not one of its export targets. Acrobat has no concept of a financial transaction, so even its Excel export gives you a grid of cells that still needs the dates, amounts and running balance identified and rebuilt before any finance program will read it. That is the work a statement converter does: it recognizes the transaction table, types each field, and writes the OFX structure the specification requires.
Both convert, but they take different routes, and knowing which one you have explains a lot about the result you get.
| Statement type | How it is read | What affects accuracy |
|---|---|---|
| Digital PDF downloaded from online banking | The embedded text layer is parsed directly | Mostly layout: multi column and wrapped descriptions |
| Scanned paper statement | OCR reconstructs the text, then the table is extracted | Scan resolution, skew and contrast |
| Phone photo of a statement | OCR, after the page is straightened | Lighting, shadows, focus and cropping |
For image based statements, a flat, evenly lit, straight on capture makes the difference between a clean conversion and one that needs review. There is more on that in the guide to converting a scanned bank statement to OFX.
The generated file is plain text you can open in any editor. Each transaction becomes an STMTTRN block carrying a type, a posting date in YYYYMMDD form, a signed amount with no currency symbol or thousands separator, a unique FITID and a description. After the transaction list sits a LEDGERBAL block with the closing balance and its date, which is the piece hand built files most often leave out and a frequent cause of a rejected import.
If you want the field by field detail, including the difference between the SGML based OFX 1.x and the XML based OFX 2.x and a fully annotated sample file, the OFX file format reference documents the specification. For a shorter introduction, see what is an OFX file, and if you would rather inspect the transactions in a spreadsheet before importing, here is how to open an OFX file in Excel.
Yes. A converter reads the transaction table inside the PDF and writes the data into the OFX structure that finance software expects. Upload the statement, and the posting date, description, signed amount and running balance from each line are extracted and exported as an OFX file you can import directly.
Upload the PDF or scanned statement to the converter above, let the extraction pull every transaction, then download the OFX file. Import it through your program's file import menu and select the matching account. Most statements finish in under a minute, including multi page and multi month files.
No. Adobe Acrobat exports to Word, Excel, PowerPoint, text and image formats, but not to OFX. Acrobat does not recognize transactions, so even its Excel export leaves you a grid of cells that still needs dates, amounts and balances identified before any finance program will accept the data.
Convert the statement to OFX here, then in Xero open the bank account and import the statement file. Xero accepts OFX, QFX, QIF, CSV and QuickBooks files for manual import and recommends OFX where possible, because it carries typed dates and signed amounts instead of columns you have to map by hand.
OFX is the open Open Financial Exchange standard that many programs read. QFX is Quicken's branded version of OFX with an added Intuit bank identifier. Use OFX for Xero, MS Money, GnuCash and Moneydance, and QFX when Quicken is the destination. Renaming one to the other does not work.
Yes. Scanned statements and phone photos are read with OCR before the transaction table is extracted, and PDF, JPG, PNG, BMP, HEIC and TIFF files are all accepted. A straight, evenly lit, reasonably high resolution capture reads most accurately.
The usual causes are a missing closing balance block, transaction IDs that repeat, a date written in a format other than YYYYMMDD, or an amount carrying a currency symbol. A converter that writes the file to specification avoids all four, which is why hand edited OFX files fail far more often.
With this converter your upload is protected by 256-bit encryption in transit and you can delete your data at any time. Before sending financial documents to any online tool, confirm that it encrypts uploads, lets you control deletion, and publishes a clear retention policy.
The broader guide to getting any statement into OFX.
Field by field reference for the OFX specification.
Export Quicken Web Connect QFX instead.
Convert scanned and photographed statements.
Convert credit card PDFs to import-ready files.
Get started converting bank statements to OFX.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
billed as
$888 yearly
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
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
