There are two parts to PEPPOL integration. 1. Generating invoices in the correct format and 2. Sending invoices to a PEPPOL access point receiver for final delivery to the account holder recipient. it may be useful to break this into two parts. Part 1 can be done by adding custom fields | tags to the account which are added to the invoice by an invoice plugin. Part 2 will involve creating a separate POPPOL access point sender component. This could run inside of the OSGi JVM or outside of it depending on the run time topology requirements. As the Bill Rush team run KB inside a kubernetes cluster we would prefer to run this outside of the KB JVM as an external component.

Peppol Integration or Peppol Access Point ? Supporting the e-invoicing data formats or providing real time network access into the peppol network? These are two very different capabilities. We should perhaps break this into two separate requirements.

Related: https://www.billit.be/fr-be/home/

I suggest to implement this as a plugin to get started. We can graduate it to a core module (or default bundle) down the line if/when it makes sense.

Its not really integration....but rather compliance with these standards. This will require us to decorate or extend the core invoice data model with new reference codes, fields and values.

I would suggest we think about whether this is an invoicing plugin or a new core module.

Its a global standard that most countries will be enforcing compliance with. Over the next couple of years this will become mandatory. Given this I would recommend that it should be implemented as a core module.

We can then extend it with country specific plugins that provide localisation extensions for language, default values, and other idiosyncracies.