Convert CSV to OFX: Tools and Manual Methods

You have transactions in a CSV file or an Excel sheet, and the software you want to load them into (GnuCash, Banktivity, MoneyMoney, HomeBank, or an accounting platform that accepts manual OFX imports) wants an OFX file. CSV is the universal export format, but OFX is the universal import format for personal-finance and accounting tools, and the two are not interchangeable. This guide covers three honest ways to get from CSV to OFX: free open-source converter utilities, web-based converters, and building a minimal OFX file by hand. It also starts with a question that saves many people the trouble entirely: do you actually need OFX at all?

Do You Actually Need OFX?

Before converting anything, confirm that OFX is really the format your software wants. A surprising number of CSV-to-OFX searches end with the discovery that no conversion was needed. Work through these three checks first:

1. Does your software accept CSV directly? QuickBooks Online, Xero, Wave, YNAB, and most modern accounting platforms import CSV files natively. If yours does, cleaning up your CSV (consistent dates, no currency symbols, a header row) is far less work than converting it to OFX. OFX only becomes necessary for tools that import exclusively through OFX or its cousins, such as GnuCash workflows built around OFX, MoneyMoney on the Mac, Banktivity, HomeBank, and the manual statement import in some Xero regions.

2. Is your destination QuickBooks Desktop? Then OFX is the wrong target. QuickBooks Desktop imports QBO (Web Connect) files, which are Intuit's fork of OFX with extra metadata requirements, and it will reject a plain OFX file. Follow our CSV to QBO guide instead. If you are unsure which format your tool expects, our QBO vs OFX vs CSV comparison breaks down exactly what each format contains and which software reads which.

3. Is your real source a PDF bank statement? Many people converting CSV to OFX created that CSV from a PDF statement in the first place. If that is you, there may be a shorter path that skips the CSV middle step. Jump to the PDF section near the end of this guide.

Still need OFX? Here are the three methods, starting with the most robust.

Method 1: Free Open-Source Converter Utilities

The most reliable free option is the family of open-source CSV-to-OFX utilities, of which the Python tool csv2ofx is the best-known example. These are command-line programs: you install them once, point them at a CSV file, tell them which column is which, and they emit a valid OFX file. Because the code is open, you can inspect exactly what happens to your data, and everything runs locally on your machine. Nothing is uploaded anywhere.

Step-by-Step

Best for: Anyone comfortable with a command line, recurring monthly conversions, and anyone who does not want financial data leaving their machine.

Method 2: Web-Based CSV-to-OFX Converters

Several websites convert CSV to OFX in the browser: upload or paste your CSV, map the columns in a form, and download the OFX result. For a one-off conversion with no software installation, this is the fastest route, and free tiers are common.

The critical caveat is data handling. A CSV of bank transactions contains dates, payees, amounts, and often account numbers. Before uploading it to any website, check three things:

• Where is the processing done? Some converters transform your file entirely in the browser with JavaScript, so the data never leaves your computer. Others upload it to a server. The tool's documentation or privacy page should say which; if it does not say, assume server-side.
• How long is the file retained? Look for an explicit deletion policy. A converter that keeps uploaded financial files indefinitely is a poor trade for saving ten minutes.
• Is the connection encrypted? The page must load over HTTPS. This is table stakes, but it is worth confirming before you paste account data into a form.

If a tool passes those checks, the workflow mirrors Method 1 without the terminal: upload the CSV, assign the date, amount, and payee columns, pick your date format, and download the OFX file. As with any converter, open the output in a text editor and verify dates, signs, and the transaction count before importing.

Best for: One-off conversions where installing software is not worth it, and users who have verified the tool's data handling.

Method 3: Build a Minimal OFX File by Hand

OFX is just structured text. For a small one-off batch (say, a dozen transactions your software refuses to take any other way), you can build the file yourself in a text editor. Modern OFX 2.x is plain XML, which makes hand-editing entirely practical. Here is a minimal skeleton with one placeholder transaction:

<?xml version="1.0" encoding="UTF-8"?>
<?OFX OFXHEADER="200" VERSION="220" SECURITY="NONE"
  OLDFILEUID="NONE" NEWFILEUID="NONE"?>
