peppol.sh

Peppol e-invoicing is mandatory or fast becoming mandatory across much of Europe, and for most engineering teams it arrives as an unwelcome compliance project: learn a new XML format, get onto the network through an access point, and keep up with country-specific rules that change on their own schedule. peppol.sh compresses that into an API call — you post JSON describing the invoice, and it handles conversion into a compliant Peppol document and delivery to the recipient's access point. The appeal is entirely about scope reduction. A billing team that would otherwise spend a quarter on UBL mapping and access point onboarding can instead treat e-invoicing as one more outbound integration, with the format and network plumbing kept on the vendor's side. That is a reasonable trade for most SaaS and marketplace products where invoicing is necessary but not the differentiator. The considerations are the usual ones for compliance infrastructure: you are placing a legally significant document flow behind a third party, so delivery reliability, error visibility and long-term availability matter more than they would for a convenience API, and you should keep archived copies of what you send. Pricing is paid with no free tier, which is standard for regulated-network access. For developers who need Peppol working this month rather than next quarter, that is usually the correct build-versus-buy answer.