Chase statements look clean. The PDF is well-formatted, the columns line up, the totals are clear. So most bookkeepers assume converting them to Excel will be straightforward.
Then they actually try it.
Maybe they copy-paste into Excel and the descriptions split across multiple rows. Maybe they use a converter that misses the running balance column or merges deposits with debits. Maybe everything looks right but the totals don't tie to the statement's ending balance, and now they're spending an hour hunting down a $43.18 difference on a 60-page statement.
I've been on the receiving end of all of these. This post walks through what's actually going on with Chase PDFs, where each common approach breaks down, and how to get a file that imports cleanly into QuickBooks Online (or Xero, or Wave) without leaving you to chase ghosts.
Short version: Chase statements have three formatting quirks that most converters mishandle — multi-line transaction descriptions, a running balance column that gets misread as a transaction, and check images that get parsed as text. Once you know what to watch for, the fix is mostly mechanical.
Why Chase statements are deceptively hard to convert
On the surface, a Chase business or personal checking statement is one of the cleaner PDFs you'll get from a major bank. It's not a scanned image (usually), the text is selectable, and the transaction table is clearly delimited. Compared to credit union statements or scanned screenshots, you're in good shape.
But three specific things tend to break automated conversion:
1. Multi-line transaction descriptions
A typical Chase transaction looks like this in the PDF:
03/14 ORIG CO NAME:STRIPE ORIG ID:1800948598
DESC DATE:240314 CO ENTRY DESCR:TRANSFER $4,218.50
That's one transaction across two lines. Naive PDF-to-Excel converters treat each line as a separate row, which means you end up with phantom "transactions" of $0 sitting between every real one. If you just import that into QBO, every other line is junk.
The fix is to detect continuation lines (typically: no leading date, indented) and collapse them into the prior transaction's description field.
2. The running balance column
Chase shows a running balance to the right of each transaction. It's helpful for humans, terrible for converters that don't know which column is which. Some converters dump the running balance into the amount column, so a $50 transaction shows up as $50,000 (because the running balance is the cumulative total).
If you've ever imported a Chase statement and seen one transaction inflate your account balance by five figures, this is almost always the cause.
3. Check images and scanned addendums
Business checking statements often include thumbnail images of cleared checks in the back pages. The PDF will sometimes embed the check number and amount as OCR-extracted text, which a converter then reads as another transaction. So you end up with the same check duplicated — once from the transaction list, once from the image OCR.
This is rarer than the first two, but it's the kind of error that survives a quick visual review because both transactions look real.
Three ways to actually do the conversion
Depending on volume and how much your time costs, one of these will be the right fit.
Option 1: Manual copy-paste (one-off, low volume)
If you have one statement, it's text-based, and you have an hour to kill, you can:
- Open the PDF in any PDF reader
- Select the transaction table (Ctrl+A in the table area)
- Paste into a fresh Excel sheet
- Use Text to Columns (Data → Text to Columns → Fixed Width) to split into Date, Description, Amount, Balance
- Manually merge any continuation rows (sort by date, drag the descriptions up)
- Drop the running balance column
- Reformat the date to MM/DD/YYYY for QBO
- Save as CSV with three columns: Date, Description, Amount
Works for one statement. Doesn't scale. And honestly, by the time you've done the column splits and the row merges, you've spent more time than you'd think.
Option 2: A generic PDF-to-Excel tool
Tools like Adobe Acrobat, Smallpdf, or Tabula will extract the table for you. They're better than copy-paste because they preserve column alignment.
The catch: they don't understand what a bank transaction is. They'll extract the running balance as a real column. They won't merge continuation lines. They'll happily output a file that doesn't reconcile to the statement's ending balance, and you'll be left to find the error.
These tools are fine for the first pass on simple statements. For anything beyond a basic checking account — especially business accounts with ACH descriptors — you'll spend nearly as much time cleaning up the output as you would have spent on Option 1.
Option 3: A bank-statement-specific converter that reconciles
A tool built for this specific job knows what a Chase transaction looks like, knows to ignore the running balance column, and — this is the part most tools skip — reconciles the converted file against the statement's beginning and ending balance before you ever download it.
That last step is the difference between "I have a CSV" and "I have a CSV I can trust." If the totals don't tie, you'd rather find out from the converter than from QBO three weeks later when the client asks why the account is off by $87.
This is what we built YourStatementConverter to do. The reconciliation pass runs every time, on every statement. If the numbers don't tie, the tool flags it before handing you the file. 25 pages free to try — no credit card.
Importing the Excel file into QuickBooks Online
Once you have a clean Excel (or CSV) file, the QBO import is the easy part. The format QBO expects:
| Column | Format | Notes |
|---|---|---|
| Date | MM/DD/YYYY | QBO is picky — 14-Mar-2026 will fail |
| Description | Plain text | Keep it under 4,000 chars; trim ACH descriptors if long |
| Amount | Decimal, negative for debits | Or use two columns (Credit/Debit) if your CSV has them split |
To import:
- In QBO, go to Bookkeeping → Transactions → Bank transactions
- Pick the bank account, click the dropdown next to "Link account" and choose Upload from file
- Drag the CSV in, map the columns, click Next
- QBO will preview the transactions — spot-check a few
- Confirm and import
QBO will flag duplicates against transactions already in the account, so you won't double-import if you're re-running a statement.
Common errors and how to fix them
"The total doesn't match the statement ending balance"
Nine times out of ten, this is either (a) a missed continuation line that should have been merged into the prior transaction, or (b) the running balance column accidentally pulled in as an amount. Sort the converted file by amount descending — if you see one transaction wildly bigger than the rest, that's your running-balance ghost.
"QBO is rejecting the date format"
QBO wants MM/DD/YYYY. Chase PDFs sometimes export as MM/DD (with no year, since it's implicit in the statement period). You'll need to add the year manually or in Excel with a formula like =A1 & "/2026".
"Descriptions are duplicated across rows"
That's the continuation-line problem. The fix is to identify any row where the date column is empty, then merge that row's description into the previous row, then delete the empty row. In Excel: filter date column for blanks, copy descriptions up, delete the now-empty rows.
"I'm seeing checks twice"
The check-image OCR issue. Open the PDF, scroll to the back pages, see if the check images are showing extracted text underneath. If yes, you'll need a converter that knows to skip those pages, or you'll need to manually deduplicate by check number.
What about Chase credit card statements?
Chase credit card PDFs (Chase Sapphire, Ink Business, Freedom, etc.) follow a similar pattern but with two important differences:
- No running balance column. One less thing to worry about.
- Payments and credits are positive, purchases are negative (or vice versa, depending on how you set up the account in QBO). Get the sign convention right or your QBO balance will swing the wrong way.
If you're tracking a Chase business credit card in QBO as a liability account, purchases should import as positive (increase to the liability) and payments as negative (decrease). Confirm the sign convention before importing 60 transactions in the wrong direction.
When the bank just won't give you anything but PDFs
Chase will let business customers export CSVs directly from the online portal — but only for the last 90 days, and only for transactions, not for historical statements. If your client just handed you 18 months of PDFs and asked you to catch up the books, the export-from-portal route isn't there. You're converting PDFs whether you want to or not.
That's the situation we actually built the tool for. If you're stuck with a stack of PDFs and a QBO import on the other side, try it on a tricky one and see if it gets you to a reconciled Excel faster than the manual route. Worst case you've burned 15 minutes; best case you've cut hours off the catch-up.
Final checklist before you import to QBO
- Three columns only: Date, Description, Amount
- Date is MM/DD/YYYY
- Debits are negative (or split into Credit/Debit columns)
- Running balance column is removed
- No empty rows or continuation rows
- Total of Amount column = Statement ending balance − Beginning balance
If all six are true, the QBO import will be boring — which is what you want.
For more on the reconciliation step specifically, see our walkthrough on catching up months of backlogged books, where the reconciliation discipline matters even more.