Convert bank CSV to OFX

Yes. Reading the CSV, reviewing transactions and creating OFX happen in your browser. No sign-up is required, and financial contents and filenames are not included in tool analytics. The sample buttons use fictional bank and card transactions.

It creates an OFX 1.02 SGML statement for one bank or credit-card account. Money out is negative and money in is positive. It does not create an OFX 2.x XML file, investment statement, invoice, journal entry or company backup. Check the import requirements of your destination app.

Choose CSV, TSV or TXT with a date, description and amount, or separate money-in and money-out columns. Optional running balances can supply the reported closing balance. Review the detected columns and use Change it under the rows if needed. Export each account separately; this tool does not split a mixed-account CSV.

Check the currency yourself; the tool may suggest one from a currency symbol and otherwise starts with USD. Choose Bank account or Credit card in OFX export settings. Purchases should be money out. If your card CSV lists purchases as positive, use Flip signs and review both payments and purchases before downloading. No currency conversion is performed.

Choose month-first or day-first dates when prompted. Rows without a valid date or amount are left out and counted in a notice. Review the parsed rows before exporting. You can edit descriptions and amounts or untick rows; only the first 200 parsed rows can be edited or excluded, and later rows are still included.

No. If running balances are present, the writer uses the latest dated row balance, reversing its sign for a credit-card account. With no balance it writes 0.00 as a placeholder and shows a notice. It does not calculate a closing balance from an opening balance or reconcile your statement. Check the balance in your destination app.

Under Advanced, enter the bank and account IDs your app expects. Empty fields use a placeholder bank ID and an account ID derived from the source transactions. Use the same account ID for later exports of one account to keep unchanged transaction IDs consistent. Stable IDs do not guarantee duplicate detection; review overlapping imports.

The OFX writer uses Windows-1252 text. Characters outside that character set are replaced or dropped and flagged for review. The Name field holds up to 32 characters and Memo up to 255, so long descriptions can be shortened. Review the generated file if text fidelity matters.

They are related formats, but apps have different import requirements. This page creates a generic OFX statement without Intuit-specific bank identifiers. Use CSV to QuickBooks for QBO or QFX output. Generating a file does not guarantee that any accounting app will accept it or authorize its bank identity.

This page reads CSV, TSV and TXT files. Save an Excel worksheet as CSV first, or use the existing CSV to QuickBooks tool for workbook input and select OFX there. For PDFs, scans and photos, choose the separate online FastOCR bank statement converter. That service uploads your file only when you choose it and uses your free or paid statement allowance.