How to add a bank account to Xero when there is no feed

First work out whether a feed exists at all

This is worth two minutes because it decides everything that follows. In Xero, open the Accounting menu, select Bank accounts, click Add bank account and start typing the name of your bank. Xero lets you filter by country, which matters if the account is held overseas and you are searching from a UK or Australian organisation. If the bank appears, a feed exists and the rest of this post is not your problem. If it does not appear, or if it appears with a Manual upload label beside it, then no feed is available for that institution and nothing you do in the connect flow will produce one. Xero says as much in its own walkthrough: if you cannot find your bank, there is no automatic feed available for now, and you can still add the account and import statements by hand.

Eligibility is decided per account rather than per bank, which is why one account can feed perfectly while another at the same institution has nothing. A business account may be covered where a personal or joint account used for business is not. A plan tier below the one the feed requires produces the same result, as do corporate cards, secondary cards and cards issued outside the covered market. Xero says it reaches over 21,000 financial institutions, and the useful way to read that number is that coverage is broad and the exceptions are specific, so the question is never whether your bank is famous enough.

• Connect your bank to XeroXero on where feeds come from, and its own fallback: "Can't get direct bank feeds? Easily upload your bank statements into Xero yourself."
• About bank feedsWhat Xero counts as a feed, and which accounts can have one.

Adding the account without a feed

1. From the Accounting menu, select Bank accounts, then click Add bank account.
2. Search for your bank. If it is not listed, or is shown with a Manual upload label, choose Add without bank feed and click Continue.
3. Fill in the account details on the Add account screen: the account name you want to see in Xero, the account type, the currency, and the account number where you have one.
4. Save. The account now appears on your dashboard and behaves like any other bank account in Xero, including for reconciliation and reporting.

One caveat that most write-ups drop: Xero's own wording is that some banks can be added this way, not all of them. If the option is not offered for your institution, the usual workaround is to add the account as a different type and treat it the same way afterwards, which is worth asking your accountant about rather than guessing at, because the account type affects how it reports.

Importing the statement, and doing it again next month

Export the statement from your online banking first. Xero accepts OFX, QBO, QFX, QIF and CSV, and OFX is the one to pick where your bank offers it, because it carries its own field structure and skips the column mapping step entirely. CSV is the most widely available and the most work: the first import asks you to map your file's columns onto Xero's fields, with Date and Amount the only mandatory ones, and there is a checkbox to exclude the header row. Xero suggests the mapping and remembers it for that account afterwards. A PDF cannot be imported at all and has to be converted first, which in the US and Canada is what Hubdoc's statement extraction does, handing back a pre-formatted CSV that you then upload yourself.

1. From the Accounting menu, select Bank accounts. Next to the relevant account, click the menu icon of three vertical dots, then Import a statement.
2. Drag the file in, or click Select file, then click Next.
3. On the import settings step, map your columns and set the date format. Xero fills most of this in on repeat imports.
4. Review the transactions in the preview, then click Complete import. Xero drops you onto the bank reconciliation screen with the imported lines waiting.

The step that quietly causes the most trouble is the amount column. Xero wants a single signed column, money in as a positive number and money out as a negative one, and a great many bank exports give you two columns instead, or one column where spending is recorded as a positive. Folding those into Xero's shape is a manual decision made in a spreadsheet at the point where nobody is concentrating, and Xero's own walkthrough names this as the step where errors get introduced without offering any way to catch one.

• Four ways to get your banking data into XeroXero on the manual route: "You can download your bank transactions from your online banking as a OFX, QBO, QFX, QIF or CSV file, then quickly upload it to Xero."
• Import a CSV bank statementThe mapping step, the mandatory fields and the date formats.

The three things the import never checks

Everything above is the documented happy path and it works. What is worth understanding before you rely on it every month is what the import is not doing, because all three of these fail silently and you find out weeks later from a balance that will not agree.

• It counts rows, not money. Xero's own guidance stops at confirming the number of transactions matches what you expected. A row count cannot tell you that the export was truncated at a page break, that a date filter cut off the first three days, or that the closing balance disagrees with the bank's. A short file imports perfectly cleanly and leaves the account quietly wrong.
• It has no opinion on the signs. If the conversion put spending in as positive, Xero imports a month of payments as income and every line reconciles against nothing. Nothing in the process flags it, and the error is invisible until the account balance is compared against the statement by hand.
• It only partly protects you from duplicates. Xero drops statement lines it recognises as ones it already holds, and it publishes a Duplicate Statement Lines report for the ones that get through, which tells you plainly that some do. That report compares dates and amounts, so it will miss a duplicate whose sign was flipped in conversion and will flag a legitimate repeated standing order as suspect.

The duplicate risk gets sharper later rather than sooner. If the bank ever gains a Xero feed, or you reconnect one that lapsed, the feed will deliver a period you have already imported by hand, and Xero's own advice at that point is to check for missing or duplicate transactions yourself. That is the moment the whole year of careful manual imports turns into an afternoon of reading two lists against each other, and it is entirely predictable, which is the frustrating part.

• Find and remove duplicate bank statement linesXero's own cleanup path, and what it compares to decide a line is a duplicate.

When it is every month rather than once

For a one-off catch-up, none of the above matters much. You do it once, you check it once, and you move on. The calculation changes when the account will never have a feed, because then the same job repeats indefinitely and each month starts from nothing: the export, the reshape, the mapping, the import, and the hope that the file was complete. Over a client base, a quarterly consent renewal on the accounts that do feed and a monthly import on the accounts that do not is a standing workload that nobody planned for.

The alternative is to have the statement posted in as a feed rather than imported as a file. StatementClear takes the same PDF, CSV or Excel file you already export, maps the columns once per account and remembers them, then checks the lines against what is already in the account, verifies the running balance against the statement's own figures, and normalises the signs before anything is sent. The lines go into Xero through the Bank Feeds API, so the account is fed from then on and the next statement continues the same feed rather than starting another import. Those three checks map exactly onto the three gaps above, which is not a coincidence: they are the errors that put a wrong number in a ledger rather than merely costing an afternoon.