Repairing a Xero bank feed gap

How to Add Missing Bank Feed Transactions to Xero

Last checked against Xero's documentation: 12 September 2026

Short answer

Short answer

First compare Xero's statement lines with the bank's statement and isolate the exact missing date range. If refreshing or repairing the feed does not restore those lines, create a manual import containing only the missing transactions, upload it to the same Xero bank account, review for duplicates, and then reconcile the repaired period.

Xero tells users changing banks to check for missing or duplicate transactions and manually import missing lines. The same careful boundary-setting applies to a late feed, a connection gap, or a feed that begins after the account's real activity.

Repair the gap, not the whole statement history

Start with evidence from both sides: the original bank statement and the statement lines already visible in Xero. Note the last correct transaction before the gap and the first correct transaction after it.

Your repair file should contain only what is absent. Importing a whole monthly statement when most of that month is already present increases the chance of duplicates and makes review harder.

The safe workflow

  1. 01

    Confirm the feed issue

    Check whether the feed is late or disconnected and whether the missing transactions have cleared at the bank.

  2. 02

    Mark the exact gap

    Compare statement lines and write down the first and last missing transactions.

  3. 03

    Prepare only missing rows

    Export them from the bank or convert the source PDF, then retain only the absent date and transaction range.

  4. 04

    Import into the same account

    Upload the repair CSV to the affected Xero bank account and inspect the preview.

  5. 05

    Reconcile the boundary

    Check both edges of the repaired period for duplicates and confirm the running balance.

The Xero actions above follow Xero's published CSV statement import instructions, including column mapping, date-format confirmation and transaction review.

Checks before you complete the import

  • The transactions are cleared at the bank rather than merely pending.
  • The first and last rows in the repair file are genuinely absent from Xero.
  • No transaction outside the identified gap is included.
  • The account balance agrees after the repair is reconciled.

What Xero itself documents

Xero's manual-import guide says the standard workflow accepts OFX, QFX, QIF, CSV and QuickBooks formats, recommends OFX where available, and directs people with PDF-only statements towards a third-party conversion service.

Xero also documents manual imports for missing lines and transactions from before a feed starts. Its troubleshooting guide says CSV imports can fail because of invalid dates, spaces, blank lines, corrupt files or incorrectly prepared data. That is another reason to review the file before treating an import as finished.

Frequently asked questions

Why are transactions missing from my Xero bank feed?

Possible causes include a late or interrupted feed, pending transactions not yet supplied by the bank, or history from before the feed start date. Check the bank and Xero before creating a manual repair.

Does Xero allow manual imports when a feed is connected?

Yes. Xero's guidance specifically refers to manually importing missing statement lines, including transactions from before a feed started.

Will Xero remove duplicate imported transactions automatically?

Some import formats may support duplicate detection, but you should not depend on it as your only control. Limit the repair file to the verified gap and review the import preview.

What if the missing transactions are only on a PDF?

Convert the original PDF to a structured CSV, verify the extracted rows, then keep only the transactions missing from Xero before import.

Related Xero guides