Bank files · Runs in your browser

Convert a CSV to OFX, version 1.x or 2.x.

Write an OFX statement from a spreadsheet export, either as modern XML (OFX 2.x) or as the older SGML form (OFX 1.x) that many programs still expect. The file is built on this device.

Using the converter

  1. Load the CSV or paste it. Lines above the real header (an account summary, for instance) are skipped automatically, and you can change how many.
  2. Confirm the columns, the amount layout and the date order. If the date order is unclear the page stops and asks you.
  3. Choose OFX 2.x or 1.x, the account type and an account identifier. Add your real institution details only if the program importing the file needs them.
  4. Convert, read the preview and warnings, then download. The generated text can be shown on the page too.

OFX 2.x XML versus OFX 1.x SGML

OFX has two syntaxes. In version 1.x, a value element is written with an opening tag and no closing tag, such as <TRNAMT>-4.50, and the file starts with a plain-text header. From version 2, the file is XML: every element is closed, the first lines are an XML declaration and an <?OFX ...?> instruction, and the text is UTF-8. This tool writes the version you choose. A fragment of the 2.x output for one transaction looks like this:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?OFX OFXHEADER="200" VERSION="220" SECURITY="NONE" OLDFILEUID="NONE" NEWFILEUID="NONE"?>
<OFX>
<SIGNONMSGSRSV1>
<SONRS>
<STATUS>
<CODE>0</CODE>
<SEVERITY>INFO</SEVERITY>
...
<BANKTRANLIST>
<DTSTART>20240304120000</DTSTART>
<DTEND>20240305120000</DTEND>
<STMTTRN>
<TRNTYPE>DEBIT</TRNTYPE>
<DTPOSTED>20240304120000</DTPOSTED>
<TRNAMT>-4.50</TRNAMT>
<FITID>20240304M450HYU3X8Z52EV</FITID>
<NAME>Corner Cafe</NAME>
</STMTTRN>
...
<LEDGERBAL>
<BALAMT>2450.91</BALAMT>
<DTASOF>20240305120000</DTASOF>
</LEDGERBAL>

The 1.x version of the same data has no closing tags on the value lines and a CRLF-separated text header, and its characters are encoded as Windows-1252 as the header declares. Characters that Windows-1252 cannot hold are replaced by a question mark, and the page counts them for you.

What each field comes from

  • Transaction type. OFX defines a fixed list: CREDIT, DEBIT, INT, DIV, FEE, SRVCHG, DEP, ATM, POS, XFER, CHECK, PAYMENT, CASH, DIRECTDEP, DIRECTDEBIT, REPEATPMT and OTHER. The page uses CHECK when the row has a check number, otherwise CREDIT for positive amounts and DEBIT for negative ones. It does not try to guess ATM or POS from the description.
  • Posted date. Written as YYYYMMDD plus 12:00:00, with no time zone, so a program that applies your local zone still lands on the same day.
  • Amount. A signed decimal with a period, negative for money leaving the account. It is computed in whole cents, so no floating-point error reaches the file.
  • Name and memo. NAME holds the first 32 characters of the description, because that is the field limit; the full text goes to MEMO if MEMO is empty.
  • Check number. Up to 12 characters.

Date order: why the page makes you choose

An entry like 03/04/2024 is genuinely two different days. The page looks at every date in the column. If any first number is above 12, the file is day-first; if any second number is above 12, it is month-first; if neither occurs, it is ambiguous and the page will not convert until you choose. If you do choose, and the data contradicts you, the rows that cannot exist are listed. Rows that happen to be valid either way are not flagged, so compare the first and last date in the status line with your statement period.

Worked example

Take a CSV with the header Date,Description,Debit,Credit, a row dated 03/04/2024 for a 4.50 debit at “Corner Cafe” and a second identical row on 03/05/2024. Because both purchases match in amount and description but fall on different days they get different FITIDs; if they were on the same day the second would carry the counter N2. With month-first order the status line reads 2024-03-04 to 2024-03-05; with day-first it reads 2024-04-03 to 2024-05-03, which is how you would spot a wrong choice.

Common mistakes

  • Choosing 1.x when the program wants XML, or the reverse. Try the other version if the first is refused.
  • Leaving the account number empty. OFX requires one, and the page will not write the file without it.
  • Expecting the file to be a bank-issued statement. It is a re-formatting of what you gave it, with a placeholder balance unless you supply one.
  • Importing the same period twice into a program that does not track FITIDs. It will create duplicates; the FITIDs only help where the importer uses them.

What this tool does not do

  • It does not certify the file for any bank or software, and it does not contact a bank.
  • It does not write investment statements, bill payments or multi-account files. One CSV becomes one statement.
  • It cannot convert PDF statements. Use the CSV the bank offers.

What happens to your CSV

The conversion is done by JavaScript running inside this page’s tool frame. The frame is sandboxed and its content security policy forbids network requests, so even a bug in the code could not send your file anywhere. The page that holds the advertising is a separate document and cannot read the frame. The file is read with the browser’s own file reader, the result is built in memory, and the download link points at a temporary address that exists only in your tab. Close the tab and it is gone. You can confirm it yourself: open your browser’s network panel, convert a file, and watch for requests. There are none.

To go the other way, see the OFX to CSV converter. For QuickBooks, use the CSV to QBO converter, and to check any OFX file use the validator.

Frequently asked questions

How do I convert a CSV to OFX?

Load the CSV, confirm the date, description and amount columns, choose the date order, enter an account number, pick OFX 2.x or 1.x, and press Convert to OFX. The page writes the statement in memory and offers it as a download. Nothing is uploaded.

Should I choose OFX 2.x or 1.x?

Use 2.x (XML) if your software reads it, because it is well-formed XML that any XML parser can check. Use 1.x (SGML) for older programs, which is the form most banks and Intuit products have produced for years. The version history is on Wikipedia: versions 1.0 to 1.6 are SGML and later ones XML. If one version is refused, try the other.

Is this the same as a QBO or QFX file?

No. QBO and QFX are Intuit’s variants of OFX 1.x with an institution block that Intuit products use. Use the CSV to QBO converter on this site if you are importing into QuickBooks. A plain OFX file has no Intuit identifiers.

Which programs read the result?

Any program that imports OFX statements may read it, but we have not tested individual programs and each applies its own rules. Run the file through the validator page first to catch structural problems.

What bank ID should I use if I do not have one?

OFX requires a bank ID in a bank statement, up to 9 characters. The page defaults to nine zeros. Some importers use the bank ID and account number to match the file to an account, so use your real routing or transit number when your software matches on it.

Why is the closing balance 0.00 in my file?

A statement in OFX must include a ledger balance. If you do not enter one, the page writes 0.00 and warns you. That value is a placeholder, not your balance. Enter your real closing balance and its date if the importer will display or use it.

How are duplicate transactions avoided on re-import?

Each transaction gets a FITID built from its date, amount, description and your account number, so the same row has the same ID every time. Identical rows on the same day get a counter so they stay distinct. Importers that track FITIDs will skip rows they already have.

Can it write credit card statements?

Yes. Choose Credit card and the page writes a credit card message set with only an account number. If your issuer lists purchases as positive amounts, pick the “positive = money out” amount layout so charges are stored as negatives.

Sources

Checked

Runs entirely in your browser. Nothing you load or type is sent or stored. This page is not affiliated with Intuit, Quicken, any bank or the OFX standards body.

Common mix-ups

  1. Open Financial Exchange 2.2 specification (Internet Archive copy)

Checked against these sources on .

Advertisement
Advertisement