<OFX>
  <SIGNONMSGSRSV1>
    <SONRS>
      <STATUS><CODE>0</CODE><SEVERITY>INFO</SEVERITY></STATUS>
      <DTSERVER>20260711120000</DTSERVER>
      <LANGUAGE>ENG</LANGUAGE>
    </SONRS>
  </SIGNONMSGSRSV1>
  <BANKMSGSRSV1>
    <STMTTRNRS>
      <TRNUID>1</TRNUID>
      <STATUS><CODE>0</CODE><SEVERITY>INFO</SEVERITY></STATUS>
      <STMTRS>
        <CURDEF>USD</CURDEF>
        <BANKACCTFROM>
          <BANKID>123456789</BANKID>
          <ACCTID>000111222</ACCTID>
          <ACCTTYPE>CHECKING</ACCTTYPE>
        </BANKACCTFROM>
        <BANKTRANLIST>
          <DTSTART>20260601000000</DTSTART>
          <DTEND>20260630000000</DTEND>
          <STMTTRN>
            <TRNTYPE>DEBIT</TRNTYPE>
            <DTPOSTED>20260603000000</DTPOSTED>
            <TRNAMT>-42.50</TRNAMT>
            <FITID>20260603-42.50-001</FITID>
            <NAME>EXAMPLE PAYEE</NAME>
          </STMTTRN>
        </BANKTRANLIST>
        <LEDGERBAL>
          <BALAMT>1250.00</BALAMT>
          <DTASOF>20260630000000</DTASOF>
        </LEDGERBAL>
      </STMTRS>
    </STMTTRNRS>
  </BANKMSGSRSV1>
</OFX>

To use it: duplicate the STMTTRN block once per transaction, fill in DTPOSTED (date posted, in YYYYMMDD plus an optional time), TRNAMT (signed amount, negative for money out), FITID (a unique ID per transaction; date plus amount plus a counter works), and NAME (the payee or description). Set TRNTYPE to DEBIT or CREDIT to match the sign, adjust CURDEF to your currency, set DTSTART and DTEND to cover your date range, and update the LEDGERBAL block with the closing balance and its date. The BANKID and ACCTID values identify the account; placeholder digits are fine for most personal-finance imports, which map the file to an account you choose during import. Save with a .ofx extension and UTF-8 encoding.

Be aware that some older programs expect OFX 1.x, which is SGML rather than XML: it has a plain-text header block instead of the XML declaration, and closing tags are optional. If your software rejects a 2.x file, its documentation will usually say which version it wants.

Best for: A dozen or so transactions, learning what your importer actually reads, and debugging a converter's output when an import fails.

The Three Methods Compared

Four Pitfalls That Break OFX Imports

Whichever method you choose, the same four issues cause the vast majority of failed or messy OFX imports. Check each one before you import.

Starting From a PDF Statement Instead?

A lot of CSV-to-OFX journeys start one step earlier: with a PDF bank statement. The workflow becomes PDF to CSV, then CSV to OFX, then import. Every extra conversion step is another place for dates to shift, signs to flip, or rows to go missing, so it is worth asking whether the chain can be shortened.

To be clear about what CapyParse does and does not do: CapyParse converts PDF bank statements to CSV, Excel, and QBO. It does not convert CSV to OFX, so if you genuinely need an OFX file, use one of the three methods above. But if your source is a PDF, CapyParse can still remove steps from the chain in two common cases:

• Your destination is QuickBooks: Convert the PDF straight to QBO and the OFX question disappears entirely. QuickBooks Desktop imports the QBO file directly, and QuickBooks Online takes either QBO or CSV. Our guide to converting bank statements to QBO walks through it end to end.
• Your destination also accepts CSV: If your software imports both OFX and CSV, a clean, consistent CSV from the PDF is all you need. CapyParse outputs normalized dates and a signed amount column, which sidesteps the mapping problems that push people toward OFX in the first place.

And if your target is strictly OFX-only, the two-step route still improves: convert the PDF with CapyParse to get an accurate, well-structured CSV, then feed that CSV to an open-source converter from Method 1. A consistent CSV with unambiguous dates makes the OFX step nearly foolproof.

Frequently Asked Questions

Related Articles