Convert Chase Bank Statements to CSV for QuickBooks

You have a stack of Chase statement PDFs and need the transactions in QuickBooks Online. The account may be closed, the feed may not cover the period, or a client may have supplied only PDFs. One controlled route is to convert the unlocked Chase statement to CSV, review it, and import it manually into QuickBooks Online.

Choose direct PDF upload or a reviewed CSV

Let’s clear up a common myth. Older guides say “QuickBooks can’t read PDF bank statements.” That’s no longer true for QuickBooks Online. Intuit’s official manual-upload guide documents two routes: upload an English-language account statement as a PDF or image for extraction, or upload a structured transaction list such as CSV, QBO, QFX or OFX.

Choose the route according to where you want to review the data:

• Different limits apply to different routes. Intuit’s 350 KB guideline and 1,000-line limit apply to a structured transaction-list upload, not to the separate PDF or image statement route.
• Chase statements require section-aware review. Checking and card statements can separate deposits, payments, purchases, fees and summary totals. Whatever extraction route you use, verify which rows are transactions and which figures are statement summaries.
• CSV can be reviewed before upload. Intuit’s PDF workflow includes a side-by-side review inside QuickBooks. A CSV lets you perform the same date, description and sign checks before you start the manual import.

Both routes require review. A structured CSV is preferable when you want a reusable, inspectable file before the data enters QuickBooks.

Convert a Chase statement for QuickBooks: step by step

Step 1 — Download the PDF from Chase

Sign in at chase.com, open Statements & documents, pick the account and the statement period, and save the PDF. Chase says that, depending on account type, up to seven years of statements may be available.

If Chase offers a CSV or QuickBooks-format activity download for the full period you need, use that bank-supplied structured file. Convert the PDF only when the monthly statement is the source you actually have.

Step 2 — Convert the PDF to CSV

Upload the unlocked statement to BankStatementLab, then choose CSV for the QuickBooks Online manual-upload workflow. XLSX is useful for spreadsheet review and JSON for a custom workflow, but QuickBooks does not use either one for this CSV import path. BankStatementLab can generate OFX 1.6 SGML for supported current/checking and savings accounts, but it does not create QBO/QFX files, connect to Chase or post transactions directly to QuickBooks; you download the result, review it and upload it yourself. Test OFX against your exact QuickBooks edition and configuration before using a full period. The general conversion guide covers the checks to run on any converted statement.

Two checks matter before you continue:

• If the PDF still asks for a password, unlock it locally first. BankStatementLab rejects a file it cannot open and never asks you to upload the banking password.
• Inspect all extracted tables, not just the first preview: Chase transaction sections can appear in separate tables. Confirm the export contains one row per real transaction. Remove statement headers, balances and section subtotals if any appear, and compare the date range and signs with the PDF.

Step 3 — Import into QuickBooks Online

Follow Intuit’s CSV formatting guidance: open Bank transactions (currently under All apps → Accounting in Intuit’s US guide), then choose Upload from file from the account dropdown, choose your CSV, select the Chase account, and map the columns. QuickBooks Online accepts a 3-column layout (Date, Description, Amount) or a 4-column layout (Date, Description, Credit, Debit). Pick one layout and keep all dates in the format selected in your import screen. Map money-in and money-out using an actual deposit and payment; column labels alone do not establish the correct direction.

Step 4 — Review before you accept

Confirm the transaction count matches each statement section and page, check descriptions and signs, and verify every ambiguous value and date. For a bank account, a signed-amount CSV normally uses positive deposits and negative withdrawals; check credit-card charges and payments separately. Match rows already recorded as invoices, bills or transfers before adding new entries, then reconcile against the original statement balances. A zero difference alone does not prove every row is correct.

Chase statement format: what to watch for

Element	On a Chase statement	Why it matters for import
Transaction grouping	May be separated into deposits, payments, purchases or fees	Preserve the section context while checking transaction signs
Statement totals	Beginning, ending and section totals may sit near transactions	Do not import summary figures as transaction rows
Date format	The printed transaction date may omit the year	Add the statement year only after checking the covered period
Descriptions	A description may wrap onto another printed line	Confirm the export keeps one transaction per row
PDF type	The file may contain selectable text or scanned pages	Review OCR-derived fields more closely when the source is an image

Keep dates in one consistent format across the whole file and inspect the mapped amounts in QuickBooks’ preview before confirming the upload.

How do I import older Chase statements without duplicating the bank feed?

Import only the periods QuickBooks does not already hold, and use the upload preview to untick anything that overlaps. When a Chase account is connected, the bank feed backfills a limited window of recent history; older missing rows may need a bank-supplied activity file or converted statements, and the two collections meet at a seam where the same transaction can land twice.

A safe order of operations:

1. Compare the statement against the account register and the bank-feed review queue. Note the first feed date and any gaps.
2. Check that boundary date transaction by transaction; do not discard a whole day if only some of its entries exist.
3. Prepare an import copy containing missing transactions only, and use the preview to deselect verified duplicates. Keep the complete source export.
4. Match existing book entries before adding transactions, then reconcile the entire statement period and check the opening balance if you imported older history.

Working one file per statement period, oldest first, keeps that seam easy to control: each import has a clean start and end date, and if something does slip through you know exactly which file to look at.

