Add support for Peppol

Feature Ideas
1

I made a little survey of the Peppol service providers.
I found at least this three which are API oriented:

2 of them are using UBL as exchange format for the outgoing and incoming invoices.
And Billit has its own JSON format (from which, I guess, they convert into UBL (or any other allowed format by Peppol)) but also support SFTP. (I do not think the API is great because they recompute the taxes.)

So I think that adding support for Peppol should be done first by creating a edocument_ubl and document_incoming_ubl which support the Invoice document.

After that the connection to specific providers will be just about implemented the submission and webhook routes and authentication.
I think it will be good to have options for the service providers (as we have already for the carriers).

What do you think?

5 Likes
2

I think this is a really nice addition, but Tryton lacks the import and export of UBL documents. Import and export of UBL invoices already is a huge step forward. Sending them through Peppol is a next step and can be done in a separate module.

So the first step is to export an UBL invoice which then can be send by a selected method. On the party a selection can be made in which format and how to send the invoice. Based on those choices the right method is chosen.

3

for the record, I just learned that ALCHIMERYS SRL, expert en logiciels libres , makers of the https://www.noalyss.eu/ free software accounting solution, just got “peppol access point” certified.

Might be interresting to see how they work and if tryton could use them as AP. If I have to pay to get my infoices on/from peppol, I might as well support a free software company.

4

Alchimerys does not seem to provide an API but only tailored solution per application.
If you care about financing companies that publish free software, you may choose https://ademico-software.com/ as they are the authors of GitHub - cefedelivery/domibus: Domibus - AS4 Message Service Handler

For B2CK we choose for now Nymus for the simplicity of the API and the cost.

5

they probably have an API to integrate with Noalyss, which is the reason why they became an access point in the first place

I do care, and I do participate (in several projects, including tryton). However that was not the point here. The point is that from 2026 I’ll have to pay to send invoices, in that case I’d prefer to pay a free software company.

I’ll of course choose what tryton supports :slight_smile:

I’ll contact Nymus to get their prices, which do not seem to be publicly available on their website…

Thanks