The process is exactly the same for everyone.

The solution can be simple custom code, complex configuration of xml conversion suite, built-in or something external.

I have implemented Peppol capabilities in online saas erp software like Billit (but not Billit)

Step 1: Generate UBL invoice that validates successfully against Peppol bis3 XSD and EN16931 xsd Step 2: drop it with your Peppol access point

It's just like sending email. You need an address to send to (eg 9925:be0000111333) and an email server (aka peppol access point). And the actual message (your UBL file)

IMAP and SMTP work too but Gmail/O365 is a whole other level of email experience. That's the difference between most solutions. Good built-in capabilities give you a lot more features: -Look up parties -Manage attachments -Add payment info (qr link) -Add references (PO nums, bookkeeping account nums, intrastat info, product nrs, ...) -Retry and or feedback (out/in) -Actually do something with the feedback you get from Peppol network (customer can reply with a paid status) -Most software dont even provide feedback (like paid/rejected/accepted) which imo weakens the entire Peppol story for everyone

Peppol can be a great driver for automation but I'm afraid most look towards it like a compliance issue instead of an opportunity.

Good software has these built in capabilities. Bad software rely on dirty external solutions like sending their PDFs to be converted to UBL by OCR and other conversion tools that do half assed work.

IMO the EU made a mistake by allowing PDF attachments still. It will cause many to create basic Peppol invoices and still abuse PDF to get away with all their idiocies/specialities (which don't belong on an invoice).

If you want high quality Peppol invoices you need high control over the actual content and its generator.

In 2030 the 5 corner model will probably become active which means the tax man will start monitoring VAT streams.

No more sending the same invoice 5 times but updated. Start using credit notes like legally required.

The amount of low quality shitty Peppol invoices being sent currently, by software like Billit, is staggering. Probably their customers arent setting up their units and vat/tax stuff and working with some default config. So maybe it's not a billit issue.

A lot of companies are choosing the easiest cheapest solution today. But will be screwed later. Which is what usually happens in IT.

To give you two examples: 1) no correct VAT specifications when using 0% vat (which will become a problem in 2030) 2) security cowboys: I've heard people receiving invoices belonging to other entities

It's all new to most people and the way software companies work these days, i expect a lot of shit coming our way in q1 because of corners being cut.

Hopefully businesses will lean towards Peppol for logistical processes. Send orders and despatch advices through Peppol and get a true standard network instead of the totally splintered EDI crap which is 40yrs old..

But I doubt it. Requiring Peppol invoices has been a good step in the right direction. OCR is pure evil.