Convert a bank CSV to an IIF file
Use LedgerHarbor when a bank export gives you transaction rows in a spreadsheet and you need a private, reviewable path to an IIF file.
Best for: bank-export CSV preparation when the source includes institution-specific headers, balances, or transaction labels.
Start with the bank export, not the balance
Most bank CSV files contain more columns than the converter needs. LedgerHarbor focuses on the transaction date, the description or memo, and the value of each row. A running balance can remain in the source file for your own reference, but it is not used to create the basic IIF entries.
Useful bank CSV structures
One signed amount
Some exports place withdrawals below zero and deposits above zero in one Amount or Transaction column. Choose that column in the standard workflow.
Separate debit and credit
Other exports place money out in Debit or Withdrawal and money in in Credit or Deposit. LedgerHarbor Plus can map those two fields and calculate the signed value for each row.
How to prepare the file
- Export the transactions as CSV and keep the header row.
- Check whether the date is recognizable and whether the file uses a comma delimiter.
- Decide whether the amount is signed or split into debit and credit.
- Open the working LedgerHarbor converter, map the columns, and analyze the preview.
Bank transaction example
A split export could look like Date,Description,Debit,Credit, followed by 07/05/2026,Office supply,42.18, and 07/06/2026,Customer payment,,480.00. An empty debit or credit cell is expected when the row represents only one side of the transaction.
What to review before export
Check the date format, sign direction, descriptions, destination bank account name, and the expense or income account names. The preview shows which rows are ready and which need review; it does not compare the result against your bank's balance.
Expected result
The output is a reviewable IIF file built from the transaction fields you mapped, not a reconciliation report. Preserve the downloaded bank CSV so you can compare dates, descriptions, and amounts after export.
Limitations and compatibility
Bank exports are not standardized. Semicolon-delimited files, unusual date formats, multi-line descriptions, transfers, and bank-specific transaction types may need cleanup before conversion. LedgerHarbor is independent and is not affiliated with, sponsored by, or endorsed by Intuit Inc.; Intuit and QuickBooks are registered trademarks of Intuit Inc.
Bank CSV to IIF FAQ
Which bank columns are useful?
A date, transaction description or memo, and either a signed amount or separate debit and credit columns are useful. A balance column is not required by the core converter.
Can I keep my bank export private?
Yes. LedgerHarbor processes the selected file locally in the browser and does not send it to a conversion endpoint.
Does LedgerHarbor understand every bank CSV?
No. Bank exports vary in delimiters, date conventions, headers, and sign rules. Review the mapping and preview, and save a comma-separated copy when necessary.
CSV to IIF converterDebit and credit workflowSpreadsheet to IIF