Settings and activity
12 results found
-
3 votes
Jonathan
supported this idea
·
-
2 votesJonathan
supported this idea
·
-
2 votesJonathan
supported this idea
·
-
2 votesJonathan
supported this idea
·
-
5 votesJonathan
supported this idea
·
-
463 votesJonathan
supported this idea
·
-
4 votesJonathan
supported this idea
·
-
8 votesJonathan
supported this idea
·
-
22 votes
We are currently developing a new Credit Note webhook and then plan to release additional webhooks
Jonathan
supported this idea
·
-
59 votesJonathan
supported this idea
·
-
997 votes
Thanks for your continued feedback and patience on this long-standing request. Our team has started to build this out, and we’re looking forward to sharing more as development and testing progresses.
This release will support ingestion of bank statement data via the Bank Feeds API for accounts where a bank feed has not been established and allow customers to automate the current manual file upload process.
As part of this work, we’ll be running a beta with a small group first (from mid June) so we can test the experience and gather feedback before broader availability. We’ll continue to post updates here as we reach key milestones.
An error occurred while saving the comment Jonathan
supported this idea
·
-
279 votes
Thank you for the continued feedback and for your patience on this long‑running request. We know that programmatic bank reconciliation and AI‑driven workflows are increasingly important to many of you, and we understand the frustration that this capability is not available via the Xero API.
After reviewing this again with our legal, risk and banking teams, we have confirmed that we will not be adding the ability to reconcile bank statement lines via the API or to expose unreconciled bank statement data via the public API.
There are a few key reasons for this decision:
- Regulatory and contractual obligations on raw bank data. Unreconciled bank statement lines are “raw” banking data – unmodified information that comes directly from banks. In markets such as Australia, this data is treated as banking data under consumer data rights regimes. Sharing it on to third parties (including via an open API) would require us…
An error occurred while saving the comment Jonathan
commented
I get why you can't do this, but it sucks. It's crazy that it's 13 years later and there isn't a better solution.
For others coming here, Xero's problem is that they are dependent on getting bank data from 3rd party data sources (typically not the bank themselves, someone like Yodlee or Plaid), and those contracts disallow allowing access to the data via API. Logically, this makes sense from the 3rd party's point of view. They make their money by selling access to the data. If they allow Xero to share this data via API, then someone could set up a Xero account, set up multiple feeds (say, for their own customers), then use the API to access the data without paying the 3rd party. It seems to me there should be a way around this though - something in the Xero user contract that says you won't do this blah blah.
I actually understand why you can't allow programmatic access to data you are importing from banks (due to contracts with the likes of Yodlee/Plaid).
I do not understand why you can't provide APIs for adding our own bank statements. I could do what I want to do, export a CSV and upload it to Xero - why not just let us do it via API though.
I suppose if you do support this, you SHOULD support letting us manage these bank statement lines via API as well, but with a big red asterisk that says "WE CAN'T LET YOU READ/MODIFY/DELETE DATA WE PAY FOR". I'm fine with that for now.