StatementCSV
Convert a bank statement PDF to OFX
Some apps would rather take an OFX file than a CSV, and your bank may only give you a PDF for older months. StatementCSV reads a text-based statement PDF in your browser, lets you fix the rows, and writes an OFX 1.02 file from the table.
Steps
- Open the statement PDF in the StatementCSV app. It's read in your browser, not uploaded. The free preview shows how many transactions it finds and the first 5 rows, so you can see whether your PDF works before you pay.
- Unlock for $9.99 one-time. Download OFX and the export options are part of the paid export; the free preview doesn't include them.
- Check the rows and fix anything that looks off. You can edit or delete rows, and the OFX file is built from the table as you leave it. Type or check the opening and closing balances to see whether the rows add up to the statement.
- Under Export options, check three settings. Statement year is prefilled from the latest year printed in the PDF. Account is Bank account or Credit card. Flip signs is for statements that print charges as positive numbers. When the app spots a credit card statement (American Express, or text like "minimum payment due" or "credit limit"), it picks Credit card and ticks flip signs for you.
- Select Download OFX. The file has the PDF's name with
.ofx on the end. The app tells you how many rows it exported and how many it left out.
- Import the file into your app (see below), then compare the imported total with the PDF before you reconcile.
What's in the file
Here's part of a file the converter writes for a checking statement that closes in 2026, with two rows (a Dec 30 coffee and a Jan 2 deposit) and a closing balance of 2,045.50:
OFXHEADER:100
DATA:OFXSGML
VERSION:102
...
<STMTTRN>
<TRNTYPE>DEBIT
<DTPOSTED>20251230120000
<TRNAMT>-4.50
<FITID>SCSV1911ea7a
<NAME>Coffee Shop
<MEMO>Coffee Shop
</STMTTRN>
<STMTTRN>
<TRNTYPE>CREDIT
<DTPOSTED>20260102120000
<TRNAMT>1250.00
<FITID>SCSVe31e51e8
<NAME>Payroll deposit
<MEMO>Payroll deposit
</STMTTRN>
...
<LEDGERBAL>
<BALAMT>2045.50
<DTASOF>20260102
</LEDGERBAL>
- It's OFX version 1.02 (the older SGML style), US-ASCII encoding, with Windows line endings.
- Bank account files use a checking-account block. Credit card files use a credit card account block.
- Each row becomes one transaction. Negative amounts are
DEBIT and positive amounts are CREDIT. Amounts have no $ sign or thousands commas.
- The posting date includes the year. Statements often print dates without one, so the converter uses the statement year. When a statement without years has both December and January rows, the December rows get the year before. Every transaction is stamped at 12:00.
NAME is the first 32 characters of the description and MEMO holds the full description.
FITID, the transaction ID that importers use, is built from the row's position, date, amount and description. If you export the same table again, you get the same IDs. If you edit or reorder rows first, they change.
- The ledger balance is the closing balance from the balance check (read from the PDF when it can find it, and you can edit it). If that box is empty, the balance is 0.00.
- If a row's date or amount can't be read, the row is left out of the file.
Importing it
- QuickBooks Online: Intuit lists .ofx among the files you can upload under Bank transactions, then Link account, then Upload from file. The limits are 350 KB and 1,000 lines per upload (Intuit's steps). If you'd rather upload a CSV, see the QuickBooks import guide.
- Xero: Xero says you can import statements in OFX, QIF, QBO, QFX or CSV formats, and Xero Central recommends OFX or QFX over CSV when you have them. Use Import a Statement from the bank account's menu (Xero Central). For the CSV route, see the Xero import guide.
- GnuCash: the manual covers File, then Import, then Import OFX/QFX transactions. GnuCash asks which of your accounts the file belongs to, then opens its import matcher so you can assign each transaction (GnuCash manual 6.16).
Limits
- We haven't tested an import in QuickBooks Online, Xero or GnuCash. The file follows the OFX 1.02 layout, and the app notes above come from each vendor's help pages.
- The file isn't a .qfx or .qbo file, and we don't claim it works with Quicken or QuickBooks Desktop.
- Every file uses the same placeholder account number (
STATEMENTCSV) and currency USD, because a statement PDF doesn't give us your real account details. Apps that remember accounts by the ID in the file will treat statements from different accounts as one account. GnuCash, for example, remembers the account you chose for that ID and doesn't ask again. If you import several accounts, open the .ofx file in a text editor and change the value after <ACCTID> for each account before you import.
- Non-USD statements will still say USD.
- Scanned or image-only PDFs can't be read. The parser reads lines that have a date, a description and an amount with cents. It labels Chase, American Express, Bank of America, Citi and Capital One statements when it recognizes them and treats anything else as Generic.
Sources