Convert Chase PDF bank statement to Xero

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

Chase PDF statement details

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.

Chase uses three different layouts

• Business checking splits transactions into sections: Deposits and Additions, Checks Paid, ATM & Debit Card Withdrawals, Electronic Withdrawals, Other Withdrawals, Fees. Every section has its own DATE, DESCRIPTION and AMOUNT header and its own total line.
• Personal checking (Chase Total Checking and similar) prints one Transaction Detail table with DATE, DESCRIPTION, AMOUNT and BALANCE columns.
• Credit card prints an Account Activity list grouped by cardholder, with a Date of Transaction, a merchant description and a dollar amount.

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".

Settings for a Chase PDF statement

• Date: transaction rows show month and day only, such as 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.
• Amount: comma for thousands, point for decimals. The dollar sign appears only on the first row of each section and on total lines. Business checking prints every amount without a sign, and the section decides whether it is money in or money out. Personal checking prints withdrawals with a leading minus. Credit cards print purchases as positive and payments and refunds as negative.
• Account number: checking statements print a 15-digit number with leading zeros, such as 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.
• Account type and currency: checking for the two checking layouts, credit card for the card layout, USD throughout.

The sign is in the section header, not in the amount

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.

Card purchases carry two dates

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.

Chase hides section markers inside the PDF

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.

Descriptions arrive in pieces and on extra lines

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.

Summary tables look like transactions

Several tables use the same dates, amounts and column widths as the transaction rows:

• Checking Summary lists each section with an INSTANCES count and a signed total.
• Daily Ending Balance prints three DATE and AMOUNT column pairs side by side, which can read as twenty or more extra transactions with no description.
• ATM & Debit Card Summary repeats per-card totals, and Service Charge Summary repeats the fee.
• Account Summary on card statements lists Previous Balance, Payments, Purchases, Fees and New Balance, and the first page also carries a calendar grid of day numbers, a remittance coupon with a long digit string, and year-to-date totals.

None of these are transactions. Reading any of them alongside the real rows creates duplicates or phantom entries.

The statement gives you three ways to check the result

• Business checking: every section ends with a Total line, and the Checking Summary states how many transactions each section has. Sixty-four card withdrawals totalling 1,727.76 in the summary must match sixty-four rows in the section.
• Personal checking: the BALANCE column on every row, plus Beginning Balance and Ending Balance rows printed inside the table.
• Credit card: Previous Balance minus Payments plus Purchases plus Fees plus Interest must equal New Balance, and each cardholder block ends with 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.

Credit card statements have their own rules

• Rows are grouped by cardholder, and the cardholder's name is printed after the group, not before it. Assigning a row to a card means reading forward to the next name line.
• Transaction dates are not sorted. A February statement can list 02/22 before 02/20, and a statement that closes in early January mixes December and January dates in the same list. The year must come from the Opening/Closing Date, not from the order of the rows: any month later than the closing month belongs to the previous year.
• Purchases are positive and payments are negative on the statement. Accounting software that imports into a credit card account usually expects the opposite sign convention, so the converter must flip signs consistently, or the balance will run backwards.
• Merchant text carries processor prefixes such as IN *, PY * and SQ *, phone numbers and state codes. Those are useful for rules but noisy as payee names.
• Two identical rows can be genuine. The same online store charging 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.

Pages that are not part of the statement

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.

Statements in Spanish

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.

Scanned copies

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.

PDF input challenges

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.

Page breaks

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.

OCR

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.

PDF questions

Can I convert a scanned bank statement?

Yes. Review the OCR result and reconcile every balance movement. Scans with faint printing, rotation, or handwritten marks need more checking than searchable PDFs.

Why does copying and pasting a PDF into Excel fail?

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.

How do I know whether the PDF contains searchable text?

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.

Xero import settings

Xero imports bank transactions through Accounting, Bank accounts, Import a Statement (also reached as Manage Account, Import a Statement). The file goes into the bank account's reconcile list, where Xero matches each line to invoices, bills and bank rules, or creates a spend or receive money transaction.

• OFX is the format to aim for. It carries the date, the amount, a payee, a description, a reference, a check number and a unique transaction ID. Xero uses the ID to skip lines it already has, so re-importing a period does not double it.
• QBO and QFX are OFX with extra header fields for QuickBooks and Quicken. Xero reads them as OFX, either directly or after renaming the extension to .ofx. If a QBO, QFX or OFX file downloaded from a bank is rejected, the file usually has a header, encoding or date format Xero does not accept; converting it to a plain OFX fixes that.
• CSV works when the columns match what Xero expects. A CSV downloaded from a bank often needs mapping on import and sometimes fails on the date or amount format. A CSV written for Xero carries the column names Xero maps on its own: Date, Amount, Payee, Description, Reference, Check Number.
• PDF must be converted first, to OFX or to a Xero CSV.

Settings that matter:

• Account: the Xero bank account is chosen before the upload. The account number inside the file is not used to pick the account, but keep it stable per account so the file is recognized on the review screen.
• Account type: bank or credit card. Xero keeps the statement's sign convention for credit cards, so a card purchase stays a debit; the converter should not flip signs for Xero the way it does for some other targets.
• Dates: four-digit years. In CSV, use one order for the whole file and confirm it on the import screen; day-month and month-day are both accepted but Xero must be told which one.
• Amounts: one signed Amount column, or separate Debit and Credit columns, in a CSV. No currency symbols or thousands separators. Money out is negative in the single-column layout.
• Payee and description: Xero shows Payee as the contact and Description as the transaction text, and bank rules match on either. Put the merchant name in Payee and the bank's transaction text in Description. Reference is a free field that other targets do not have; use it for the bank's reference number.
• Transaction IDs: unique per line and stable per transaction, so a second import of the same statement skips what is already there instead of duplicating it.
• Balances: Xero does not read an opening or closing balance from the file. Check the statement balance in Xero against the printed closing balance after import.

Xero questions

Should I import OFX or CSV into Xero?

OFX. It carries the payee, description, reference and check number in separate fields and gives Xero a transaction ID for duplicate checks. CSV is fine when the file was written for Xero with the right column names; a bank's own CSV usually needs mapping and cleanup.

Xero says my OFX, QFX or QBO file is invalid. What is wrong?

Most often the file has a header Xero does not read, non-UTF-8 text, dates in a format it does not accept, or a missing transaction ID. Convert the file to plain OFX and import that. Renaming QBO or QFX to .ofx helps only when the content is already clean.

Why did Xero import only some of the transactions?

Xero skips lines whose transaction ID it already has, and for CSV it skips lines it reads as duplicates by date, amount and description. Two genuine identical lines on the same day can be dropped from a CSV. Use OFX with unique IDs for those.

Why are the dates wrong after a CSV import?

The date order was misread. A file with 03/04/2026 can be read as 3 April or 4 March. Set the order on the import screen, or export dates as YYYY-MM-DD, which Xero reads without asking.

How do I undo an import?

Open the bank account, go to the statement lines or Bank Statements tab, select the imported statement and delete it. The lines disappear from reconcile and the file can be imported again.

Can I import older periods into Xero?

Yes. There is no date limit on file imports. Import periods in order and do not overlap them, so the balance in Xero follows the statements.

Does Xero read the opening balance from the file?

No. The statement balance in Xero is computed from the imported lines. Compare it to the printed closing balance after each import. If they differ, a line is missing, doubled, or has the wrong sign.