Skip to main content
Back to Articles

How to Convert a Bank Statement PDF to OFX

Check when you need OFX, then convert a bank statement PDF, verify the transaction dates and account details, and test the import.

Bank statement PDF connected to an OFX 1.6 SGML file through a reviewed-data step.

Try with your file

Drop your bank statement (PDF)

1 file · 100 pages max · Free preview of 2 pages

Save hours every week

Turn your bank statements (PDF) into Excel, CSV or OFX, without manual retyping.

Try for free

To convert a bank statement PDF to OFX, extract its transactions, review the rows, choose OFX export and confirm the account details and closing balance. Download the file, then test a short period in the destination software. BankStatementLab generates OFX 1.6 SGML; check that your destination accepts that version and account type.

If you manage several client accounts, see the OFX workflow for accounting-firm controls, sign-off, and audit trails.

When to convert a bank statement PDF to OFX

  1. Check your bank’s downloads for the dates you need. Use the bank’s own OFX file if it covers the right account and period and your software accepts it. A PDF conversion is useful when you only have an archived statement, such as for a closed account or a gap in a bank feed.
  2. Check the formats your import screen accepts. If it accepts the original PDF, you can review the transactions directly in the destination. If it requires a structured file and accepts OFX 1.6 SGML for this account, follow the steps below. If it asks for CSV, see how to prepare and map a CSV when a bank feed is unavailable. See the manual import requirements by software and region.
  3. Follow any requirement for a specific file type. For example, Intuit’s US instructions for QuickBooks Desktop Web Connect require a .qbo file. If you use that workflow, look for your bank’s QuickBooks download. Intuit’s Web Connect instructions.

How to convert a bank statement PDF to OFX step by step

1. Upload and process the statement

Start with the statement for the correct account and period. If it asks for an opening password, unlock a copy on your device if you know the password and have permission to remove it. Preview up to two pages as a guest. Choosing OFX in the guest preview takes you to sign-up. To download OFX, open the processed statement in your BankStatementLab account. If the statement you previewed is missing after you sign in, upload the PDF in your account.

Confirm the first and last transaction and check how multiple accounts or sections are separated into tables.

2. Review and correct every transaction

Compare every extracted table with every original PDF page; the default visible table may not contain the entire statement. Focus on dates, amount signs, decimal separators, multiline descriptions, missing rows, duplicated headers, and non-transaction lines such as opening balances or carried-forward totals.

Correct errors before export; investigating them after an accounting import is harder. Reconcile printed totals where available, but remember that a matching balance alone can hide offsetting errors.

3. Choose OFX as the export format

From the processed statement, choose OFX. Use it only when your destination’s documentation confirms support for OFX 1.6 SGML in the relevant product version, region, account type, and configuration.

4. Supply account, currency, and closing-balance details when requested

Before generating OFX, confirm the account type, currency, account identifiers and closing balance for each selected table. Use a valid IBAN or a local account identifier with its bank or routing identifier. Your importer may ask you to match the file to the destination account. BankStatementLab may suggest a closing balance from the processed table. Check it against the original statement for the selected account and period, and enter the statement’s closing balance if the field is blank.

5. Select the year when statement dates omit it

Use the statement period to confirm the year. If the export asks for a year because the rows only show day and month, select it from the source statement. For a date such as 03/04/2026, confirm the month using a nearby unambiguous date or the statement period.

For a fictional statement covering December 2025 and January 2026, the rows marked 31 Dec and 2 Jan need different years. Enter both full dates in the transaction rows before exporting.

6. Generate the .ofx file

Generate the export after checking the table, required account details and closing balance. BankStatementLab validates the transactions before creating the file.

A transaction with a zero amount, invalid date or missing description triggers a preflight issue. The interface can offer a correction or an explicit exclusion of eligible rows or tables from the export copy. It does not silently skip them.

Prefer correcting a genuine transaction from the original evidence. If you deliberately exclude an item, document why, check the reduced period and totals, and resolve any legitimate transaction outside this export. Do not invent an amount or description merely to make the file pass. Corrections and exclusions made within this export flow affect the export copy, not the saved source extraction; update your working records separately when necessary.

7. Handle multiple transaction tables

Each selected transaction table produces one OFX file. If you select several tables, BankStatementLab puts their OFX files in a ZIP archive. Open the ZIP and match each file to its source table, account and period.

8. Verify the import with a small controlled scope

Use the same software edition and account settings as your intended import. Start with an import preview, a reversible test account, or a short statement period that is absent from your bank feed and earlier imports.

  • Before import, record the source account, currency, first and last transaction dates, number of transactions, and totals for money in and money out. Base the counts on the transactions included in the file and record any deliberate exclusions separately.
  • In the preview or test import, check the selected destination account, row count, dates, descriptions, signs and both totals. For a fictional full statement, an opening balance of USD 1,000.00, USD 300.00 in and USD 425.00 out give a closing balance of USD 875.00. Check the inflows and outflows separately, then verify the closing balance against the source.
  • Before importing the rest, investigate skipped or rejected rows and compare the date range with entries already in the account. Check how the software handles the test rows before importing a file that includes them again.

What PDF-to-OFX conversion actually does

A statement PDF is a visual document. Even when its text is selectable, it may use separate debit and credit columns, wrapped descriptions, repeated headers, or several account tables.

OFX carries transaction and account information in named fields. BankStatementLab generates OFX 1.6 using SGML syntax, listed by the Financial Data Exchange as the last SGML-based version. See the official OFX Work Group page for its version history.

