• Lexware Alternative

Hallo, kennt irgendwer eine gute Alternative zu Lexware für die Buchhaltung, am besten auch incl. Löhne, die auch mit BUNQ funktioniert?
Ich würde gerne vollständig zu Bunq wechseln, dafür bräuchte man aber natürlich eine Software die auch vernünftig mit dem Konto funktioniert...

    Ja, davon ist leider nichts wirklich brauchbar.

      Lexware ist halt schon ziemlich genial für deutsche Unternehmer... aber die Supporten BUNQ nicht, und BUNQ will sich nicht an Lexware wenden, um das Problem zu klären...
      Also wird es am Ende einen Verlierer geben...

        @Manuel-Grey-Kiwi#129584 Ja, davon ist leider nichts wirklich brauchbar.

        When you want advise on alternatives it might be useful to share why these apps are not useful for you. 😉 Otherwise you might end up with very similar suggestions that still don't help you.

        @Manuel-Grey-Kiwi#129586 Lexware ist halt schon ziemlich genial für deutsche Unternehmer... aber die Supporten BUNQ nicht, und BUNQ will sich nicht an Lexware wenden, um das Problem zu klären...

        This does not have to do much with bunq,.. it's the third party that must integrate the API. bunq already build the API, all third parties can implement it when they want. And when they need help with that I'm sure bunq will provide technical support. But bunq cannot force another company to integrate the bunq API. Collect enough customers and raise a point at this third party in case you want to see some balls rolling, this will indicate that it's a wish among a bigger group of their users. 🙂

          7 months later

          @Sander#129587 It’s not enough to just provide a fancy API and hope that all big accounting software providers will develop an individual implementation just for the small bunq. Why should they?

          bunq needs to implement the European Standard PSD2 XS2A like every other bank does and all is fine. I hope bunq will do that asap, otherwise they exclude themselves for all businesses who have professional accounting software.

            @Stefan-Lime-Akita-3397131654#163183 Do you maybe mean the "OpenBanking" standard?

              X2SA is not a standard, and there‘s no requirement in PSD2 to follow any specific standard. Some do exist, though, so it might be nice if bunq would also have an API that adheres to one of the more established ones for easier integration, while keeping their own API which allows for more in-depth integration. However, maintaining multiple APIs might also be a risk for them from a security and cost perspective.

                I'm talking about the Payment Services Directive 2 ("PSD2"), that is, European Union Directive 2015/236.

                The PSD2 came into force on January 12, 2016, and had to be implemented within two years (that is, until January 2018). At this point, all regulated financial entities had to ensure that they comply with PSD2 and the Regulatory Technical Standards (RTS) set out by the European Banking Authority (EBA).

                PSD2 Access to Account (XS2A) is a mandatory regulatory component, under which all institutions that offer payment accounts (like bunq), must offer access to regulated third party providers (like Lexware). PSD2 X2SA had to be implemented until September 14, 2019.

                Open Banking Europe has been launched to support Payment Service Providers (PSPs) and Third Party Providers (TPPs) in meeting the Access to Account (XS2A) requirements of PSD2.

                  @Stefan-Lime-Akita-3397131654#163307 We were talking about exactly the same thing. PSD2 X2SA is not an API standard, just a regulation (that bunq complies with, btw). It only demands there to be an API open to PIS and AIS that they can use to get certain information about a user's account and create payments on behalf of the user, depending on if they're a PIS, AIS or both. But there's nothing in the PSD2 that tells a bank on how exactly the API has to be structured, only that there has to be a way to these things. In case of bunq, their API can be used by every PIS and AIS out there, and also in addition to that by other users and developers, so they exceed the PSD2 regulations by far.

                  As you stated "Open Banking Europe has been launched to support Payment Service Providers (PSPs) and Third Party Providers (TPPs) in meeting the Access to Account (XS2A) requirements of PSD2". Many banks didn't have any APIs or didn't have APIs that were powerful enough to meet the PSD2 requirements. Therefore, they were looking for solutions to do so and some of them chose to go with the Open Banking / Preta standard. Some others went with other standards (Berlin Group etc.), and some built their own APIs. In regards to meeting the requirements of PSD2, it doesn't matter which standard you adhere to or if you adhere to any standard, your API just has to allow a PIS and AIS to do their respective actions in regards to user accounts.

                  Maybe you don't like that, and I also think this isn't the best outcome, but that's what PSD2 is. So if you want bunq to adhere to a standard like Preta or Berlin Group, then sure, that's a fair request to make. (But might also have some downsides that I mentioned in my previous comment.) But somehow suggesting that bunq is not meeting PSD2 requirements with their API is pretty far-fetched and not true as far as I'm aware.

                    Write a Reply...