Synthetic QIF example
!Type:Bank D01/15/2026 T-45.00 POffice supplies ^ D01/16/2026 T1200.00 PClient payment ^
QIF QBOQIF
QIF
to QBO.
Read QIF bank transaction fields into QBO with account metadata for an import check. Review the preview before downloading.
QIF is a text transaction format with date, signed amount, payee and optional memo/category lines. Date order is inferred from the whole file when possible. If all dates are ambiguous, choose a date order. Split/category details are retained as memo text, not reconstructed as accounting entries.
How your file is handledYOUR CONVERSION WORKSPACELocal first
PDF · OFX · QFX · QBO · QIF · IIF · CSV
Documents and conversion results are stored privately for 90 days to investigate errors and improve conversion quality. Temporary downloads expire after 15 minutes or first use. Storage and deletion details.
Prepare QIF transactions for a Web Connect import check
QIF generally lacks the bank metadata expected in QBO. Establish its date convention and supply the real account, currency and institution BID. A new extension and valid transaction syntax do not prove QuickBooks eligibility.
Content checked against the implemented converter on . Scope and editorial method.
Understand QIF source files · Understand QBO output files · How to assess conversion quality
A CONCRETE EXAMPLEWhat goes in.
What goes in.
What comes out.
These are synthetic examples, not customer data. Output excerpts illustrate the transaction mapping; download a sample through the converter to try the full workflow.
Illustrative QBO excerpt
<STMTTRN> <DTPOSTED>20260115000000 <TRNAMT>-45.00 <NAME>Office supplies </STMTTRN>
FIELD MAPPINGThe same transactions.
The same transactions.
A different format.
| Source field | Output | Handling |
|---|---|---|
| D date | DTPOSTED | Source dates are validated. Choose a convention when the file is ambiguous. |
| P payee / M memo | NAME / MEMO | Supported text is mapped; this does not reconstruct the original accounting structure. |
| T signed amount | Signed TRNAMT | Debit/credit direction is retained; amounts are not reconciled automatically. |
| No bank running-balance field in this reader | LEDGERBAL only if a final balance is unambiguous; checks in report | Missing balances stay missing. A balance check does not prove every transaction was extracted. |
THREE STEPS
Prepare. Convert. Review.
Check the source
Upload an unlocked QIF file up to 10 MB. Choose a date order if it cannot be established from the file.This path reads transaction fields directly; no document-reading AI is needed.
Read the preview
Compare the transaction count, date range and totals with your source. Check running-balance warnings. A clean balance check does not prove every row was extracted.
Download & validate
Download the QBO output, then inspect its mapping in your destination application. The temporary download expires after first use or 15 minutes. A separate encrypted review copy is retained for 90 days.
Questions about this conversion
When should I choose another format instead of QBO?
Use the bank's original QBO when possible. If the importer rejects institution metadata, a supported CSV mapping may be preferable to changing bank identifiers. This is not a company-file migration.
What should I check before using this export?
Compare row count, first and last dates, debit/credit direction and totals with the source. Review any balance warnings. Test the destination mapping with a copy or test account; a successful export does not prove importer compatibility.
Are my source and result deleted after download?
No. Temporary download links expire after first use or 15 minutes. A private encrypted source/result copy, including failed attempts, is retained for 90 days to investigate errors and evaluate conversion improvements. The upload notice explains storage, and the document receipt lets you request deletion.
OTHER WORKFLOWS
All converters