PinnedAlex Olsson·Feb 16The Hidden Complexity of Peppol Discovery: A Visual Deep-DiveThe Peppol discovery process looks simple on the surface: type a company identifier, find its endpoint, send an e-invoice.A response icon2A response icon2
Alex Olsson·Jun 11Peppol From a Raspberry Pi: The Access Point Is Becoming Just Another NodeA few years ago, the phrase “Peppol Access Point” sounded like something that belonged inside a government procurement department, an enterprise integration team, or a vendor presentation full of architecture diagrams.
Alex Olsson·May 12Peppol’s Nervous System is Here — Is Your Integration Ready for MLS?Message Level Status (MLS) represents the most important architectural upgrade to Peppol since the switch from AS2 to AS4. While the change…A response icon1A response icon1
Alex Olsson·Mar 30The Future: AI Can Now Tell You Why Your Peppol Delivery FailedYour invoice was delivered. The AS4 receipt confirmed it. Your counterpart never received it. Everything was technically correct. Nothing…
Alex Olsson·Mar 23Peppol’s 4-Corner Trust Model: What Actually Enforces TrustPeppol’s architecture is built on a deceptively simple idea: participants never connect to each other directly. Instead, messages are…
Alex Olsson·Mar 9A Fully Working Peppol AS4 Sender in Node.js — In ~500 Lines of CodePeppol has a reputation for being complicated. If you look at the transport stack alone, it’s easy to see why. The Peppol transport layer…
Alex Olsson·Mar 2Peppol AS4 Under the Microscope: From TCP Handshake to Encrypted InvoiceIf you’ve ever implemented a Peppol Access Point, you’ve likely encountered a familiar frustration: the documentation explains what to…
Alex Olsson·Feb 2312 Hidden Pitfalls in Peppol Discovery: Troubleshooting checklistPeppol’s distributed architecture is elegant — until something breaks. Because discovery spans SML/SMP, certificates, and caching layers…
