Which access points are supported?
Peppyrus (sending, directory, statuses, reception) and Scrada Peppol Only in beta. Local mode works without a provider for generation and checks only. Other access points need an additional connector.
Is the UBL really checked before sending?
Yes. The embedded OASIS UBL 2.1 schemas are applied first, then the EN 16931 and Peppol BIS rules implemented in the module (BR-CO-10 to 17, BR-S/E/AE/K/G/O, PEPPOL-EN16931-R003…). The ChangeLog lists the Peppol 3.0.21 and CEN 1.3.16 references used for comparison. This is test evidence, not a guarantee that every recipient will accept every document.
How is the sender’s Peppol identifier found?
From the company card: Belgian enterprise number (scheme 0208), SIRET (0009) or SIREN (0002) for France, otherwise the VAT number. You can force another value in the setup, and a third-party extrafield stores each customer’s identifier.
Can sending be automatic?
Yes, since 1.1.0. Enable the option, then the scheduled task “PeppolConnect: send queue” with a user allowed to send. Only invoices validated after activation are queued; manual sending remains available.
Does it handle the French e-invoicing reform?
No. The diagnostic warns a French company that Peppol lets it invoice Belgian and European customers but does not replace a French approved platform. See FacturXFrance and PA Transmission for France.
What happens on upgrade?
Replace the folder, then disable and re-enable the module: it creates the outbox table and the third scheduled task. Back up the database, the documents directory and the local encryption key first.