Hi Peter👋

We have an open API, which other parties can use to integrate us in their projects😊

Thus it is up to Zoho Books to integrate us.

Perhaps it's a good idea to approach them and let them know that you would be interested in this integration.

Cheers!

Thank you for letting us know!

I went ahead and removed the link for now 👍

Dat van die prijs snap ik niet helemaal, volgens mij kost de basic versie van Zoho Books al meer dan een Big Mac menu. (Zoho Books Basic is more expensive than a Big Mac menu).

To answer your question, like Xero, Zoho Books works with Yodlee for bank connections. So, Yodlee would have to make a connection with bunq. And then probably both Zoho and Xero would connect to bunq.

Till then: Zoho Books works fine with bunq csv export (comma separated). Just tested it myself.

please also xero integration

Again: Yodlee has to make a connection with the bunq api. It is not up to bunq to do this. Only thing they can do is contact Yodlee about this and ask them to make the connection.

No, you can define the csv format before you import it. You must say it has only one column, also make sure the numbers are configured correctly, choose format 1.000.000,00. You can change all these parameters in advance. Then you will see it works. When you have it right, save the formats and you are ready to go.

BTW, thanks for this topic. Sofar I like what I see with Zoho Books (and Expenses). Had it up and running, with bunq csv import in no time. The csv import was for me quite straight forward. Reminded me of the good old days, when there were no direct feeds or bank connections ;-) Like you I sometimes had to change the import file by hand. The programs back then did not have the possibility to define the csv format.

@WilDorenbos: Why does having an API mean "it's not up to bunq"? The other party has an API too, they could say the same thing.

If both parties support delegation, a third party could integrate them. For example YNAB supports OpenID, so you get these kinds of screens:

The BUNQ API only has plain text root passwords called API keys. These keys can make payments and retrieve the ID of your passport. Not something you could trust a third party with...

@Wessel: that is the standard bunq reply, so ask them, not me ;-) I am just a chartered accountant. Not ict or fintech.

Me too. Afterall they already have AMRO, ASN, ING, KNAB , Regiobank and SNS, so why not bunq?

PS I tested their direct feed with ASN and KNAB in Zoho Books, both (private accounts) did not work. ASN resulted in an error, KNAB gave the message this was no longer suported.

Hi Wessel and Wil,

We are of course more then happy to explain a bit more about this! 😊

At bunq we believe that a public API offers many more opportunities for other parties than when we would integrate other parties ourselves. With a public API everybody has the possibility to connect with a bank and with it offer features that otherwise would not have been possible. A real time overview in your software is made possible mainly because it's the bookkeeping parties themselves that are building the connection (which we can offer real time). With other banks this is not possible due to how they integrated the bookkeeping parties.

So having your bank integrating other parties offers limitations compared to a bank offering a Public API. As many other banks do not offer a public API (yet), there is no other option than waiting on the bank to integrate you. With bunq however, other parties do not have to wait for us to built the connection, but they can start right away and built it the way they like best! 😎

Examples of existing integrations are indeed bookkeeping software parties, but also car rental companies where you receive a payment request right after you rented a car, cashless card solutions for big health organisations and many more (https://together.bunq.com/topic/what-have-you-made-with-the-public-api)! All to make your overal experience more fun and easier. 😃👍This is also one of the reasons why PSD2 came into existence. If you want to know more about PSD2 and why banks will all have to offer an public API in the future, you can check out this topic: https://together.bunq.com/topic/opinion-we-shouldnt-need-psd2-but-apparently-we-do 👍

I do understand your concern when it comes to the way you connect your account to a third party. For that reason the bookkeeping parties choose to integrate our Connect feature. So no need to share your API key 🙌🔐 Offering different level API keys is also already on our wishlist: https://together.bunq.com/topic/api-key-with-scopes.

Hope that clarifies it a bit more 😊 And let us know if there are any other questions! 😃👍

Update: I had reported the ASN error to Zoho, who passed it on to Yodlee. And today I received a message it was fixed. Now I have a working direct feed with my personal ASN account in Zoho Books.

Wessel: this exactly why I am not convinced bunq should rely so heavily on their api, and let others do things with it: "The BUNQ API only has plain text root passwords called API keys. These keys can make payments and retrieve the ID of your passport. Not something you could trust a third party with..." Only big, established, trustworthy companies would do for me, but at the moment I do not see them building much for the api. But: Yodlee did try to contact me on the bunq connection ;-)