PEPPOL requirements for Events and Memberships

Thanks. Take your time. Together, we should be able to come up with a solution

Regards,

Tuan

Hi Tuan, indeed we do not collect endpoint_id, endpoint_scheme for customers.

PEPPOL flow is the following:
1/ Eventbooking creates an invoice in your accounting or invoicing software.
2/ Eventbooking sends it to your Peppol Access Point (eg doccle or any other accounting software) .
3/ The Access Point routes it through the Peppol network.
4/ The recipient receives it through their Access Point into their accounting system.

Hi Tuan, In my case, we always generate invoices. If buyer is not known in the Peppol directory, the Peppol Access Point will forward the invoice to the email adress.

Oh, so something need to be figured out here:

- How can we get endpoint_id, endpoint_scheme for customers?

- In step 2, where and how Events Booking can sends invoice to? I could not find any documentation for that

Tuan

In my opinion, we do not need the endpoint_id, endpoint_scheme for customers. We only need VAT number. The Peppol Access Point will the receive the VAT and make a connection with the endpoint_id, endpoint_scheme of the customer. If no endpoint_id, endpoint_scheme is found, the Peppol Access Point wil forward invoice to customer (in most cases this means customer is not a business but a private person.
Concerning step 2: The connection should be made by API. You can find lots of usefull help on the internet for this

Oh, about step 2: I imagine that there would be different Peppol Access Point providers, each of them use different API ?

Indeed, there are different Peppol Access Point providers (eg Doccle, Yuki , ...)

they have their own api

Oh, then we have difficulty here. How could we know what Access Point is used and we would have to support many different Access Point ?

How about other customers in this forum topic? Could I have your feedback ?

Regards,

Tuan

I'm not very technical myself, but this is what I found. From this, I understand that you only need to choose one access point.

Single Infrastructure: Your application connects to a single Access Point (AP) account provided by your chosen vendor.
Unique Peppol IDs: Each of your end-users is registered with their own unique Peppol ID through your AP connection (usually based on their national business ID like a VAT number).
Multi-tenancy: The Access Point provider's system is designed to handle multiple distinct businesses (tenants) while ensuring data privacy and correct routing for each one.
Simplified Integration: This approach simplifies your integration process because you only build and maintain one connection (via API) to the provider, rather than managing separate connections for each user.
This setup allows your app to act as an intermediary, managing all of your users' Peppol document exchange through a single, secure gateway.