How to Convert OFX and QFX to CSV Online (Complete Guide)

Typical CSV columns after conversion

Exact headers vary by converter, but you should expect a rectangular table with transaction date, amount, description/name/memo, type, and a unique fitid when present. Example shape:

date,name,amount,type,fitid
2026-05-03,Cloud hosting,-39.99,DEBIT,txn-1002
2026-05-06,Client payment,2400.00,CREDIT,txn-1003

OFX/QFX vs bank PDF statements

Prefer OFX/QFX/CSV downloads from your bank whenever available. PDF statements are for humans and auditors; extracting tables from PDFs introduces OCR and layout risk. If your bank only gives PDF, use PDF bank statement tools—and reconcile carefully. Structured OFX/QFX is the better source when you have a choice.

Do not confuse QFX with QBO or IIF

QBO (QuickBooks Online/Web Connect related downloads) and IIF (Intuit Interchange Format for list/transaction imports) are different workflows. This guide is about statement-style OFX/QFX transaction lists to CSV. If your file opens as tab-delimited IIF headers like !TRNS, use IIF converters instead.

Optional: OFX → QFX → CSV

If a tool chain insists on a .qfx extension, run OFX to QFX first, then QFX to CSV. For Convert CSV Online’s QFX to CSV path, uploading .ofx directly is usually enough. Use the extra step only when a specific app is picky about filenames.

Optional: go straight to Excel

QFX to Excel produces .xlsx when stakeholders refuse CSV. Many bookkeepers still prefer CSV for import templates—Excel is better for human review and pivots. You can also CSV → CSV to Excel after cleaning.

Date range strategy

Download overlapping ranges carefully. Banks often allow “last 30 days” or custom ranges. Overlaps create duplicate fitids if you concatenate months blindly. Prefer mutually exclusive ranges, or dedupe on fitid after merging CSVs.

Amount sign conventions

OFX amounts are typically signed: money out negative, money in positive (conventions can vary by institution wording, but TRNAMT signing is the machine truth). In Sheets, confirm SUM of the amount column matches the change in balance for the period (± timing of pending transactions). If your template wants separate Debit and Credit columns, split with formulas: =IF(A2<0,-A2,"") style—after preserving the original signed column.

FITID is your dedupe key

When importing into a ledger that already has transactions, FITID prevents double-booking the same bank line. If FITID is missing (rare but happens in odd exports), fall back to a composite key: date + amount + name—knowing collisions are possible. Never silently drop rows without logging.

Payee cleanup

Banks stuff NAME/MEMO with store numbers, cities, and payment processor prefixes (SQ *, PAYPAL *, TST*). For category analysis, add a normalized_payee column in the CSV editor. Keep the raw name for audit; categorize from the normalized form.

Date parsing pitfalls

OFX timestamps often look like 20260503120000. Converters emit calendar dates for sheets. Watch time zones and “posted Sunday, visible Monday” effects when reconciling weekend activity. For accounting periods, decide whether you book by posted date or by your own invoice date—and document it.

Pending vs posted

Some downloads include pending authorizations that later change amount or vanish. If your CSV was taken mid-day, reconcile again after the next business day before month-end close. For month-end, download after the bank finalizes the period.

Multi-account files

Occasionally an OFX payload contains more than one account. If your CSV mixes accounts without an account column, split by account before bookkeeping. Prefer downloading one account at a time when the bank UI allows it.

Currency and FX

Foreign transactions may show in account currency already converted, or include FX details in memos. Do not assume CSV amount is original foreign currency. Match against the bank’s posted amount in the statement currency you actually account in.

Freelance bookkeeping in Google Sheets

Download monthly QFX, convert to CSV, append to a master transactions sheet, categorize with dropdowns, and build a simple P&L pivot. FITID column stops accidental duplicate appends next month.

Moving off Quicken while keeping history

Export QFX historical ranges, convert to CSV, and import into a new ledger that prefers CSV. Keep original QFX files as forensic backups.

Accountant handoff

Accountants often ask for CSV or Excel. Convert OFX/QFX, rename columns to their template (Date, Description, Amount), and send CSV + a PDF statement for attestation. The PDF remains the bank-branded artifact; CSV is the working copy.

Expense report enrichment

