At a glance
Bank2QBO reads CSV and produces QBO. It does not merely rename the file: it converts table rows into structured OFX-style transaction records and adds account metadata.
| Format | What it is | Typical role |
|---|---|---|
| CSV | Plain table of rows and columns | Bank export and source for conversion |
| QBO | QuickBooks-oriented bank data file | Manual bank transaction import |
| OFX | Open Financial Exchange data | General financial-data exchange |
| QFX | Quicken-oriented OFX variant | Quicken transaction import |
| IIF | Intuit Interchange Format | Other QuickBooks list/transaction exchange workflows |
Why CSV needs mapping
CSV defines separators and rows but does not standardize what a column means. A negative amount may indicate a withdrawal at one bank, while another uses separate Withdrawal and Deposit fields. Dates may use different orders, and descriptions may be split across two columns.
Mapping resolves those differences explicitly. That is why reviewing the preview is essential even when the converter correctly guesses familiar headings.
Where IIF fits
IIF serves different QuickBooks exchange workflows and should not be treated as a synonym for a bank-feed file. If your goal is to bring statement activity into a bank-transactions review flow, confirm which formats your current QuickBooks product accepts for that flow.
Software capabilities and menu labels can change. Consult current product documentation before selecting a format for a critical or high-volume migration.
Decision example: choose by destination workflow
Suppose a bank offers CSV and QFX, while the intended accounting workflow asks for a QBO bank-data file. CSV is the useful source for Bank2QBO because its columns can be inspected and mapped; renaming QFX to QBO would not perform a valid conversion.
In a different case, the receiving application explicitly accepts the bank’s original OFX or QFX file. Using that documented native route may be simpler than converting CSV. Bank2QBO is appropriate when CSV is the available source and QBO is the confirmed destination format.
- Confirm the receiving workflow before converting.
- Prefer an accepted original bank format when it already meets the need.
- Do not assume similar extensions are interchangeable.
- Keep the source export regardless of the chosen format.