How to Use PDF2QFX Convert+ to Import Transactions into Quicken

Troubleshooting PDF2QFX Convert+: Fix Common Conversion Errors

1. Conversion produces blank or missing transactions

• Cause: PDF contains scanned images (no selectable text) or text is embedded as images.
• Fix: Open the PDF and try to select text. If not selectable, run OCR (recommended: Adobe Acrobat, PDF-XChange, or free tools like OCRmyPDF) to convert images to searchable text, then retry conversion.

2. Dates import incorrectly or in wrong format

• Cause: Ambiguous date formats (MM/DD/YYYY vs DD/MM/YYYY) or OCR misreads (e.g., 1 vs 7).
• Fix: In PDF2QFX Convert+ settings, set the correct date format before converting. If unavailable, edit dates in the source PDF (or exported CSV) to a consistent format (YYYY-MM-DD preferred) then reconvert.

3. Amounts shifted between columns or merged fields

• Cause: Irregular column alignment, extra spaces, or OCR errors.
• Fix: Export to CSV first (if the tool supports it) and open in a spreadsheet to verify column alignment. Use find‑and‑replace or text-to-columns to separate fields, then re-import into PDF2QFX Convert+ or generate QFX from the cleaned CSV.

4. Negative amounts or credits treated incorrectly

• Cause: Different conventions for parentheses, minus signs, or CR/DR labels not recognized.
• Fix: Standardize amount format in the source (e.g., use leading negatives: -123.45). In spreadsheet, replace parentheses with a leading minus and remove CR/DR labels before conversion.

5. Duplicate transactions after import into Quicken

• Cause: Quicken’s duplicate detection differs from the converter’s output, or transactions already exist.
• Fix: Use Quicken’s “Find & Remove Duplicates” tool. When converting, enable any “Include unique ID” or “Match original transaction ID” option so the QFX contains consistent identifiers.

6. Unsupported PDF layout or multiline descriptions split incorrectly

• Cause: Bank statement designs with wrapped descriptions or footers inserted between rows.
• Fix: Preprocess the PDF: convert to plain text and clean line breaks (merge wrapped lines belonging to the same transaction). Tools: text editors, Python scripts, or spreadsheet formulas to join lines based on date/amount patterns.

7. Error: “Unable to parse PDF” or crashes

• Cause: Corrupt PDF, password protection, or very large file.
• Fix: Confirm PDF opens normally in a reader; remove password protection; split large statements into smaller files; rebuild the PDF (print to PDF) to remove hidden issues.

8. QFX rejected by Quicken on import

• Cause: Missing required QFX tags, wrong account type, or malformed XML.
• Fix: Open the QFX in a text editor and check for required tags ( header, ,entries). Ensure account numbers and types match your Quicken account. If unfamiliar with QFX structure, export a working QFX from Quicken (dummy transaction) and compare.

9. Currency or decimal separator problems

• Cause: Locale differences (comma vs period) or currency symbols interfering with parsing.
• Fix: Standardize to a dot decimal and remove thousands separators and currency symbols in the source or CSV before conversion.

10. General workflow checklist (step-by-step)

1. Verify PDF text is selectable; run OCR if needed.
2. Check and standardize date and amount formats.
3. Export to CSV to inspect columns and clean data when available.
4. Adjust converter settings (date format, account type, negative format).
5. Convert to QFX and open in a text editor to spot obvious XML errors.
6. Import into Quicken; resolve duplicates or rejections as needed.
7. If errors persist, split the statement into smaller chunks and convert incrementally.

Quick tools & commands

• OCR: Adobe Acrobat, PDF-XChange, OCRmyPDF (CLI)
• Text cleanup: Excel/Sheets (Text to Columns), Sublime/VS Code (regex), Python (pandas)
• QFX inspection: any text editor

If you want, I can walk through a specific PDF you have (describe the error or paste a sample transaction line) and provide exact fix steps.