QBO and OFX to CSV: a Tested Transaction-Field Reference
A QBO-to-CSV conversion is a field selection, not a reversible copy of a bank statement. This reference pack contains two fictional bank exports, independently specified expected CSV files and the exact questions to check before using a converted table. Download the complete QBO/OFX sample pack, or inspect its files individually below. No bank account or real transaction appears in the examples.
Try it free: Free QBO to CSV Converter Free to use, no account needed.
| Input to try | Expected output | What it demonstrates |
|---|---|---|
| Fictional bank statement (.qbo) | Bank CSV | Legacy OFX SGML, signed debit and credit amounts, leading-zero IDs, check number and a source timezone suffix |
| Fictional credit-card statement (.ofx) | Card CSV | XML OFX, a separate EUR account and protection of a formula-like name |
The expected files are the converter's default protected-text output, with a UTF-8 byte-order mark and CRLF row endings. They were specified from the source fields, then checked byte-for-byte against the current converter; they were not made by copying its output. The pack README states reuse terms and source references.
Try the examples in the browser
Open the QBO to CSV converter, select one input file, choose Read transactions, review the account and two rows, then download that account's CSV. Compare the downloaded file with its expected CSV in a text editor or a byte comparison. Keep Protect formula-like text in spreadsheets on for an exact match. The card example's =SAMPLE name becomes '=SAMPLE in CSV by that option; its amount remains -8.25.
The two source statements have different currencies and account sections. Process and compare them separately. The bank sample is a .qbo Web Connect-style export; the card sample is .ofx XML. This page does not require signing into a bank or QuickBooks account.
Field-by-field mapping
| Source field | CSV column | What to check |
|---|---|---|
DTPOSTED | Date; Original posted date | Date is the source calendar day in YYYY-MM-DD; the original timestamp and any offset text remain in a separate column. The tool does not shift the day to your device timezone. |
TRNAMT | Amount | Signed decimal string is retained. The bank debit -24.50 must not become positive or rounded. |
CURDEF | Currency | Statement default currency appears on each row. The bank example is USD; the card example is EUR. |
TRNTYPE | Type | Source type such as DEBIT or CREDIT is retained without inferring the amount sign. |
NAME, or PAYEE/NAME if needed | Name | A formula-like text value receives a leading apostrophe when the default protection option is enabled. |
MEMO | Memo | Text is quoted and escaped as CSV, including commas. |
FITID | Transaction ID | Leading zeros stay in the CSV bytes; spreadsheet software may still reinterpret them unless you import the column as Text. |
CHECKNUM | Check number | Included when present; 0007 is text in the bank sample. |
The bank input also contains BANKID, ACCTID and LEDGERBAL/BALAMT. They are deliberately absent from the CSV. The converter's account selector masks the account identity, and each downloaded CSV contains only the supported transaction columns. Keep the original QBO/OFX if you need balance, account identifiers or other OFX metadata. The expected CSV is neither a lossless archive nor a guaranteed import template for QuickBooks or another accounting app.
Four checks before relying on any converted file
- Compare row count, signed amounts and source dates with the original statement. A debit and a credit should retain their source signs.
- Import
Transaction IDandCheck numberas Text in a spreadsheet. CSV has no column-type schema, so opening it directly can strip zeros. - Confirm whether the destination expects a generic transaction table or a particular import layout. A correct conversion here does not complete an accounting import.
- Keep the original file. If it contains investment, loan, pending, correction or per-transaction currency data, this converter rejects it rather than silently providing a partial table. Its current bounds are 10 MiB, 10,000 transactions and 50 account sections.
For a practical walkthrough of the picker, review step and common errors, see How to convert QBO to CSV. The OFX standard is maintained by the FDX OFX Work Group; Intuit's Web Connect overview explains the bank-export context. These fictional samples illustrate the supported subset of our converter, not every OFX feature or an official bank/Intuit file.
About this reference
Version 1, 14 October 2026. TimeToTime Tools created the fictional specimens and reviewed the field mapping against the current parser. The example CSV bytes are verified by an automated pack test. You may copy and adapt the fictional fixture files with attribution to TimeToTime Tools. This technical example is not financial advice. Ads and site services may make network requests; conversion of a selected file runs locally in the browser.
Try it free: Free QBO to CSV Converter Free to use, no account needed.