Synthetic CSV example
Date,Description,Amount,Balance,Currency 2026-01-15,Office supplies,-45.00,955.00,USD 2026-01-16,Client payment,1200.00,2155.00,USD
CSV OFXCSV
CSV
to OFX.
Read CSV bank transaction fields into OFX with account metadata for an import check. Review the preview before downloading.
CSV files need a header row with a recognized Date and Description column, plus either signed Amount or Debit/Credit. Comma, semicolon and tab separators are detected. ISO dates avoid ambiguity. Malformed quoting, missing dates and invalid amounts are rejected without dropping rows.
How your file is handledYOUR CONVERSION WORKSPACELocal first
PDF · OFX · QFX · QBO · QIF · IIF · CSV
Documents and conversion results are stored privately for 90 days to investigate errors and improve conversion quality. Temporary downloads expire after 15 minutes or first use. Storage and deletion details.
Add bank transaction structure to a CSV export
The CSV must identify valid dates and signed values. OFX cannot safely merge different accounts or currencies. Retain source transaction identifiers when available and inspect placeholders before importing.
Content checked against the implemented converter on . Scope and editorial method.
Understand CSV source files · Understand OFX output files · How to assess conversion quality
A CONCRETE EXAMPLEWhat goes in.
What goes in.
What comes out.
These are synthetic examples, not customer data. Output excerpts illustrate the transaction mapping; download a sample through the converter to try the full workflow.
Illustrative OFX excerpt
<STMTTRN><DTPOSTED>20260115000000</DTPOSTED><TRNAMT>-45.00</TRNAMT><NAME>Office supplies</NAME></STMTTRN>
FIELD MAPPINGThe same transactions.
The same transactions.
A different format.
| Source field | Output | Handling |
|---|---|---|
| Date column | DTPOSTED | Source dates are validated. Choose a convention when the file is ambiguous. |
| Description / Memo columns | NAME / MEMO | Supported text is mapped; this does not reconstruct the original accounting structure. |
| Amount or Debit / Credit columns | Signed TRNAMT | Debit/credit direction is retained; amounts are not reconciled automatically. |
| Balance column, when present | LEDGERBAL only if a final balance is unambiguous; checks in report | Missing balances stay missing. A balance check does not prove every transaction was extracted. |
THREE STEPS
Prepare. Convert. Review.
Check the source
Upload an unlocked CSV file up to 10 MB. Choose a date order if it cannot be established from the file.This path reads transaction fields directly; no document-reading AI is needed.
Read the preview
Compare the transaction count, date range and totals with your source. Check running-balance warnings. A clean balance check does not prove every row was extracted.
Download & validate
Download the OFX output, then inspect its mapping in your destination application. The temporary download expires after first use or 15 minutes. A separate encrypted review copy is retained for 90 days.
Questions about this conversion
When should I choose another format instead of OFX?
Keep the original bank export when available. CSV/Excel is preferable for a combined account review; a single-account OFX export needs a checked currency and account identity.
What should I check before using this export?
Compare row count, first and last dates, debit/credit direction and totals with the source. Review any balance warnings. Test the destination mapping with a copy or test account; a successful export does not prove importer compatibility.
Are my source and result deleted after download?
No. Temporary download links expire after first use or 15 minutes. A private encrypted source/result copy, including failed attempts, is retained for 90 days to investigate errors and evaluate conversion improvements. The upload notice explains storage, and the document receipt lets you request deletion.
OTHER WORKFLOWS
All converters