IIF Export Review Checklist
An export is a handoff, not the end of your review. Use this checklist to compare the generated IIF with the source file before testing it in your bookkeeping workflow.
Check the transaction rows
- Dates. Confirm the first, last, and a few middle dates.
- Descriptions. Check that useful payee or memo text survived mapping.
- Signs. Compare known inflows and outflows with the source.
- Accounts. Confirm destination and balancing account names.
- Rejected rows. Resolve or document every row marked for review.
Check totals and duplicates
Compare the number of source rows with the rows in the preview and export. Investigate missing rows, repeated date-description-amount combinations, and any total difference you did not expect. Similar-looking rows may be legitimate recurring transactions, so do not delete duplicates without checking the source.
Preserve the source and test carefully
Keep the original CSV, the cleaned copy if you made one, and the generated IIF together. If your workflow supports a backup or test company, use it first and record which file and settings you tested. A small sample can reveal sign or account mapping problems before a larger handoff.
Example review note
07/12/2026,Domain renewal,-24.00 should be traceable from the source row to the preview and then to the exported IIF. If the description changed, the sign reversed, or the account name is unexpected, stop and correct the mapping before continuing.
Limitations and review guidance
LedgerHarbor shows a local preview and validation results, but it cannot promise that another application will accept every export, transaction type, account name, or field combination. Review the file and test with a backup before relying on it.
Continue with LedgerHarbor
Open the working converterColumn mapping guideSigned amount vs debit and creditCSV formatting errors