Xero users often need to import historical bank activity when feeds are missing, a client provides old statements, or a business is moving records from another system. The challenge is that older statements often arrive as PDFs, while Xero import workflows need structured transaction rows.
This guide shows how to move from a PDF bank statement to a Xero-ready CSV file. If you need a bank statement CSV for Xero import, BS Conv extracts PDF statement tables into CSV or Excel so you can review the data, clean the import copy, map columns in Xero, and reconcile with more confidence.
Quick answer
To import a bank statement into Xero from a PDF, convert the statement to CSV or Excel, review dates, descriptions, debits, credits, amounts, and balances, remove non-transaction rows, then upload the cleaned CSV through the Xero bank statement import workflow. Use the preview step to confirm mapping before completing the import.
When you need to import a bank statement into Xero
Xero works best when bank transactions arrive through a connected feed or a clean bank statement file. Manual import becomes useful when a feed is unavailable, a feed only pulled recent transactions, a client sends historical statements, or a business is moving older records into Xero during onboarding.
Many historical records arrive as PDF statements. Use the PDF as the official bank-issued source, then extract the transactions into spreadsheet rows, review them, and prepare a clean CSV file for the Xero import workflow.
This guide focuses on the practical path from PDF bank statement to Xero import: convert the PDF to CSV or Excel, check the extracted rows, clean the import copy, map the file in Xero, and then reconcile the imported transactions. If you are looking for a Xero bank statement converter, the useful result is a reviewed file that matches Xero import rules, not an unchecked PDF extraction.
What formats does Xero accept?
Xero bank statement import workflows commonly support structured formats such as CSV, OFX, and QIF. CSV is the most flexible option when the only available source is a PDF because the file can be opened, inspected, and corrected before import. When a valid OFX file is available for the exact period, it can provide cleaner automatic mapping. For older statement periods, a reviewed CSV created from the PDF is often the practical path.
Use PDF, Excel workbooks, screenshots, and Google Sheets as source or review layers. If the bank gives you a native CSV or OFX for the exact period, use that. If the reliable source is a PDF, convert it into reviewable CSV or Excel rows first, then create the import copy.
Method 1: Convert a PDF bank statement and import it into Xero
-
Start with the original PDF statement.
Use the bank-issued statement when possible and confirm the account, currency, opening date, closing date, and statement period.
-
Convert the PDF to CSV or Excel.
Use BS Conv as a PDF to CSV converter for Xero preparation. Use Excel first when a reviewer needs filters, notes, formulas, or category columns before creating the final CSV.
-
Review the extracted rows.
Check the first transaction, last transaction, one large debit, one large credit, long descriptions, and the ending balance where available.
-
Create a Xero-ready CSV copy.
Remove summaries, repeated headers, blank rows, disclosure text, helper columns, currency symbols, and formulas.
-
Import the CSV into Xero.
Open the relevant bank account in Xero, choose the bank statement import option, upload the cleaned CSV, map the columns, preview the transactions, and then import.
Method 2: Use a bank-exported CSV if it is available
Some banks let users download transactions directly as CSV. If your bank provides a complete CSV for the exact account and period you need, that may be faster than converting a PDF. Still, inspect the file before importing. Bank-exported CSVs often include extra columns, regional date formats, currency symbols, summary lines, or descriptions that need cleanup before Xero mapping.
If the bank CSV imports cleanly and covers the right period, use it. If the official PDF is the more complete record, convert the PDF and compare both sources. The goal is reliable rows, not just the quickest file download.
Method 3: Manual entry for very small statements
Manual entry can work when there are only a few transactions. For monthly statements with dozens or hundreds of rows, a reviewed CSV workflow is usually faster, easier to audit, and less exposed to typing errors.
If you do enter transactions manually, still keep the original PDF statement with the workpaper. Xero reconciliation depends on source records. A converted CSV or Excel workbook gives you a better review trail than scattered manual entries when another person needs to check the work later.
Xero CSV format requirements
A Xero-ready CSV should include transaction date, description, and amount at minimum. A single amount column is common: money out is negative and money in is positive, depending on the mapping expected by your Xero organisation. Some files use separate debit and credit columns instead. Preserve both columns during review if that makes it easier to compare against the PDF, then create the final import structure Xero asks for during mapping.
Keep formatting plain. Use a consistent date format, plain numeric amounts, a header row, and UTF-8 encoding. Remove currency symbols, thousands separators, merged cells, blank rows, bank logos, page footers, and summary totals. CSV is simple, but that simplicity is exactly why the file needs to be clean before upload.
Optional columns can help review. Payee, reference, check number, transaction type, card suffix, and balance may be useful in Excel. Keep a review workbook with extra details, then save a simplified CSV for import.
How to import the prepared CSV in Xero
In Xero, start from the relevant bank account rather than a generic file upload. Open Accounting, go to Bank accounts, choose the bank account that should receive the transactions, and use the import statement option. Upload the cleaned CSV and follow the mapping screen to identify the date, description, and amount fields.
The preview step matters. Confirm that deposits and withdrawals are in the right direction, dates are interpreted correctly, descriptions are readable, and the imported period is separate from transactions already present from a feed or earlier import. If the preview needs work, fix the CSV before completing the import.
Common Xero import errors and fixes
Date format not recognized
Match the CSV date format to the Xero organisation settings. Ambiguous dates such as 04/05/2026 should be checked before import.
Amounts imported backward
If money out appears as money in, reverse the sign rule or remap debit and credit columns before uploading the full statement.
Duplicate transactions
Check whether the imported period overlaps with bank feed data or a previous CSV import.
Encoding problems
Use UTF-8 when descriptions include accents, symbols, or non-English merchant names.
No transactions found
Remove extra header rows, statement summaries, blank rows, and footer notes so the CSV contains only tabular transaction data.
Wrapped descriptions
Long PDF descriptions may continue onto a second line. Keep them attached to the correct transaction before import.
What to check before reconciliation
After import, the transactions appear in the bank account workflow where they can be matched, categorized, and reconciled. Before relying on them, compare the imported period with the original PDF. Check the account, currency, first transaction, last transaction, large debits, large credits, duplicate periods, and ending balance if the statement provides one.
Import multiple months in chronological order. This makes balance gaps, missing periods, and duplicate rows easier to find. For client work, keep a consistent file name that includes business name, bank, account suffix, statement period, and status. Store the original PDF, review workbook, and final CSV together so another reviewer can trace the source.
Best fit for Xero users
This workflow is useful when bank feeds are missing, a client provides historical PDF statements, or a bookkeeper needs to reconstruct activity before reconciliation. If a native bank feed, official bank CSV, or valid OFX file already covers the exact period, that source may be faster. If the available record is a PDF, start by converting it into reviewable rows.
The strongest Xero import workflow is not simply upload and hope. It is convert, review, clean, import, preview, and reconcile. That sequence gives you speed without giving up the source checks that matter in accounting work.
Frequently asked questions
Can I import a PDF bank statement into Xero?
Xero bank statement imports need structured transaction data, not an unchecked PDF page. BS Conv helps convert PDF statements into reviewed CSV or Excel rows first, so you can prepare a clean file for the Xero import workflow.
Can I use a PDF to CSV converter for Xero?
Yes, if the source is a bank statement PDF. Convert the PDF to CSV or Excel, review the rows, then create a clean Xero-ready CSV copy before importing.
What formats does Xero accept for bank statement import?
Xero commonly supports structured bank statement imports such as CSV, OFX, and QIF. CSV is the most practical option when the source is a PDF because the rows can be reviewed and mapped before import.
Should I import monthly statements into Xero one by one?
Yes. Monthly chronological processing is usually safer. It makes missing periods, duplicate periods, balance gaps, and reconciliation problems easier to spot.
What is the biggest Xero import risk?
The most common risks are wrong date format, reversed signs, duplicate rows, encoding issues, and extra non-transaction rows copied from statement headers or summaries.
What should I check before importing a converted CSV into Xero?
Check date format, description column, amount signs, duplicate periods, blank rows, repeated headers, and whether the imported period overlaps with bank feed transactions.
Prepare a Xero-ready bank statement file.
Upload a statement PDF, inspect the extracted rows, and export CSV or Excel for Xero import preparation.