Settings and activity
7 results found
-
26 votes
Aaron Angel supported this idea ·
An error occurred while saving the comment -
3 votes
-
2,452 votes
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
An error occurred while saving the comment "Instead of Xero building a feed for each individual bank – a process that could take months per bank – financial institutions will be able to build to Xero’s API as quickly as in a few days."
I don't know why Xero thinks banks are going to cater to Xero users with custom applications; they aren't. Banks are looking for ease of maintenance and broad appeal. Maintaining code to integrate with multiple niche third-party products serves neither of those purposes.
Most importantly, Xero should ditch Yodlee. Xero talks about security in updates to this suggestion, but what the security of giving your banking password to a third-party? Yodlee is a web-scrapper, and their product is brittle. I have lost count of the number of times their product has broken. I have also lost count of the number of times their developers, completely oblivious to the fact that humans need sleep, have twiddled around with my account, triggering MFA calls back to back to back in the middle of the night. They've even persisted after I changed my password to the point that they locked me out of my banking account. Their product still periodically breaks. Why does Xero still do business with such a company?
Xero would do better to join some open banking efforts and support existing work being done in this area. Telling users banks can "build to Xero" is like saying water can flow upward. Sure, it could happen. Will it solve the present problem? No.
An error occurred while saving the comment I am glad to see this is planned again. I would love to be able to integrate this better with Stripe (we have multiple Stripe accounts for various parts of our operations), as well as cash management.
An error occurred while saving the comment Despite more votes, you have downgraded this from "planned" to "under review." What exactly is there to review? You've had years to take care of this. It has been requested for years. Your team is really slacking, here. Do you need some help writing this? It can't be that difficult.
-
71 votes
An error occurred while saving the comment Now that Xero is pushing its new reports and planning to retire the old reports in July, this is even more important. Despite deprecating their older reports, Xero has yet to provide an actual transition plan for developers who need reports through the API. Updating the API to allow following the layout of the new reports is an interesting idea, and I added some of my votes to it. If you're interested, I also submitted an idea for Xero to create a real transition plan for developers, since they have none at present.
-
107 votes
-
22 votes
-
133 votes
This would be very useful to automate user provisioning. For example, I would like to automatically create users in Xero that can submit expense claims when a user is created in G Suite with a specific attribute or in a specific organizational unit.