Thanks for your feedback on this long-standing issue, we hear your frustration. A team is currently in discovery mode. Your input is valuable and we’ll share updates when we have them. Appreciate your patience

We continue to see great success with our new Bank Feeds API with a pipeline over over 30 Financial Institutes currently integrating and positive feedback from customers using these bank feeds.

We’ve completed our roadmap for the next financial year and have decided to not implement a public version at this time in order to maximise opportunities in other areas of our bank feeds product, in particular PSD2 and Open Banking.

This feature request is still on our backlog and we will be keeping an eye on this forum to understand the use case for a public bank statements API going forward.

If you are a customer of a financial institute not integrated with Xero and could benefit from having statement data in Xero, encourage them to make use of our API, they can contact us here https://www.xero.com/nz/partner-programs/financialweb/contact/

We’ve now launched our new bank feeds API (https://www.xero.com/blog/2018/09/xero-opens-banks-feeds-faster-platform-growth/) that will allow financial institutes globally to build direct bank feeds that deliver statements into Xero.

The bank feeds API (https://developer.xero.com/documentation/bank-feeds-api/) is a closed API that is only available to financial institutions that have an established financial services partnership with Xero.

The first integrations that are taking advantage of this new API are leading UK fintechs Tide, Starling, TransferWise and Revolut (https://www.xero.com/blog/2018/11/uk-banking-connections-fintech-integrations/), who all have live integrations available now.

Further updates will be provided here in early 2019 regarding a publicly available API for the import of statements that leverages what we’ve built for financial institutes.

Looking to put a roadmap together for this financial year. Initially this will enable traditional bank feeds via the API but will be extended to statement upload in future.

- Update September 2016 -

We appreciate that this is a highly demanded feature but it is not on the current roadmap.

We’re looking at tackling some big features in the next 3-6 months including practice-level auth (XeroHQ API), webhooks and a new developer portal. That means an API for importing bank statement lines is unlikely to be built in the forseeable future.

Once we’ve shipped some of those higher priority features we’ll re-evaluate the status of this one.

Hi all,

I’m afraid we still don’t have anything exciting to share around bank statements, but this request is well overdue for an update.

We do ‘refresh’ the status of these requests every couple of months and, if nothing’s changed, it’s often with the same message. The aim of this isn’t to fool the community into thinking we’re actively working on something, we’re trying to tell the community that we’re actively listening to your feedback and watching these pages.

I apologise if it comes across as deceptive, but there’s only so many ways you can say “Great idea, we agree this would be awesome, but it’s not on the roadmap for the next 3-6 months.” I wish UserVoice had a status for that!

So, sorry to sound like a broken record, but even though we see the value in this feature it’s still not something we’ll be delivering in the next 3-6m months. That said, we WILL be working on the next version of the API authentication layer which will finally make more complicated endpoints like this possible.

Cheers,
Adam

Hi everyone, we know this has been a longstanding request, but a number of security and licensing issues have prevented us from providing this.

We have marked this as ‘planned’ as we still have it in our long term roadmap to provide it once we can add a more comprehensive permissions model to the API, but the honest answer in terms of timing is that this will not be available in the next 6-9 months at least.

A reminder on an article that may help some users get around this feature gap for the time being: https://community.xero.com/developer/discussion/3879525/

Hello everyone, we know this has been a longstanding request, but a number of security and licensing issues have prevented us from providing this.

We have marked this as ‘planned’ as we still have it in our long term roadmap to provide it once we can add a more comprehensive permissions model to the API, but the honest answer in terms of timing is that this will not be available in the next 6-9 months at least.

A reminder on an article that may help some users get around this feature gap for the time being: https://community.xero.com/developer/discussion/3879525/

Hello everyone, we know this has been a longstanding request, but a number of security and licensing issues have prevented us from providing this.

We have marked this as ‘planned’ as we still have it in our long term roadmap to provide it once we can add a more comprehensive permissioning model to the API, but the honest answer in terms of timing is that this will not be available in the next 6 months at least.

A reminder on an article that may help some users get around this feature gap for the time being: https://community.xero.com/developer/discussion/3879525/

We have added an update on keeping you better informed on feature requests in the future also: https://community.xero.com/developer/discussion/10480255/

Thanks for your votes everyone. As we have completed other requests this one has creeped up the list and is overdue an update.

We do agree this would be a useful feature to expose via the API. We will begin scoping this shortly and update you when development begins, but no ETA yet.

We have reviewed some of your comments and use cases below however, and have written up an article on some possible existing API options: https://community.xero.com/developer/discussion/3879525/ – note this may not apply to your situation, but hopefully useful to some.