Keep the original export until the import is complete
A converted or standardized file is a working copy. Keep the original download in case the destination rejects a row or you need to compare a transaction later. This guide is about file preparation, not financial advice or account reconciliation.
1. Start with the format your bank actually gave you
A CSV is a table. OFX, QFX, and QBO commonly package transaction data in a financial-exchange format. QIF is an older line-based format that may include split transactions. Do not rename a file just to make a tool accept it; use a converter that understands the source format first.
You have CSV
Map the bank's own columns to a small, explicit transaction table. Do not guess whether a number is a debit or credit.
Standardize a bank CSVYou have OFX, QFX, or QBO
Convert the transaction records to CSV, then keep any record that needs review separate from the normal export.
Convert OFX to CSVYou have QIF
Select the source date order deliberately and inspect split or unreadable records before using the result.
Convert QIF to CSV2. Make the destination columns explicit
Before importing, identify which source field represents the posting date, description, amount, and currency if your destination needs it. A bank may provide one signed amount, separate debit and credit columns, or both. Review the header and a few transactions at the start, middle, and end of the export.
- Confirm whether a negative amount means money left the account in your source and destination.
- Keep the original transaction description when you are unsure how a destination categorizes it.
- Avoid inventing a payee, category, or missing amount from nearby rows.
3. Treat dates as a decision, not a cosmetic cleanup
A value such as 03/04/2026 can mean different dates depending on the bank and locale. Spreadsheet programs can also turn numbers into dates unexpectedly. Choose the source format explicitly and compare a few known transactions after conversion.
When a CSV date column needs correction
Use the CSV Date Column Fixer only when you know the source format or need to convert Excel serial dates. It asks for a format instead of silently choosing between ambiguous day and month values.
4. Review the file that will actually be imported
Before uploading to a budgeting or accounting service, open the final copy as plain text or through that service's preview. Count the records, check a known balance period, and look for blank dates, unexpected zero amounts, duplicated rows, or shifted columns. Keep any rows that require review separate rather than forcing them into the import.
First and last row
Check date, description, and amount formatting at both ends of the export.
A known transaction
Compare one transaction you can identify in the original bank download.
Import preview
Use the receiving service's preview when it offers one; its column rules are the final authority.
Import the reviewed copy, then keep both files briefly
After the destination accepts the file, compare its imported transaction count with your reviewed export. Keep the original and the import copy until you are satisfied that the transfer is complete.
Common questions
Should I use the bank CSV or an OFX/QIF download?
Use the format that your destination supports and that preserves the fields you need. A CSV can be easier to inspect and map; an OFX or QIF converter is useful when the bank provides structured transaction records instead.
Can this guide tell me whether transactions are correct?
No. It helps you prepare and inspect a file. Your bank statement and the receiving service's import preview are the sources to use when checking transaction accuracy.
Should I upload a bank export to a random converter?
Bank exports can contain names, merchant descriptions, balances, and account-related information. Read a tool's handling details before you use it, and keep the original file private.