OFX vs QBO vs CSV: choose by structure and target workflow.

CSV stores rows and columns without a universal bank schema. One file may use Amount; another may split Debit and Credit. Dates, signs, encodings, and header names need explicit review.

OFX represents account statements and transactions with named tags. It can retain fields such as transaction IDs and memos, but different producers may use SGML-style or XML-style variants and optional extensions.

QBO belongs to the OFX family and adds fields used by QuickBooks workflows. It is a bank statement file, not a QuickBooks Online company backup and not a guarantee that every QuickBooks release will accept it.

• You need to inspect or edit rows in a spreadsheet.
• The target workflow explicitly accepts bank CSV.
• You need a simple archive with visible columns.
• You can verify date and amount conventions.

• The target workflow accepts structured bank statements.
• You want to preserve transaction identifiers.
• You want account and statement metadata in the file.
• You can validate the target product and account connection.

Converting structured OFX/QBO to CSV flattens tags into columns. Converting CSV to QBO must infer fields that CSV may not contain. Review the output rather than assuming a change of extension preserves every detail.

The format itself does not decide privacy. A local browser tool can process any of these without upload; a server converter can upload all three. Check the actual Network behavior and privacy policy.

Use QBO to CSV or OFX to CSV when you need rows. Use the CSV formatter when the target is a QuickBooks Online bank CSV.