Synthetic QIF example
!Type:Bank D01/15/2026 T-45.00 POffice supplies ^ D01/16/2026 T1200.00 PClient payment ^
Read QIF bank transaction fields into PDF as a readable transaction report. 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 handledDocuments 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.
Establish the QIF date convention before creating the report. Categories and split details remain memo text rather than reconstructed accounts. The resulting PDF is a reading copy; use CSV or Excel to preserve full text for further work.
Content checked against the implemented converter on . Scope and editorial method.
Understand QIF source files · Understand PDF output files · How to assess conversion quality
These are synthetic examples, not customer data. Output excerpts illustrate the transaction mapping; download a sample through the converter to try the full workflow.
!Type:Bank D01/15/2026 T-45.00 POffice supplies ^ D01/16/2026 T1200.00 PClient payment ^
Transaction report 15 Jan 2026 Office supplies debit 45.00 balance 955.00 16 Jan 2026 Client payment credit 1200.00 balance 2155.00
| Source field | Output | Handling |
|---|---|---|
| D date | Date column | Source dates are validated. Choose a convention when the file is ambiguous. |
| P payee / M memo | Description (including memo when supplied) | Supported text is mapped; this does not reconstruct the original accounting structure. |
| T signed amount | Debit / Credit columns | Debit/credit direction is retained; amounts are not reconciled automatically. |
| No bank running-balance field in this reader | Balance column and separate validation report | Missing balances stay missing. A balance check does not prove every transaction was extracted. |
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.
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 the PDF 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.
Choose CSV or Excel when you need editable rows, identifiers or full Unicode text. A generated PDF is a reading report and does not preserve the bank's original appearance or authenticity.
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.
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.