Brought to you by

Check for known delays by clicking on your region below.
If your bank isn’t listed, or you’re not sure if you have a Direct or Yodlee feed, see our support article for more information.

New Zealand  –  Australia  –  Asia  –   South Africa  –  United Kingdom  –
United States – Rest of World

Current disruptions (September 29th, 2020)

Direct and Yodlee feeds for today appear to be imported and up to date.


If you’re wondering how often and when your bank feeds should appear in your Xero, check out the target times & frequency of Direct bank feeds for New Zealand.

 

Current disruptions (September 29th, 2020)

Macquarie (Direct Feed)
We’re still waiting to receive the bank feed files for some Macquarie customers, statements dated 25th – 28th September. We’re working with the bank to get these through to you.


If you’re wondering how often and when your bank feeds should appear in your Xero, check out the target times & frequency of Direct bank feeds for Australia.

 

Current disruptions (September 29th, 2020)

UOB Singapore (Direct Feed):
We’re still waiting to receive the bank feed files for UOB. We’re working with the bank to get these through to you as soon as possible.


If you’re wondering how often and when your bank feeds should appear in your Xero, check out the target times & frequency of Direct bank feeds for MalaysiaHong Kong, and Singapore.

 


If you’re wondering how often and when your bank feeds should appear in your Xero, check out the target times & frequency of Direct bank feeds for South Africa.

 

Current disruptions (September 29th, 2020)

HSBC (Open Banking)
We’re aware of an issue where some HSBC feeds are not importing recent transactions. Our Product team are investigating this and are working to get these through to you as soon as possible.

Santander (Open Banking)

We become aware of an issue affecting some Santander customers which was causing duplicate transactions through the bank feed in Xero.  The additional transactions that users were seeing were transactions that were incorrectly posted by the bank. While Santander work on a permanent fix, we’ve put a 24 hour delay on the feed.  This is to prevent any further duplicates for customers.  Santander are continuing to work on the issue their side and once a fix has been put in place we can look to remove this delay.


Recent disruptions:

Lloyds (Open Banking)
We were aware of an issue which is causing the Lloyds bank feed to delay or sometimes duplicate the import of transactions into Xero. We’ve worked with Lloyds to resolve this issue and transactions should now import consistently.

Clydesdale & Yorkshire Bank (Open Banking)
We were aware of an issue with connections of these Open Banking feeds. This is now resolved.

HSBC (Open Banking)
We were aware of an issue where a “Something went wrong” error message appears when renewing, connecting or refreshing this bank feed however, this is now resolved.

HSBC (Open Banking)
We’re aware of an issue where some HSBC accounts imported duplicate statement lines for the 28th and 29th of May. Any duplicates that have imported will need to be deleted. For information on how to delete statement lines see this Xero Central article. We’re sorry for any inconvenience this causes.


If you’re wondering how often and when your bank feeds should appear in your Xero, check out the target times & frequency for United Kingdom.

 

Current disruptions (September 28th, 2020)

Direct and Yodlee feeds for today appear to be imported and up to date.


If you’re wondering how often and when your bank feeds should appear in your Xero, check out the target times & frequency of Direct bank feeds for the United States.

Current disruptions (September 28th, 2020)

Open Banking:
Allied Irish Bank customers can now connect a new feed for account types the bank has made available via Open Banking.


Recent disruptions:

RBC Royal Bank (Canada) and RBC Royal Bank (Canada) – Credit Card (Yodlee Feeds)
We were aware of an issue affecting some some RBC Royal Bank (Canada) and RBC Royal Bank (Canada) – Credit Card customers. This should now be resolved. Please try manually refreshing or connecting to the feed.