QuickBooks imports structured rows, not PDFs, which is why statement-to-books projects stall at the first download. The reliable bridge is conversion first, mapping second, import third: turn the PDF into clean Excel, align its columns to the QuickBooks banking template once, and import a file the importer accepts on the first attempt.
Conversion quality decides everything downstream. Amounts in the wrong sign, dates in mixed formats, and running balances pasted as transactions all import as real errors that take longer to find than to prevent. The free Bank Statement Analyser outputs typed dates, signed amounts, and the bank's original columns with reconciliation enforced before download — a mismatch fails loudly instead of poisoning the ledger.
Map once and reuse: Date to Date, Description to Description, Debit and Credit to Amount split by sign, and keep the Statement Info sheet as the audit reference for the import batch. CSV works anywhere Excel does not, including direct bank-feed-style imports and accountant handoffs.
For client books with unknown history, analyse before importing. The free Bank Statement Analyser flags duplicate-heavy periods, cash intensity, and balance problems on the same PDF, so cleanup happens before import rather than as journal-entry archaeology after it.