How Many Transactions Can You Import into Xero at Once?

Short answer: Xero limits a CSV bank statement import to 1,000 statement lines per file. Bigger imports, such as invoices or contacts, are capped separately, and a CSV cannot exceed 100,000 rows in any case. If your statement holds more than 1,000 transactions, split it into separate files, usually one per statement period, and import them in date order. Xero accepts CSV, OFX, QIF, and QFX for bank statements and will not read a PDF or an Excel workbook at all.

This trips people up during catch-up work, because a year of a busy operating account routinely runs 1,500 to 4,000 lines. Xero does not warn you gently. You get a rejected file or a partial import, and then you are hunting for which transactions actually landed.

Xero import limits at a glance

How Xero compares with QuickBooks Online

Both cap a manual upload, but they cap different things, and knowing which is which saves a lot of guessing when a file bounces.

What Xero's CSV actually has to look like

Xero is stricter about shape than about size. A bank statement CSV needs a Date column, a Description column, and the money either in one Amount column, where withdrawals are negative and deposits positive, or split into separate Debit and Credit columns. Both income and expense amounts have to live in the same Amount column when you use the three-column layout; you cannot scatter them.

Dates go in DD/MM/YYYY, MM/DD/YYYY, or YYYY/MM/DD, and you tell Xero which one you used during the mapping step. Do not use commas as decimal separators, and strip currency symbols and thousands separators from the amount column. The Reference field tops out at 255 characters and the cheque number at 20, so a long memo pasted into the wrong column is enough to fail the import.

How do I import more than 1,000 transactions into Xero?

Split the file. There is no setting to raise the cap and no paid tier that lifts it. The clean way to split is by statement period, because it keeps the reconciliation honest: each file then covers a period with its own opening and closing balance, so if a month is off you know exactly which file to look at rather than hunting through a merged year.

1. Sort the transactions by date, oldest first.
2. Cut the file at month or statement boundaries, keeping every file under 1,000 lines.
3. Import them in date order, oldest first, so the running reconciliation follows the real sequence.
4. After each import, check the imported line count against the transaction count on the statement.

If you are converting statements rather than editing spreadsheets by hand, the Xero bank statement converter reads the PDF and outputs a Xero-ready CSV with the columns already named the way Xero expects and the signs already correct, which removes the two failure modes that cause most rejected imports.

Why does my Xero import fail even under the limit?

Nine times out of ten it is not the count. The usual causes, in order of how often they bite:

• Date format mismatch. The file says 03/07/2026 and you told Xero the wrong order, so July 3 imports as March 7, or the row rejects outright.
• Amounts in two places. Half the values in an Amount column and half in a Debit column. Pick one layout.
• Currency symbols and commas. $1,204.50 is text, not a number. It has to be 1204.50.
• Duplicate detection. Xero blocks statement lines it thinks it has already seen, which is a feature until you are re-importing a corrected file.
• Blank descriptions. Rows with no payee text can fail or import unusably.

Does the bank feed have a limit too?

Different limit, same effect. A Xero bank feed pulls ongoing activity once connected, but the initial backfill depends entirely on what the bank hands over, and for most US institutions that is somewhere between 90 days and 12 months. Nothing you do in Xero extends it. That is why a catch-up covering a prior tax year always ends up as a statement import job, no matter how healthy the feed is, and why the 1,000-line cap matters so much in exactly the situations where you have the most transactions.

A worked example

Say you are cleaning up an 18-month backlog for a small e-commerce client whose operating account runs about 210 transactions a month. That is roughly 3,800 statement lines. The feed will backfill maybe 90 days of it. The remaining 15 months have to be imported, and at 1,000 lines per file you need at least four files, though six or seven is smarter because splitting on month boundaries makes each one reconcilable on its own. Converting 18 monthly statement PDFs produces exactly that: one clean, Xero-shaped CSV per period, in date order, with running balances you can check each month against. The bills and receipts that come with a cleanup can be handled the same way, since pulling line items out of invoice PDFs is the other half of most catch-up jobs.

Related reading

If you work in both systems, the caps and the accepted formats differ in ways that matter: see QuickBooks Online vs Xero bank statement import for the side-by-side, how many transactions QuickBooks accepts at once for the Intuit numbers, and how to import bank statements into Xero for the full walkthrough.