Networks, access points and Peppol

The pillar guide

Networks and access points explained: how an invoice is routed - Direct exchange, providers, platforms and the Peppol network, compared by addressing, acknowledgement and responsibility.

Working guides in this topic

• Access points: choosing a provider without losing control - What an access point does, what it must not own, and the questions to ask before signing.
• Direct exchange vs network exchange - When a direct interface is simpler, when a network is safer, and what each choice costs in onboarding.
• Government platforms and portals as routes - When a government platform is the route, what it checks, and how its status messages differ from a network.
• Message status and acknowledgements across a network - Transport acknowledgement, delivery and business acceptance are three different statuses, and confusing them hides failures.
• Multi-network strategy for sellers with many buyers - One internal model, several routes, and a routing table that decides by buyer, not by habit.
• Network costs and contracts to check - What to check in a network or provider contract: scope, status, support, exit and data return.
• Network failures and retries: a safe retry rule - Idempotent resubmission, duplicate detection and the retry window, agreed before live exchange.
• Peppol ids and addressing: getting the recipient right - Participant identifiers, schemes and the service metadata lookup, and the error when an address is wrong.
• Peppol network: how it works, in plain terms - Access points, service metadata, document types and the four-corner model, explained without vendor language.
• Service metadata and capability lookup - How a sender learns what a receiver can accept, before the first invoice is sent.

All topics