Split a Xero bank statement CSV into traceable batches

Split transactions while preserving the bank format

A bank statement file can fail because it is too large, contains blank lines, or uses the wrong date format. Separate those causes: split the rows first, then remove only rows confirmed as blank or invalid.

• More than 1,000 transactions cause the manual import to fail
• Blank lines create an error even though the transactions are valid
• Dates or debit/credit columns map incorrectly in the preview

• Split a large CSV into traceable batches →Keep the header and reconcile every output row.
• Diagnose CSV column counts and quoted fields →Review structural findings before changing a value or header.

Decide whether a blank line is data or noise

Xero's troubleshooting guidance distinguishes blank lines and date formatting from account reconciliation. Keep an original statement and document any excluded rows before importing.

• Count transaction rows separately from header and blank rows
• Use the bank's date format rather than a locale guess
• Do not alter transaction amounts while preparing batches

• Keep only rows that belong in the import →Exclude test, inactive, or incomplete records with a visible count.
• Diagnose CSV column counts and quoted fields →Review structural findings before changing a value or header.

Create Xero-ready batches in LocaCSV

LocaCSV does not reconcile a bank account or decide whether a transaction is a duplicate. It makes the file boundaries and excluded-row count visible.

1. 1Open the statement copy and run CSV diagnosis for blank rows and columns
2. 2Filter only confirmed blank rows if the bank export contains them
3. 3Split the remaining transactions into batches of up to 1,000 rows
4. 4Import one batch and retain Xero's result before continuing

Check row counts and dates before reconciliation

• Every batch repeats the header and stays within the transaction limit
• Input rows equal output rows plus explicitly excluded blank rows
• Dates, descriptions, and debit/credit values remain unchanged
• The Xero import log identifies each batch by filename

• Split a large CSV into traceable batches →Keep the header and reconcile every output row.
• Keep only rows that belong in the import →Exclude test, inactive, or incomplete records with a visible count.
• Diagnose CSV column counts and quoted fields →Review structural findings before changing a value or header.

If Xero still rejects the statement

Review the bank-specific columns and date format in Xero's error message. A valid split cannot fix an account, currency, or transaction-type mismatch.

• Diagnose CSV column counts and quoted fields →Review structural findings before changing a value or header.
• Keep only rows that belong in the import →Exclude test, inactive, or incomplete records with a visible count.
• Check the CSV character encoding →Choose the source encoding from the preview instead of guessing from the country.

Prepare Xero bank batches