Most "PDF to OFX" tools are websites. This guide does it on your phone with Filemorph (Pro, iOS 26+), then walks through the import in GnuCash, YNAB and Xero, and what to do when a statement doesn't parse cleanly.
Most banks will hand you a statement as a PDF and stop there. Your accounting software wants OFX — a format built for transactions, not a picture of a table. Filemorph reads that PDF with Apple's on-device Vision framework, finds the transaction table, and writes an OFX file you can hand to GnuCash, YNAB or Xero. No upload, no server in the middle — the document with your account number and every transaction on it stays on your iPhone the whole time.
This is a longer job than most conversions on this site, because there's a review step in the middle and three different apps to import into. Here's the whole path, plus the fixes for the handful of things that trip people up.
There are three common starting points, depending on where the statement is coming from. If your bank's website offers a PDF download, save it into Files from Safari, or open Filemorph directly and pick it straight from the Files picker. If the statement arrived as a Mail attachment, open the attachment, tap Share, and choose Filemorph from the share sheet. And if all you have is a paper statement, Filemorph's Scan to PDF turns a photo of it into a PDF first — keep the page flat and well-lit, since the next step reads the table optically.
With the PDF open in Filemorph, choose the To OFX operation. If the PDF is password-protected, Filemorph asks for the password before it reads the file — it's decrypted on-device and never sent anywhere to be unlocked.
Before anything is written, Filemorph shows a review sheet: which columns it detected as date, description and amount, whether the account is checking, savings or credit card, the currency, the date order (day-first or month-first), and the sign convention for charges versus payments. For a statement with a messier or less standard layout, an optional on-device Apple Intelligence assist can propose a column mapping for you to confirm rather than build one from scratch. Fix anything that's wrong, then move on. If you've confirmed this bank's layout before, the sheet skips straight to a "verified" card — the layout is remembered on the device, encrypted, so a repeat statement from the same bank is a one-tap job.
Tap Export and choose Save to Files or AirDrop. The result also opens inside Filemorph as a small statement view — dates, descriptions, amounts — so you can eyeball the totals before you trust it to an import.
File → Import → Import OFX/QFX…, then point it at the .ofx file. On the first import for an account, GnuCash asks which account to post the transactions into; after that it remembers. GnuCash matches duplicates by the transaction's FITID, which is why running the same import twice doesn't double your transactions.
In the YNAB web app, open the account and choose Import, then pick the .ofx file — YNAB accepts OFX alongside its native QFX and CSV imports. Payee names come through as written on the statement, so it's worth renaming a few the first time so future imports auto-categorize the same way.
Accounting → Bank accounts → Manage account → Import a statement, then select OFX as the file type and upload it. Xero matches dates and amounts against any existing bank feed transactions for the same period, so importing on top of a live feed doesn't create duplicates either.
Across all three, Filemorph's OFX carries the same fields — a posting date, a payee taken from the statement's description column, a signed amount and a stable transaction ID — so what changes between GnuCash, YNAB and Xero is where the import button lives, not what actually gets imported.
A few things come up often enough to call out ahead of time:
A bank statement is one of the most identifying documents you own: account number, balance, full transaction history. An online "PDF to OFX" converter asks you to upload that file to a server you don't control, in exchange for a format conversion Apple's own frameworks can already do on your phone. Even a routine checking-account statement carries your name, address and a month of spending in one file — none of that needs to touch a server just to change its file extension. Filemorph never makes that trade — turn on Airplane Mode and the conversion still runs, because there's no server to reach. Read exactly what Filemorph can and can't send over a network on the transparency page, or see the OFX format explainer for what the file actually contains. For a fuller look at how web-upload, desktop and on-device converters differ on privacy, price and formats, see PDF to OFX converters compared.
Converting a PDF to plain text is free in Filemorph. Turning a bank statement PDF into OFX is part of Filemorph Pro, which includes a 7-day trial on monthly and annual plans.
No. Filemorph writes plain OFX 1.02; QFX is a licensed variant it does not produce. Check your finance software's import menu for an OFX option — many list both.
No. Each transaction carries a deterministic ID, so importers that track it (GnuCash and YNAB) skip rows they have already seen; Xero matches on date and amount instead.
Filemorph can remind you to convert your statement on the 1st of the month, if you opt in after an export. Because the layout is remembered, the next export for the same bank is a one-tap job — not full automation, but close.
Filemorph Pro converts PDF statements to OFX on-device. 7-day trial included. Plus 300+ more file operations.
Download on theApp Store