Can I convert a Chase credit card statement the same way?

Yes — the conversion workflow is identical, but two things change on the QuickBooks side. First, the destination must be a credit card account, not a bank account, so charges and payments post in the right direction. Second, a Chase card statement is organized into its own labeled sections (payments and credits, purchases, fees, interest charged) and prints summary figures — previous balance, new balance, minimum payment due — that are not transactions.

Test a purchase, refund and card payment in the import preview to confirm their direction. A payment appearing on both a checking and card statement is one transfer between accounts, not a new expense on each side.

Those summary figures can become phantom rows if they are mistaken for transactions. Scan the exported file for them before upload, and compare its row count with the entries printed in the statement’s transaction sections.

A word of warning if your ledger lives in QuickBooks Desktop

This guide is written for QuickBooks Online, and the distinction matters. The PDF/image and CSV workflow above is an Online workflow. Intuit’s QuickBooks Desktop bank-feed guide says Web Connect bank-transaction imports use a .qbo file supplied by the bank.

A BankStatementLab CSV does not become a .qbo file and does not create a Desktop bank-feed import. It can still serve as a readable file for checking dates, descriptions and totals; obtain the Web Connect file from Chase when you need that Desktop route.

What this saves you

Converting the statement replaces re-keying with a reviewable transaction table. You still need to compare the file with the PDF, perform the manual QuickBooks upload, review the imported rows and reconcile the account.

Run the full mapping and duplicate checks on a small date range before importing the rest of the statement. The pricing page lists the included credits and current plan limits.

Compare bank movements with your books

For a separate comparison, export the relevant bank-account entries from your books and use the BankStatementLab reconciliation report with your processed statements. Approve reviewed proposals and export Excel, CSV or PDF with the remaining exceptions. This does not change the reconciliation status or post adjustments inside QuickBooks.

Frequently Asked Questions

Can QuickBooks Online import a Chase PDF directly?

Yes. QuickBooks Online can extract transactions from an English-language account statement uploaded as a PDF or image. Intuit presents the statement and extracted rows side by side for review. A CSV workflow is useful when you want to inspect and normalize every transaction before the manual QuickBooks upload. The 350 KB and 1,000-line limits apply to structured transaction-list uploads, not to the separate PDF statement workflow.

What’s the best file format to import into QuickBooks Online?

Use CSV when your starting point is a PDF and you want an inspectable file: QuickBooks Online maps CSV data in three columns (Date, Description, Amount) or four (Date, Description, Credit, Debit). Use a QBO, QFX or OFX file when Chase supplies one for the period. BankStatementLab exports CSV, XLSX, JSON and OFX 1.6 SGML for supported current/checking and savings accounts; it does not generate QBO or QFX files. Test any OFX import in your exact QuickBooks edition before using a full period.

Why not just download CSV/QBO straight from Chase?

Use Chase’s own CSV or QuickBooks download whenever it includes the period you need. Conversion is for cases where the available source is the formal monthly PDF, such as archived statements or documents supplied by a client.

How many transactions can I import into QuickBooks Online at once?

Intuit allows up to 1,000 lines in a structured transaction-list upload and gives a 350 KB file-size guideline for that upload path. Split a CSV into shorter date ranges when it exceeds those limits. These limits should not be presented as limits for QuickBooks Online’s separate PDF or image statement upload.

Does this work for QuickBooks Desktop too?

This guide covers QuickBooks Online. Desktop’s native bank-transaction import path is the Web Connect .qbo file, and a CSV export does not replace it, so a converted CSV cannot be imported into Desktop directly. On Desktop the converted file is still useful as the readable copy you check dates, descriptions and totals against, but the import itself needs a .qbo file from Chase or a converter that produces that format.

Can I convert a Chase credit card statement as well as a checking statement?

Yes, the conversion workflow is the same. Two things differ in QuickBooks: the destination has to be a credit card account rather than a bank account, and a Chase card statement prints summary figures such as previous balance, new balance and minimum payment due that are not transactions and must not appear as rows in the import file.

How do I avoid duplicate transactions when the Chase bank feed already covers part of the period?

Identify missing transactions against both the register and the bank-feed review queue. Check the first feed date row by row, since it may be incomplete, and import only missing items. Use the preview to deselect verified duplicates, then reconcile the whole statement period.

My Chase PDF is password-protected. What do I do?

A password-protected Chase statement has to be unlocked before it can be converted. Remove the password from the PDF first, then convert the unlocked file to CSV and import it into QuickBooks Online. BankStatementLab publishes a separate guide covering how to unlock a password-protected bank statement.

Conclusion

QuickBooks Online can extract an uploaded Chase PDF, while a CSV gives you an inspectable file before import. When you choose the CSV route, the workflow is: download the Chase PDF → convert the unlocked file to CSV → review it → map the columns → import manually → reconcile in QuickBooks Online.

Create your BankStatementLab account and test a representative statement. Check current credits on the pricing page.

---

Related articles

• Prepare a bank statement for Xero
• Guide: How to convert a bank statement PDF to Excel or CSV
• Import a bank statement into accounting software with no bank feed
• Reviewed PDF-to-OFX conversion workflow