Chase bank statement PDF to CSV
Chase will email a PDF for the month QBO’s feed missed, for a closed account, or for the 18-month history a new client forwarded from Gmail. Native QBO PDF import is capped and picky. Retyping Amazon and Zelle lines is how the file sits on your desk until Friday.
Drop a text-based Chase statement. LedgerDrop maps the signed Amount column (negatives → debit, positives → credit), fills opening/closing when the PDF prints them, and will not pretend a scan is data.
Download CSV only after you glance at the proof. FAIL still lets you export — you own the books.
FAQ
How do you treat Chase signed amounts?
A negative or parenthetical amount becomes Debit; a positive amount becomes Credit. The last number on the row is treated as running balance when the header says Amount / Balance.
Why not just use QuickBooks’ own PDF import?
QBO’s native path is size-capped and US-leaning. LedgerDrop is for the leftover PDFs: longer history, forwarded attachments, and statements you want to prove before import.
Does the Chase PDF get uploaded?
No. Parse runs in this browser. We do not retain statements on a server in v0.
Always verify before importing into your books. LedgerDrop does not connect to Chase, does not post to QBO, and does not claim 99.9% accuracy on every Chase template.