What do you mean? All Belgian users unite?
V2 of InvoicePlane is on its way. We can connect to any API by then.
If there is a Peppol provider that offers Api access and if they’re helpful we’ll just connect to them.
1 Like
Peppol is not accessible to the public, only through Access Points. None of them will be willing to freely open their access to Peppol to IP-users. Except if IP would become an integrator for that Access Point. But that will not be free either. I had signed up as an integretor few weeks ago. They charged 65 EUR/year for being an integrator and 10 EUR (one time off) for enabling a registered VAT number.
As Peppol is a Belgian company and the Belgian government forces Belgian entrepeneurs to use it, it’s not something you can include in IP. I noticed the Italian users created their own IP in 2019 for the same reasons. France will have their own standards as from 2026.
The only solution I see is to turn IP into a hosted app, become a Peppol Access Point (and pay 2000 EUR/year) and try to make some money to cover the costs. Apart from Belgium there are a dozen of other countries that use Peppol and it’s flavor of the UBL Invoice standard. This can work, really!
IP could then grow into a SAAS SME-solution provider, just like Odoo has. My expectation is that somewhere in 2025, at least a dozen of new competitors will join this market. IP can be one of them.
2 Likes
Hi everyone, I have some similar issue, but with spanish e-invoice that is more easy i guest , need to make a XML format file and an invoice PDF signed .
URL format:
https://www.facturae.gob.es/formato/Documents/EnglishFacturae3_0.pdf
Has anyone tried it .
Thank you
Version 2 of InvoicePlane is on its way, but let’s fiest figure out if our export of Zugferd etcetera is good enough.
1 Like
@myedgy if you want to help you can make an overview of the peppol providers (Access Points)
Figure out which ones have the best potential to take on an open source project.
Stuff like that.
If they have an Api, they’ll have more potential
hey underdog,
first of all thank you and all the contributers for this piece of golden OSS!
just landed here, cause i am also interested in this topic (and not by free will)…
may I share my idea on how the demanding user requests and the time limit for this whole e-invoicing madness could be implemented with less stress?
for example here are some providers who support manual upload.
- Qvalia (Belgium)
- Storecove (Netherlands with a branch in Germany)
- Webware24 / Webware Internet Solutions GmbH (Germany)
so, its not absolutely necessary to develop an API right from the start and lock yourself into a single provider, especially since such providers are happy to reward such initiatives later on by increasing their prices.
it would be better to initially focus on stable e-invoicing, using various CIUS (Core Invoice Usage Specification) formats, starting with EN16931 and PEPPOL BIS v3.0 (uses UBL 2.1) and perhaps v2.2. Later, expand to country-specific formats (XRechnung, FatturaPA-XML, KSeF, Artemis, ATCUD…).
B2B users can then use the services mentioned above (at the same time, thank their governments for the extra costs) and upload the invoice if their customer exists in the PEPPOL directory.
i have seen that work is also being done on the zugferd format (ZUGFeRD 2.1.1 EN16931), which is identical (automatically compatible) to the french Factur-X (Factur-X EN16931). users are currently raising concerns because it has been recognized that PDF and XML content are two different data sets, and therefore consistency is not guaranteed. since the XML content is binding, and the PDF part, which can be changed intentionally or unintentionally, cannot be trusted, the format is often questioned. only a electronic signature creates trust: QES is recommended in France, and even mandatory in Germany for invoices to public procurement agency. otherwise AES has to be the choice. this means additional costs for a QTSP or CA provider to securely use this format.
mate, thinking and writing about this is like opening pandoras box anew every time…
1 Like
Hi James,
Thank you for your message.
I’m on Discord if you want to discuss further.
Work on the e-invoicing branch can be considered “done” and we have an "rc2’ .zip fole for download at the moment.
If you want to explain what QES and QTSP is, br my guest.
O’m open to having users upload their files to their providers
1 Like
hey thank you, i will give rc2 a try and report, as soon as I can free up some time. same for discord 
QES (qualified electronic signature) is just a type of eSignature. it is subject to the eIDAS regulation and therefore probably only (but well) known in the EU. legally equivalent to a handwritten signature, it is intended to replace it on the path to digitalization. to use it you must obtain a certificate from an accredited provider (QTSP). from here on, the costs and dependencies begin again…
wiki has a quick overview, but fynk (a contract management service depending on QES) explains it very well.
1 Like