Try with your file
Drop your bank statement (PDF)
1 file · 100 pages max · Free preview of 2 pages
1 file selected
Save hours every week
Turn your bank statements (PDF) into Excel, CSV or OFX, without manual retyping.
Drop a PDF statement and watch the extraction happen live. Instant preview, no signup required.
An OFX converter for accountants and bookkeepers becomes valuable when a client sends archived bank statements but no usable transaction feed. The goal is not merely to produce an .ofx file. A firm needs to identify the client, account, and period; review the extracted rows; generate the right file for the right account; test the destination; and preserve evidence of what happened.
BankStatementLab exports OFX from processed statements. Use a pilot account-period to check the extraction, account details and destination import before processing a client’s archive.
Use only a statement you are authorized to process. The guest preview covers up to two pages and offers an XLSX or CSV download of up to the first ten rows of the selected table. Choosing OFX takes you to sign-up. Export OFX from the processed statement in your account. If the guest preview is missing after you sign in, upload the PDF from your account.
This page covers multi-client boundaries, review ownership, sign-off, and audit evidence. For one statement and the export mechanics themselves, use the step-by-step PDF-to-OFX conversion guide.
When should an accounting firm choose OFX conversion?
Use OFX conversion when the source statements are the available evidence and the intended destination explicitly supports the generated format. BankStatementLab produces OFX 1.6 SGML. Support for a file named .ofx does not by itself prove that a particular application, version, region, or account configuration will accept that syntax.
A bank-native structured download remains the preferable source when it covers the required period and fits the destination. Conversion is useful when that route is unavailable, incomplete, or no longer accessible.
| Selection criterion | Suitable candidate | Stop or investigate first |
|---|---|---|
| Source | Complete statement for one identified account and period | Screenshots, missing pages, or uncertain ownership |
| Account type | Checking/current or savings | Credit card, loan, investment, or another unsupported account type |
| Destination | Documented OFX route that can be tested | Unknown format support or no controlled test environment |
| Dates | Full dates, or a day/month order proved by the transaction column | Ambiguous dates or a single year across a calendar boundary |
| Account context | Verified currency, identifiers, and closing balance evidence | Values guessed from another account or a current portal view |
| Review capacity | Named preparer and reviewer with source access | Unowned batch with no sign-off or exception process |
An OFX file is structured, not self-validating. It can still carry the wrong date, sign, account identifier, or client context when source controls are weak.
What BankStatementLab does—and what remains with the firm
BankStatementLab processes the statement into transaction tables, lets the user review those rows, and generates OFX from the reviewed result. For each retained table, confirm the account type, currency, closing balance and account identifiers in the export dialog. BankStatementLab may suggest a closing balance from the processed table. Verify it against the statement for that account and period, or enter the documented closing balance if none is suggested.
The firm remains responsible for import, classification and posting. BankStatementLab has no live bank feed or direct accounting connector. Its accounting integrations overview explains the file-based handoff; confirm import requirements in the destination’s current documentation.
An active Starter, Pro or Business plan is required to create a reconciliation report and validate matches. The report compares processed statements with an accounting export and proposes matches for review. You can still open and export reports you own as Excel, CSV or PDF without an active plan. The OFX transaction file and reconciliation report serve different purposes.
A firm-ready OFX workflow, from intake to sign-off
A repeatable procedure treats each client-account-period combination as its own work unit. Avoid a generic folder of “statements to convert.” Identify the entity, account, period, and source without exposing unnecessary bank details.
| Workflow stage | Preparer action | Reviewer control | Evidence retained |
|---|---|---|---|
| 1. Register intake | Record client, entity, account label, period, source, and requested destination | Confirm scope and authorization | Intake record and original statement |
| 2. Isolate the work unit | Place only one client’s approved account material in the working boundary | Check that no other client or account is present | Folder or job identifier |
| 3. Process statement | Create the transaction table in BankStatementLab | Compare table boundaries and period with source | Processed result reference |
| 4. Review rows | Check dates, descriptions, amount signs, and table completeness | Reperform totals and verify coverage of every source transaction | Exception and correction log |
| 5. Complete OFX modal | Enter verified account type, currency, closing balance, and identifiers | Match every value to source evidence | Modal inputs or review note |
| 6. Generate and label | Create one OFX per retained table and label each output | Map every file to one source table and destination account | OFX file or ZIP manifest |
| 7. Test import | Use a small, controlled scope in the exact destination setup | Check rejects, duplicates, count, signs, and totals | Test results and approval |
| 8. Import and reconcile | Complete the approved import | Reconcile imported activity to the reviewed source | Import log and reconciliation evidence |
1. Register the client, account, and period before processing
Before upload, record the statement owner, legal entity, bank account, period, and intended destination. If any answer is uncertain, hold the job.
2. Keep strict boundaries between clients and accounts
Never combine statements because they arrived together, share a bank, or belong to related entities. Use separate work units for each client and account, apply the firm’s confidentiality and retention policies, and map every generated OFX to one approved destination account.
3. Review the processed transaction table against the source
OFX export starts from a processed statement. Review the first and last transaction, period, table boundaries, date sequence, descriptions, amount signs, repeated headers, carried balances, and subtotals. Check every transaction table. Compare every source transaction with the extracted tables, then use row count, date span, net movement and table totals as additional checks: an equal balance alone does not rule out offsetting omissions.
4. Resolve missing years only when the date pattern proves the order
Some statements show day and month on each row but the year elsewhere. A statement spanning 31 December 2025 and 2 January 2026 needs two different years. Use one missing-year value only when it fits the entire table and the day/month order is established. For dates with a missing year, use the row-level year correction where offered and verify each date against the source. Correct ambiguous dates from the original before export.
5. Complete the account details from authoritative evidence
Enter the requested account type, currency, closing balance, and identifiers from the statement or an authoritative record for the same account and period. Use a valid French or international IBAN, or supply the applicable local account and bank identifiers. French banking components are derived from the IBAN; an international IBAN is preserved across the available OFX fields and may require manual matching to the destination account. Do not copy details from a sibling account. BankStatementLab does not invent a closing balance, so resolve missing evidence rather than substituting a current balance. The OFX balance date is the date of the latest retained transaction. If the statement closes on a different date, record both dates and check how the destination handles the balance before sign-off.
6. Treat blocked exports as control exceptions
A transaction with an invalid date, missing description, or zero amount initially blocks generation. The export dialog can accept source-verified corrections for supported issues. Where offered, it can also explicitly exclude eligible invalid rows or tables. It shows the exclusion counts and checks the retained selection again; nothing is silently omitted. These actions change the export copy, not the saved extraction.
Log the exception and compare it with the statement before choosing a correction or exclusion. An excluded real transaction still needs separate resolution. Record its amount, reason, and destination treatment, and compare the retained export plus documented exclusions with the complete source population. A partial export must not be signed off as the full account period.
7. Map one OFX file to each transaction table
BankStatementLab generates one OFX file per retained transaction table. If the export contains multiple tables, the output is a ZIP containing those separate files.
A ZIP is a delivery container, not permission to merge accounts. Map each filename to its client, source table, date range, and intended destination. If ownership is unclear, stop.
Controls before and after OFX export
The best workflow preserves the same account identity and transaction population at every stage. The following table turns that principle into review points.
| Control | Before generation | After test import |
|---|---|---|
| Client and entity | Confirm intake record matches the source | Confirm the destination company or ledger is the approved one |
| Account | Verify type, currency, identifiers, and statement label | Confirm the file mapped to the intended destination account |
| Period | Confirm first date, last date, and missing-year decisions | Confirm the imported range has not shifted or truncated |
| Population | Compare retained rows plus documented exclusions with the full source | Compare accepted, rejected, and existing rows with the test log |
| Amounts | Review signs, decimals, and zero-value exceptions | Reconcile debit/credit direction and totals |
| Narratives | Resolve blank or broken descriptions | Check material truncation or character handling |
| Balance | Use the documented period-end closing balance | Reconcile the resulting position using the firm’s normal process |
| Duplicates | Identify prior imports for the same account and dates | Review destination warnings and existing transaction matches |
An accepted file can still reach the wrong account or interact badly with existing transactions. “Import completed” is an event to review, not an audit conclusion.
Run and record a small import test
OFX importers vary by version, account type, required fields, date rules, encoding, and duplicate logic. Never convert a full archive based on a generic compatibility claim. Test a complete file for a short, representative account period in the exact destination setup, using a test ledger or a controlled import preview when available. Keep the source and documented closing balance for the same period. If you test a subset, record its scope separately from the full-period sign-off. Record:
- the source and generated filename;
- destination entity and account;
- software version or configuration relevant to the test;
- exported, explicitly excluded, accepted, rejected, and existing row counts;
- imported date range and net movement;
- warnings, mapping choices, corrections, and rollback action;
- preparer, reviewer, and approval date.
Expand only after the test passes the firm’s criteria. If rejected, investigate the documented requirement instead of repeatedly changing account data.
FITIDs may support duplicate checks, but do not replace them
BankStatementLab generates the same FITID when the exported account identifiers, normalized transaction date, amount, description and occurrence are unchanged. The destination decides how it uses FITIDs, so check for duplicates during the test import and reconciliation.
The destination may ignore FITIDs, combine them with account identifiers, or apply separate date and history rules. Historical files may overlap with an old feed, manual batch, earlier import, or opening-balance work. Use layered controls: period register, account mapping, test import, destination review, and reconciliation.
Onboarding historical statements without losing the audit trail
A new client may provide years of archives with no usable feed. Inventory them by entity, account, currency, and month; identify gaps and overlaps; then pilot one representative account-period. Once it passes review and destination testing, process bounded batches. Preserve originals and track whether each period is unprocessed, reviewed, exported, tested, imported, reconciled, or held.
For the wider handoff, see how to prepare bank statements for an accountant. OFX conversion sits inside that evidence and approval framework.
Frequently asked questions
Can an accounting firm use BankStatementLab to create OFX from client statements?
Yes. BankStatementLab generates OFX 1.6 SGML from reviewed statement transactions. An active Starter, Pro or Business plan is required to create a reconciliation report and validate matches. The report compares processed statements with an accounting export and proposes matches for review. You can still open and export reports you own as Excel, CSV or PDF without an active plan. Neither workflow connects directly to your bank or posts journal entries to another system. Category suggestions still require review.
Which accounts and details are supported for OFX export?
The current OFX export supports checking or current accounts and savings accounts. For each retained table, confirm the account type, currency, closing balance and account identifiers in the export dialog. BankStatementLab may suggest a closing balance from the processed table. Verify it against the statement for that account and period, or enter the documented closing balance if none is suggested. You can use a valid French or international IBAN, or the applicable local account and bank identifiers. An international IBAN may require manual account matching in the destination because OFX 1.6 has no dedicated IBAN field.
What should a bookkeeper do when transaction dates have no year?
A statement spanning 31 December 2025 and 2 January 2026 needs two different years. Use one missing-year value only when it fits the entire table and the day/month order is established. For dates with a missing year, use the row-level year correction where offered and verify each date against the source. Correct ambiguous dates from the original before export.
Can several client accounts be combined into one OFX file?
Keep clients and accounts strictly separate. BankStatementLab creates one OFX file for each retained transaction table; when the export contains multiple tables, those files are delivered in a ZIP. Treat each file as a separately identified account-period unit and map it to one approved destination account.
What happens if one transaction is invalid?
A missing description, invalid date, or zero amount initially blocks generation. Nothing is silently dropped. Resolve supported issues in the export dialog using source-verified corrections, or explicitly exclude eligible invalid rows or tables when the dialog offers that option. These choices affect the export copy, not the saved extraction. Record exclusions and reconcile them separately before treating the account period as complete.
Does OFX guarantee a successful import or prevent duplicates?
No. Import behavior depends on the destination’s supported OFX version, configuration, validation rules, and existing data. BankStatementLab generates the same FITID when the exported account identifiers, normalized transaction date, amount, description and occurrence are unchanged. The destination decides how it uses FITIDs, so check for duplicates during the test import and reconciliation.
Build a controlled OFX workflow for client work
For an accounting practice, the value of OFX conversion is a repeatable handoff from statement evidence to a reviewable import file. BankStatementLab provides the processed table, export checks, OFX 1.6 SGML output, and separate files for separate tables. Your firm supplies the client boundary, source verification, account approval, destination test, reconciliation, and audit trail.
Start with one client, one account, and one representative period. Prove the dates, use source-verified account details and closing balance, resolve every blocked transaction, and test the exact destination before scaling the historical workload.
Create your BankStatementLab account and prepare a controlled OFX export.
Related Articles
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.