Filter CSV to card transactions for a trip, join to receipts elsewhere, and produce a reimbursement sheet. Raw OFX is awkward for that join; CSV is natural.

Startup cash runway chart

Founders convert weekly downloads to CSV, chart cumulative cash, and annotate financings. Speed matters more than perfect categories in early days—but still reconcile totals.

Mistake deep-dive: duplicate months

You download Jan 1–Feb 1 and Feb 1–Mar 1. The shared day duplicates. Either use half-open ranges (start inclusive, end exclusive) or dedupe fitids after concat. Duplicates inflate expenses and destroy trust in dashboards.

Mistake deep-dive: “CSV amounts don’t match Quicken”

Quicken may apply rules, splits, or renames after import. Compare to the bank—not only to Quicken registers—when diagnosing converter output. Also confirm you did not filter the CSV accidentally before summing.

Mistake deep-dive: locale decimal commas

Some regions format amounts differently in sheets after open. Keep a pure numeric amount column with . decimals in CSV, and format display separately in Excel.

Privacy and security

OFX files can include account identifiers and full transaction histories. Share on a need-to-know basis. Convert CSV Online runs everyday conversions in the browser without an account for typical use, with client-side processing for these finance tools—still follow company and personal security practices. Avoid public Wi‑Fi for downloads when possible, and do not commit bank files to public git repos.

Retention

Tax and corporate policies may require multi-year retention of statements. Keep bank PDFs plus OFX/QFX plus CSV if you rely on CSV for analysis. Redundancy is cheaper than reconstruction.

QuickBooks note

QuickBooks ecosystems sometimes prefer QBO Web Connect or native bank feeds over CSV. CSV remains useful for review, custom reports, and non-Intuit tools. Choose OFX to QBO when that is the supported import path for your QuickBooks setup—and still keep CSV for analysis if helpful.

Problem: File will not parse

Confirm it is text OFX/QFX, not a PDF renamed to .ofx. Open in a plain text editor—you should see OFXHEADER or &lt;OFX&gt;-style tags. Re-download from the bank. Do not save through Word.

Problem: Zero transactions

Date range may be empty, or the file contains investment/message types your converter is not mapping. Try a shorter recent range known to have activity. Check whether you downloaded a statement empty of &lt;STMTTRN&gt; entries.

Problem: Dates look wrong

Verify timezone/posted date interpretation. Reformat in Sheets with an explicit date format. Compare three rows to the bank UI.

Problem: Amounts off by sign

Your template may expect positive expenses. Keep a raw_amount column and a display column rather than overwriting.

Problem: Duplicate imports in accounting software

Use FITID matching. Clear the failed import, dedupe CSV, re-import. Disable any “auto add web connect” parallel path that might double-post.

Problem: Need categories like the bank app

Bank categories are often not inside OFX the way the mobile app shows them. Categorize in your sheet or ledger rules after CSV conversion.

Download and convert

In the bank portal, choose account Business Checking, date range 2026-07-01 to 2026-07-31, format QFX. Save 2026-07_business.qfx. Upload to QFX to CSV. Preview ~80 rows of activity.

Clean for the accountant template

In the Online CSV Editor, rename columns to Date, Description, Amount. Keep fitid in a hidden fourth column for your own dedupe archive, even if the accountant ignores it. Remove any account-number columns you do not want in email.

Reconcile

Bank UI shows opening 12500.00, closing 14210.50, net +1710.50. CSV SUM(Amount) equals +1710.50. Spot-check the 2400.00 client payment and the -39.99 hosting charge. Export CSV and send via secure link with the July PDF statement attached.

Next month

Download August with start date 2026-08-01 to avoid July overlap. Append to your archive after FITID dedupe against July. Boring, safe, repeatable.

Credit cards

Signs can feel inverted vs checking depending on issuer conventions. Always validate against the issuer’s web ledger. Credits (payments, refunds) vs purchases should sum to the change in balance for the period.

Brokerage / investment OFX

May include positions, trades, and income types beyond simple STMTTRN banking lines. A generic QFX→CSV path may only surface a subset. If conversion looks incomplete, use the brokerage’s CSV export for tax lots and keep OFX for cash activity only when that split is clearer.

Multi-currency

Maintain separate CSVs per currency account. Do not sum USD and EUR amounts in one column without FX conversion logic. Label files with currency codes.

Convert your bank file now

