In reply to: Michal Rykiert
Well... like with everything in life (except taxes), you have a choice :). It boils down to your priorities and what makes the most sense.
When it comes to ERPs, most of them will have a KSeF connector to issue invoices. However, most of them won't have a connector to receive invoices.
WEBCON is going to provide a service to support both scenarios, although naturally we observe the highest interest on the receiving end of invoices. And yes, it's going to be a paid service, and the clients will be able to choose which scenarios (sending and receiving) they wish to support with WEBCON and they'll be charged accordingly.
The majority of companies prioritize stability and ongoing support, especially when it comes to highly government-regulated business cases. That's precisely what we're going to offer.
Can you create your own connector? Yes. Although, you need to factor in the cost of your labor and ongoing maintenance. The latter is particularly important as we already experience many changes into KSeF and many more are expected after go live.
So again, everything boils down to weighing advantages and disadvantages. After all, you can run processes in Excel, via e-mail, etc. yet you decided to use WEBCON (even if it's just the freemium version) :).
I agree that life is an art of choice :)
I do not encourage it, but I do draw attention to the pains and problems that may be overlooked.
Yes, creating and, above all, maintaining your own connector is expensive (on begining), although for companies that already have their own development team (not necessarily developing webcon) it will not be a particular challenge. REST API, etc.
As for using WEBCON as another point in communication, everyone must decide for themselves what will be more reliable in their environment and what it can rely on. Who will try harder to ensure the availability of the service supporting e-Invoices: the ERP system manufacturer (FK/Trade) or the Workflow (BPS) system manufacturer. Cost issues may also be important (I have heard about settlements based on the number of documents, their size, etc.).
Some options:
Gateway <-> WEBCON Connector Service <-> Webcon APP <-> ERP
Here I see two possible points of failure between ERP and GOV, which may block me from receiving and issuing invoices. 1 point (WEBCON APP) can be in "my scope"
vs.
Gateway <-> ERP Connector Service <-> ERP <-> WEBCON APP
Here I see 1 possible point of failure.
By the way, my personal opinion is as follows: ERP manufacturers, instead of adapting their software to the new GOV gateway standard as part of paid updates, have made themselves a permanent source of income by introducing a subscription service. Instead of adding an interface that communicates directly with the gateway and adapting as part of the ERP update, they force you to buy the service, because otherwise you won't be able (easy) to force the ERP to work with the gateway. From this perspective, in the long run, your own connector will be cheaper (the worst, of course, is the beginning before the gateway stabilizes).
PS. Freeminum is good and can be successfully used for testing and programming in LABs (a domain or two is enough :/ ). IMO, this version is completely unsuitable for production so don't believe everything you see :)