How to Convert PDF Bank Statements to CSV for QuickBooks and Xero

This guide explains how to convert PDF bank statements into clean CSV files that import smoothly into QuickBooks Online and Xero. It covers common formatting issues like date normalization, debit and credit column splitting, amount signs, and encoding so your bookkeeping workflow stays accurate.

Last updated 2026-05-19

How does the PDF-to-CSV conversion workflow work?

Start with a PDF bank statement from any supported bank. Upload it to the converter, which auto-detects the bank layout, extracts transaction rows, and normalizes dates and amounts into a standard schema.

The output CSV contains Date, Description, Debit, Credit, Balance and Payee columns. Before download, the tool runs balance verification: opening balance plus credits minus debits must equal the closing balance. Discrepancies are flagged so you can review before importing into accounting software.

How do I import the CSV into QuickBooks Online?

QuickBooks Online expects specific column headers and date formatting. The converter produces a QuickBooks-friendly CSV with dates in MM/DD/YYYY or DD/MM/YYYY depending on your company locale, and amounts as plain numbers without currency symbols.

Payee names are truncated to 30 characters to match QuickBooks limits. Debits and credits are split into separate columns rather than signed amounts, which reduces import-mapping errors. If your statement uses a single Amount column with negative signs for debits, the converter splits these automatically.

What does Xero require from a CSV import?

Xero accepts CSV imports with Date, Amount, Payee, Description, Reference and Check Number fields. The converter maps bank-statement Description to Xero Description and uses the first 30 characters of the description as Payee when a dedicated payee field is missing.

Xero prefers signed amounts rather than separate debit and credit columns. The converter can output a single Amount column where debits are negative and credits are positive, matching Xero’s default bank-import template. Dates are formatted as DD/MM/YYYY for UK, AU, NZ and IE organisations, and MM/DD/YYYY for US and CA.

How are date format mismatches between countries handled?

Bank statements use local date conventions: DD/MM/YYYY in the UK, AU, NZ and most of Europe; MM/DD/YYYY in the US; and YYYY/MM/DD in some Asian statements. Importing a CSV with the wrong date format causes every transaction to fail or map to incorrect months.

The converter infers the original date format from the statement text and rewrites it into the target format before export. For QuickBooks, it uses your chosen locale. For Xero, it matches the country setting of your organisation. You can preview a few rows before downloading to confirm the dates look correct.

How are amount columns split correctly?

Some statements list debits and credits in separate columns. Others use a single Amount column where the sign indicates direction. QuickBooks usually prefers separate Debit and Credit columns, while Xero expects a single signed Amount.

The converter detects the original layout and restructures it for your target system. If the PDF has one Amount column, the converter examines the transaction type labels (Debit, Credit, Deposit, Withdrawal) or the sign to place values in the correct output columns. This prevents the common error of importing all transactions as expenses because the sign was lost.

How are encoding and special characters handled in the CSV?

Special characters in descriptions — commas, quotes, ampersands and non-Latin text — can break a CSV if it is not properly quoted. The converter uses RFC 4180 quoting: fields containing commas or quotes are wrapped in double quotes, and internal quotes are escaped.

The file is emitted as UTF-8 with a BOM so Excel on Windows opens it correctly and non-Latin characters display properly. This matters for international banks where transaction descriptions may contain accented characters, Arabic text, or Asian scripts.

Related workflows

Continue from this guide into the matching converter, accounting import, security, or country hub pages so crawlers and readers can follow the full workflow.

Frequently asked questions

Can I convert any PDF bank statement to CSV?

Yes. The converter supports any bank, with no per-bank setup. If your bank is not listed, the generic regional profile usually handles the layout correctly.

Will the CSV import directly into QuickBooks Online?

Yes. The CSV uses QuickBooks-friendly columns, date formats and a 30-character Payee field. You can map the columns during QuickBooks import or use the default mapping.

Does the CSV work with Xero too?

Yes. Choose the Xero export option and the converter emits a signed-amount CSV with DD/MM/YYYY or MM/DD/YYYY dates depending on your Xero organisation locale.

What if my statement has one Amount column instead of Debit and Credit?

The converter reads the labels and signs in the PDF and splits the values into the correct output columns for your target accounting software.

Are dates automatically reformatted?

Yes. The converter detects the original statement date format and rewrites it to match QuickBooks or Xero expectations based on your selected locale.

Is the output balance-verified before download?

Yes. Opening balance plus credits minus debits is checked against the closing balance. If the totals do not match, the discrepancy is shown so you can review before exporting.

Related ClearlyLedger resources

Use these canonical pages to compare formats, verify data handling, and move from PDF extraction into accounting review.

Loading interactive converter… Try ClearlyLedger free