Open QFX to CSV, upload your .qfx or .ofx download, preview transactions, reconcile totals, and download UTF-8 CSV for Sheets or Excel.

Who this guide is for

Small business owners leaving Quicken exports, freelancers bookkeeping in Sheets, accountants collecting client bank activity, and anyone whose bank still speaks OFX/QFX while their tools speak CSV.

Partial-month flash reports

Leadership sometimes wants mid-month cash flash. Use a separate mid-month download labeled _flash so you do not confuse it with the official month file. Flash CSVs can be approximate; month-end CSVs must be reconciled. Naming prevents mixing them in pivots.

Multiple entities

If you operate several LLCs or properties, separate folders per entity and never reuse a sheet tab named “bank” without an entity prefix. Cross-entity paste errors are painfully expensive to unwind after tax season starts.

Separate debit and credit columns

Some paper ledgers want Debit and Credit columns instead of signed amount. Derive them with formulas from the signed Amount rather than deleting Amount. Auditors prefer a single source column with derived views.

Category and class columns

Add empty Category / Class / Project columns in your template before each month’s paste. Fill via rules or manual review. Do not expect OFX to supply your internal class codes—those are your chart of accounts, not the bank’s.

Sample rename workflow in Online CSV Editor

Upload the fresh CSV, rename headers to match the template row 1 exactly (including capitalization if your importer is strict), drop columns you will not import, download, then import. Keeping a screenshot of the “good” header row in your wiki speeds training for new bookkeepers.

Run a fire drill once a year

Once a year, pretend the feed is dead. Download OFX/QFX, convert to CSV, and import into a sandbox company file. Time the exercise. If it takes three hours of confusion, improve docs now—not during a real outage in tax season.

Communicate with your accountant during outages

Tell them you are on manual OFX→CSV for the affected weeks and that FITIDs will prevent double entry when the feed returns. Ask whether they prefer one combined CSV or weekly files. Clarity prevents duplicate work on both sides.

Training a new bookkeeper in one afternoon

Give them this path: download sample QFX from a sandbox bank account (or a redacted fixture), convert with QFX to CSV, reconcile against a provided answer key balance, rename columns to the firm template, and file into the month folder. If they can do that without help, they can cover feed outages. Record a five-minute Loom once; stop re-explaining in chat forever.

Do not mix feed and CSV for the same period carelessly

If the feed partially posted a week, reconcile which FITIDs already exist before CSV import. Blindly importing a full-month CSV on top of a partial feed is a classic double-count scenario.

Strip processor prefixes

Remove leading tokens like SQ *, PAYPAL *, TST*, POS, and similar payment-processor prefixes into a separate raw_prefix column if needed. Analysts group spend by merchant better when “COFFEE SHOP 1234” and “COFFEE SHOP 5678” collapse under one normalized label.

Rule tables in Sheets

Maintain a two-column rules sheet: match_substring → normalized_payee. Use formulas or a light script monthly. Start with the top fifty merchants by spend; long-tail noise can wait. Do not over-automate rare one-off wires.

Keep raw forever

Never overwrite the bank’s original NAME/MEMO in your archive CSV. Normalization belongs in added columns. Disputes and chargebacks refer to what the bank showed, not your cleaned label.

Personal vs business cards on one login

If personal and business downloads land in the same browser session, label files immediately with entity names. Mixed personal grocery spend into a business P&L is a painful tax cleanup. Folder discipline beats clever formulas after the fact.

Seasonal merchant cleanup

After holidays or major conferences, expect a burst of new merchant strings. Schedule a thirty-minute normalization pass in January and after big travel months. Small maintenance prevents category reports from collapsing into an “Other” bucket that hides real problems.

What “good” bank support looks like

A helpful bank confirms known OFX defects, offers a regenerated file, or points to a different export menu (often buried under “Account services” or “Statements & documents”). Keep polite, specific tickets. Vague “your download is broken” reports go nowhere; FITID-level examples get engineering attention.

Parallel path while you wait

If support is slow and books cannot wait, use the bank’s CSV download when available, or carefully convert PDF statements with reconciliation. Document that the period used a fallback source so you can replace rows when a correct OFX arrives. Never quietly leave a fallback in the official archive without a note. Replace the fallback as soon as the bank provides a clean OFX or QFX file.