Chase provides statements and transaction records for its bank and credit-card accounts.
Countries: United States, United Kingdom
Supported statement formats: PDF, CSV
Supported destinations: QuickBooks Desktop, QuickBooks Online, Quicken, Xero, CSV/Excel, Microsoft Money, Wave, MYOB, FreeAgent, Kashoo, AccountEdge Pro, Banktivity
QuickBooks Online can read a PDF statement itself: Banking, Upload transactions, choose the PDF. Try it first. Use ProperConvert when QuickBooks flags the statement for review, stops before the last page, or the account is not in QuickBooks Online.
For a short statement, type the date, memo, and amount into the destination. Reconcile the result to the closing balance.
Open the PDF statement, review the extracted transactions, choose QuickBooks Online, and save the converted file on your computer.
Choose the posted transaction date, supply a missing year from the statement period, and check statements that cross January.
Remove currency symbols from numeric cells, preserve the decimal separator, and verify debit and credit signs against the running balance.
Keep the payee or customer reference that helps identify the transaction, while avoiding repeated headers and unrelated reference numbers.
The following details were checked against Chase statements from 2020 to 2026: business checking, personal checking, and credit card, plus scanned copies and one statement issued in Spanish. Chase changes small things between account types and years, so always reconcile the converted transactions to the statement totals.
A converter that recognizes only one of these will read the other two as plain text. The Checking Summary or Account Summary near the top identifies the account type: a line such as "Chase Total Business Checking" or "Chase Total Checking" sits above the summary, and card statements show "Account Number: XXXX XXXX XXXX 6037".
07/03. Take the year from the period line that repeats on every page, for example July 01, 2020 through July 31, 2020, or from Opening/Closing Date 02/09/26 - 03/08/26 on card statements. Many Chase cycles run mid-month to mid-month (May 20 to June 18), so a statement crosses a month boundary every time and crosses the year in December.000000767025179. Anything that treats it as a number drops the zeros, and the online banking feed uses the shorter form, so an imported file may not match the existing account. Card statements mask the number and leave only the last four digits.On business checking every amount is printed as a plain positive number. 7.43 under ATM & Debit Card Withdrawals is money out; 500.00 under Deposits and Additions is money in. The only thing that tells them apart is the section header above, and that header repeats on the next page with a (continued) mark. A converter that loses track of which section it is in flips every sign from that point on, and the statement still looks fine because nothing is printed as negative.
The Checks Paid section also changes the column order. It prints CHECK NO., a ^ or * marker, DESCRIPTION, DATE PAID and AMOUNT, so the date sits far to the right of where it sits in every other section, and the description is usually empty. ^ means a check image is available; * means a gap in the check number sequence.
A debit card row reads 07/01 Card Purchase 06/29 Coffee Shop Rancho Mirage CA Card 1234. The date in the DATE column is the posting date. The date inside the description is the day the purchase happened. Chase itself uses the posting date for the balance, so that is the one that reconciles, but a bookkeeper matching receipts expects the other one. The converter should keep both and let the user choose. The trailing Card 1234 identifies which debit card was used and is useful when a statement covers several cards.
Every text-based Chase statement contains tiny invisible strings such as *start*deposits and additions, *end*checks paid section3 and *start*daily ending balance2, printed at about 4 pixels high around each section. A person never sees them. A converter that reads them knows exactly where each section begins and ends without guessing from headers. Scanned statements do not have them, because a scanner only captures what is visible, which is one reason the same statement is harder to convert as a scan.
Chase prints parts of a description at fixed horizontal positions. An ACH row can come through as three separate strings: the company name, the entry description and a PPD ID: or Web ID: reference, each starting at its own column. Reading them in file order can glue them together in the wrong sequence or without spaces.
Long descriptions wrap, and the wrapped part is printed on the next line with no date and no amount. A row such as Recurring Card Purchase 05/21 Phone Company 855-707-7328 MO Card is followed by a line that contains only 9380. That line belongs to the row above it. A converter must attach it to the previous transaction rather than drop it or treat it as a new row.
Several tables use the same dates, amounts and column widths as the transaction rows:
None of these are transactions. Reading any of them alongside the real rows creates duplicates or phantom entries.
1,727.76 in the summary must match sixty-four rows in the section.TRANSACTIONS THIS CYCLE (CARD 6037) $10726.83-, a subtotal with a trailing minus sign.If the counts and totals match and the ending balance is reached, every posted row was included exactly once.
IN *, PY * and SQ *, phone numbers and state codes. Those are useful for rules but noisy as payee names.142.31 on two different days is common, and two identical restaurant charges on the same day happen. De-duplicating by date and amount removes real transactions; each row needs its own transaction ID.A personal checking statement can open with a full page of account messages, so the summary and the transactions start on page two. Card statements continue those messages onto later pages with a (CONTINUED) heading. The address block on page one carries a mail sorting line of codes such as DRE 703 210 21420. Page footers appear as Page 2 of4 or as two fragments, 4 and Page 2 of. A converter should count pages from the Page X of Y text to confirm nothing is missing, and ignore everything else on those lines.
Chase issues statements in Spanish for customers who request them. The layout is the same but every header changes: RESUMEN DE CUENTA, Saldo Anterior, Nuevo Saldo, Fecha de apertura/cierre. A converter keyed on the English headers finds no sections at all. Numbers keep the same comma and point format.
A scanned Chase statement loses the hidden section markers, and OCR splits every word into a separate element, so rows have to be rebuilt from positions. Typical OCR errors are $l for $1, O for 0 and accented characters in Spanish statements coming through as symbols. The balance column, the section totals and the summary counts are what catch those errors, so a converter should always reconcile a scan, not only a text PDF.
Compare the converted transaction count and totals with the statement, then confirm that the calculated final balance equals the printed closing balance.
Yes. If the PDF statement is readable, its age does not prevent conversion. Confirm the year when transaction rows omit it.
No. Convert posted transactions that contribute to the statement balance. Pending or future-dated items should not be mixed into that reconciliation.
Use the destination-specific settings below, then review the file before import. The destination may require particular columns, dates, account identifiers, or sign rules.
A bank PDF can contain searchable text, scanned page images, or a mixture of both. Searchable text still needs layout analysis because transaction descriptions wrap, columns move, and headers or balances repeat at page breaks. A scanned statement adds OCR uncertainty.
A transaction may begin at the bottom of one page and continue on the next. Continuation pages can omit column headings, repeat an opening balance, or insert footer text and legal pages between transaction pages. A conversion should join split rows and exclude repeated page furniture before it writes the output.
On scanned pages, OCR can turn 0 into O, 1 into l, or 5 into S. It can also lose a minus sign or decimal mark, read two columns in the wrong order, or struggle with skewed and faint pages. The running balance is the best check: a damaged amount or missing row breaks the balance sequence.
Yes. Review the OCR result and reconcile every balance movement. Scans with faint printing, rotation, or handwritten marks need more checking than searchable PDFs.
PDF text stores page positions rather than a spreadsheet table. Wrapped descriptions, repeated headers, and visually aligned columns can paste in the wrong order or into the wrong cells.
Try selecting a transaction description in a PDF reader. If individual words can be selected, the page probably contains text. If the whole page behaves like one picture, it requires OCR.
QuickBooks Online imports bank transactions from a file through Banking, Upload transactions. It accepts QBO, QFX and OFX files, which share the OFX structure, and CSV files. Uploaded rows land in the For Review list, where QuickBooks matches them to existing entries and the user adds or excludes them.
Since 2026 the same upload screen also takes a PDF or an image of a statement (JPG, PNG, HEIC). Intuit's AI reads the pages, and a statement it cannot read with confidence is held for a manual review by Intuit staff. If the account is in QuickBooks Online and the statement is a clean PDF, try that first; it costs nothing. A converted file is the better route when the upload flags the statement or stops before the last page, when there are many statements to catch up, when the bookkeeper wants to see and fix every row before it enters the books, or when a client's statement should not be uploaded to a third party.
Settings that matter:
MM/DD/YYYY or DD/MM/YYYY depending on the company settings, digits only, four-digit years.Use OFX, QFX or QBO when the file can be made in that format. It carries the payee, the memo and the check number and gives QuickBooks a transaction ID for duplicate checks. Use CSV when a spreadsheet is the only source and a single description is enough.
The usual causes are a date column QuickBooks cannot read, an amount with a currency symbol or thousands separator, more columns than the three- or four-column layout, or a file over the size limit. Save the file with dates as digits, amounts as plain numbers, and only the needed columns.
The account was chosen during upload. QuickBooks Online does not read the account name from the file. Exclude the rows, delete them from Excluded, and upload again with the right account selected.
In For Review, select the rows, choose Batch actions, Exclude Selected. Open Excluded, select them again, Batch actions, Delete. The rows are gone and the file can be uploaded again.
QuickBooks Online skips rows whose transaction ID it has already seen and, for CSV, rows it reads as duplicates by date, amount and description. Two genuine identical rows on the same day can be dropped from a CSV. Use an OFX-type file with unique IDs for those.
Yes. The 90-day limit applies to a live bank connection, not to a file upload. Any date range can be uploaded from a file.
For one clean statement of an account that is already in QuickBooks Online, the built-in upload is the shortest path, and this page says so. A converter earns its place when the upload flags the statement for review, when a scanned or multi-year statement does not go through, when the account is in QuickBooks Desktop, Quicken, Xero or Sage instead, or when the statement must stay on your computer. The converted file goes through the same Upload transactions screen as a QBO file, with a transaction ID per row, so re-uploading a period does not double it.