Why is my HSBC bank feed a day behind in Xero?

By design. HSBC allows a transaction's reference to change within 24 hours of it posting, so the feed holds new lines back rather than import them and correct them later. It is not a fault and there is no setting that turns it off. Where the current day has to be reconciled, posting the statement covers it.

Does the HSBC feed cover HSBC Kinetic?

No. Kinetic has a separate feed, connected only from a mobile device, and only the handset the Kinetic app was installed and signed into. If that phone is not to hand, or the account holder is not the person reconciling, StatementClear posts Kinetic statements instead.

Can I get more than twelve months of HSBC history into Xero?

Yes. The feed shares twelve months at most when you connect it, but HSBC lets you download statements for older periods. Upload them in any order: dedupe stops overlaps posting twice and the balance checks flag a period that has gone missing.

Is this a real bank feed or another import?

A real feed. Lines post through Xero's official Bank Feeds API and arrive ready to reconcile, alongside whatever the native HSBC feed brings in. Nothing is handed back to you to upload.

HSBC bank feed for Xero: post the days and months the feed misses

HSBC UK's Xero feed imports twice a day but holds transactions back 24 hours, because HSBC allows references to change within a day of posting. It shares twelve months of history at most, does not cover HSBC Kinetic, and needs HSBCnet permissions for corporate accounts. StatementClear posts HSBC statements into Xero as feed lines to fill what it misses.

The HSBC feed is one of the better ones and it still leaves you waiting. Lines are held back a full day by design, because HSBC allows a transaction's reference to change within 24 hours of it posting, so today's activity is simply not there when you sit down to reconcile. Add the 90-day consent renewal, a twelve-month backfill ceiling and a Kinetic account that connects through an entirely different feed, and most HSBC users have a period somebody fills in by hand. StatementClear posts HSBC statements into Xero as live feed lines, deduped against whatever the feed has already brought in.

Join the waitlist

Where the native HSBC feed falls short

HSBC UK has a direct Xero feed covering business current, savings, credit card and foreign currency accounts, importing twice a day on a 90-day open banking consent with up to twelve months of history shared at setup. Transactions arrive on a deliberate 24-hour delay, HSBC Kinetic runs on a separate feed of its own, and corporate accounts need third-party provider permissions enabled in HSBCnet before they will connect at all.

Three HSBC-specific things decide whether the feed actually covers you. The first is the 24-hour delay. HSBC lets a transaction's reference change within a day of posting, so Xero holds new lines back rather than import them and then correct them - documented behaviour rather than a fault, and the reason the account never shows today's activity. It has its own long-running request on Xero's product ideas board. The second is HSBC Kinetic, which the main HSBC UK feed does not cover. Kinetic connects on a feed of its own, only from a mobile device, and only from the same handset the Kinetic app was installed and signed into at least once - awkward when the person reconciling is not the person holding the phone. The third is corporate: HSBC Corporate accounts will not connect until third-party provider permissions are switched on in HSBCnet, which is an internal request inside the bank rather than a setting in Xero. On top of those, the ordinary limits apply. Consent expires every 90 days and the feed stops on the expiry date, not on the day somebody notices. Backfill is capped at twelve months, so an older account's early history has to come from statements either way. A credit card feed is created against the master account and brings the subsidiary cards in with it, so the cards arrive as one combined feed. StatementClear works from the statements HSBC already gives you in PDF, CSV or Excel: upload the missing period, map the columns once, and dedupe checks every line against what has already posted, so covering a gap never double-counts the overlap.

The manual way, every month

Log in and export a statement (and hope the format didn't change)
Reformat columns, dates and signs until Xero's importer accepts it
Upload the CSV into the right account and pray nothing doubled up
Eyeball the balance, fix what broke, repeat next month

And after all that, it still isn't a feed - it's a one-off import you'll redo next month.

The StatementClear way: a real feed

Upload the statement and it posts into Xero as a live bank feed through Xero's Bank Feeds API - deduped, balance-checked and ready to reconcile. Not another file to import. Converters hand you a CSV; this arrives in Xero the way a bank feed does.

Step 1
Connect Xero
Link your org and pick the account that has no feed.
Step 2
Upload your HSBC statement
PDF, CSV or Excel - whatever you can export. Map the columns once and we remember the mapping.
Step 3
We check it first
Duplicates are skipped, the running balance is verified, and sign errors are caught before anything posts.
Step 4
It lands as a feed
Clean lines arrive in Xero through the Bank Feeds API, ready to reconcile.

Questions about HSBC and Xero

Related accounts

Stop importing HSBC statements. Start feeding them.

Tell us how your HSBC setup is structured and we'll get you connected.