CSV → QuickBooks Desktop US (IIF General Journal)
Prepare General Journal entries for QuickBooks Desktop US from an original CSV, after explicitly reviewing the ledger accounts and posting dates.
Purpose
Upload the original CSV. Inspect its canonical columns or map actual fields. Identify bank ledger and counter-accounts, confirm genuine BOOKED status, posting dates and tax review. The free Java inspection verifies destination representability before a paid or eligible trial conversion produces an .iif file.
Workflow fit
For accountants transferring reviewed, representable bank transactions into a QuickBooks Desktop US company file as General Journal entries, not as a bank-feed upload.
Implementation note
Not QuickBooks Online/QBO bank CSV. No automatic connection, posting, inferred VAT, inferred counter-accounts or Intuit-certified import. Make a company-file backup and verify the journal in QuickBooks Desktop before importing.
QuickBooks Desktop US · IIF General Journal (not QBO bank CSV)
No. The IIF General Journal format targets QuickBooks Desktop US. It is not a QBO bank-feed CSV, a direct API integration or an import guaranteed by Intuit.
No. You must confirm the bank ledger, counterparties and authentic posting dates. The server rejects unrepresentable or incomplete accounting evidence rather than inventing journal entries.
Yes. Source inspection and accounting destination inspection are free and do not consume trial conversions or credits. A separate paid/trial conversion is requested only after you confirm the facts.
Paid conversions start at one prepaid credit per begun 10,000,000 input bytes. Eligible trial files are limited to 10,000,000 bytes and the trial allowance; the backend confirms final pricing and limits.
No. An IIF file may be technically representable without certification in your QuickBooks version or company settings. Back up the company file and review the imported journal manually.
Related converters
Explore other production-ready routes connected to this format.