Peppol in practice: what changes when you leave the direct connection
Peppol is a network, not a file format. Understanding the four-corner model explains most of the surprises during onboarding.
The four-corner model
Sender and receiver never talk directly. Each connects to an access point, and the two access points exchange the document over the network using a shared addressing scheme. You only integrate with your own access point.
Addressing replaces partner setup
Instead of agreeing an FTP endpoint per partner, you address a participant identifier. The service metadata publisher declares which document types that participant accepts. If the document type is not registered, delivery fails before any content validation happens.
- Participant identifiers are scheme-qualified, for example 0088 for GLN or 0204 for the German Leitweg-ID scheme.
- Document type and process identifiers must match what the receiver published.
- A successful transport does not mean a successful business acceptance.
Validation still applies
Peppol BIS Billing 3.0 is built on EN 16931, and national CIUS rules such as XRechnung apply on top. The network delivers the file; the receiving ERP still enforces the semantic rules. Validate locally before sending, because a rejection on the far side arrives asynchronously and costs days.
Try it on your own document
Upload an EDIFACT, X12 or XML file and see structure, validation findings and a plain-language explanation in one view.
Analyze a document