The conversion is therefore a controlled data transformation:

StageWhat happensWhat you should verify
Process the statementThe PDF is turned into one or more transaction tablesPeriod, table boundaries, dates, descriptions, signs, and amounts
Review the rowsYou correct extracted data before exportNo missing transactions, subtotals, headers, or balance rows treated as activity
Add OFX contextConfirm the required account details and closing balance. Supply the year if neededValues match the original statement and destination account
Generate the outputThe reviewed table is serialized as structured OFX outputFile count, filename extension, account details, and date range
Test the destinationYou import a small controlled scopeExact software version, configuration, account, duplicate behavior, and totals

The process creates a structured file from reviewed data. It does not claim perfect PDF interpretation or identical behavior across OFX importers; the destination still controls acceptance.

What is inside the OFX file?

The generated file follows the SGML conventions described above. At a practical level, it describes the account and contains structured transaction entries rather than page coordinates or PDF formatting.

OFX informationPurpose in the fileOperational check
Account typeIdentifies the account categoryCurrent/checking or savings accounts
CurrencySets statement-level monetary contextMatch the source account and destination ledger account
Account and bank identifiersAssociates the statement with an accountCheck the supplied IBAN or local identifiers; confirm the destination account after import
Transaction datePlaces each entry in the statement periodResolve missing years and invalid dates before generation
AmountRepresents debit or credit valueZero values trigger review; verify signs and document any exclusion
DescriptionCarries transaction narrativeMissing descriptions trigger review; preserve meaningful source text
FITIDProvides a transaction identifierUseful input for duplicate checks, but destination behavior varies
Closing balanceRecords the required statement closing balanceVerify the exact closing balance for the selected account and period

OFX export supports current/checking and savings accounts. It does not cover credit-card, investment, loan, or every other financial account statement. OFX itself can describe broader message sets, but product support and destination support are separate questions.

FITIDs can help with duplicates, but cannot control the importer

OFX transaction entries include a financial-institution transaction identifier, commonly called FITID. The OFX specification describes its primary purpose as helping a client detect duplicate responses within an account context.

BankStatementLab generates a stable FITID when the account identifiers, normalized date, amount, description and occurrence stay the same. The importer decides whether to use it to detect a duplicate.

An importer may combine FITID with account identifiers, apply its own date-range logic, or treat regenerated files differently. Corrections to transaction data can also change the identifier inputs. Compare the date range with prior imports and check how the destination handles duplicates before re-importing a full period.

For recurring work, keep an import log containing:

  • entity and destination account;
  • source statement and period;
  • generated filename and table number;
  • import date and operator;
  • row count and net movement;
  • exceptions, corrections, and rollback notes.

This small record is especially valuable for bookkeeping firms, where two team members may work on the same client at different times.

Compare bank movements with your books

With an active paid BankStatementLab plan, you can use the bank reconciliation report to compare processed statements with an accounting export. The report offers proposals for approval and exports Excel, CSV or PDF. Keep the OFX for transaction import and the report for reviewing the comparison.

Frequently Asked Questions

Can BankStatementLab convert a bank statement PDF to OFX?

Yes. BankStatementLab’s OFX export starts from a processed statement. Review and correct the extracted transactions, choose OFX, confirm the required account details and closing balance, and generate the file. The output is OFX 1.6 SGML; you should still test it in the exact destination software version and configuration.

Will the OFX file import into every accounting application?

Importers support different OFX versions, account types, fields, and validation rules. Confirm that your exact destination version accepts OFX 1.6 SGML, then use a small, controlled test before importing the full period.

Which account types can I export to OFX?

OFX export supports current or checking accounts and savings accounts. It is not an export route for credit cards, investments, loans, or every financial account type. Confirm both the source account type and the destination’s accepted account configuration before generating the file.

What account information may be required for OFX export?

Before generating OFX, confirm the account type, currency, account identifiers and closing balance for each selected table. Use a valid IBAN or a local account identifier with its bank or routing identifier. Your importer may ask you to match the file to the destination account. BankStatementLab may suggest a closing balance from the processed table. Check it against the original statement for the selected account and period, and enter the statement’s closing balance if the field is blank.

Do FITIDs prevent duplicate transactions?

BankStatementLab generates a stable FITID when the account identifiers, normalized date, amount, description and occurrence stay the same. The importer decides whether to use it to detect a duplicate. Check the date range and prior imports before loading the file.

What happens when a transaction is invalid or the statement has multiple tables?

A zero amount, invalid date or missing description triggers a preflight issue. Correct it or, where offered, explicitly exclude the affected rows or tables from the export copy. Nothing is silently omitted. Document exclusions and verify the remaining scope; export-only changes do not change the saved source extraction. Each selected transaction table produces one OFX file. If you select several tables, BankStatementLab puts their OFX files in a ZIP archive.

Turn a reviewed statement into an OFX export

Statement-to-OFX conversion is most useful when historical or client-supplied statements are the available source and the destination documents support for the generated format. BankStatementLab gives you a visible sequence: process the PDF, review and correct the transactions, add the required account context, generate the export, and validate it in a small destination test.

Keep your own copy of the original statement with the reviewed rows and import result so you can trace them to the account and period.

Create an account to process your statement and export OFX.

---
🎁 5 credits on signup, then 5/month
💎 1 credit = 1 page

Ready to prepare your OFX export?

Turn a processed statement into an OFX file, review the data, then test the import in your target software.

Try BankStatementLab