Peppol network: how it works, in plain terms

Access points, service metadata, document types and the four-corner model, explained without vendor language. Peppol network is best approached through four corners, one address lookup. For peppol network, the participant identifier and the document type decides the outcome. For peppol network, the participant identifier and the document type missing means rejection. For peppol network, the participant identifier and the document type wrongly mapped means wrong meaning. This guide keeps returning to one check for peppol network: check the participant lookup before sending.

The route stage for peppol network is Route. At Route, the participant identifier and the document type is what follows next. For peppol network, a Route decision cannot be repaired later. For peppol network, a Route decision cannot be repaired cheaply. Check the participant identifier and the document type for peppol network before moving on.

Follow the invoice as a record through peppol network. At Route, the record for peppol network carries the participant identifier and the document type. Answer the participant identifier and the document type for peppol network with evidence. Then the rest of networks, access points and peppol becomes easier. Then the rest of peppol network becomes easier to check.

Describe the record before the system for peppol network. Systems change, but the participant identifier and the document type for peppol network stays. Providers change, but the participant identifier and the document type for peppol network stays. Formats change, but the participant identifier and the document type for peppol network stays. For peppol network, ask what record a system produces. For peppol network, ask what record a system accepts. For peppol network, ask what status evidence it returns.

The data that matters most for peppol network is the participant identifier and the document type. That is not a slogan for peppol network. It is what the next peppol network check looks at. If the participant identifier and the document type for peppol network is missing, expect rejection. If the participant identifier and the document type for peppol network is ambiguous, expect rejection. If the participant identifier and the document type for peppol network is wrongly formatted, expect rejection.

Check the participant identifier and the document type as the receiver reads peppol network. For peppol network, screen correctness is not enough. For peppol network, file correctness is not enough. For peppol network, mapping correctness matters too. Use the mapping table for peppol network first. Use the receiver test for peppol network second. Use a sample invoice for peppol network third.

For peppol network, validation has three gates. Peppol network structure comes first. Peppol network business rules come second. Peppol network receiver rules come third. Each peppol network gate has its own failure message.

A peppol network rejection should name its rule. A peppol network rejection should name its field. A peppol network rejection should name the value sent. A peppol network rejection should name the value expected. Without those facts, a peppol network rejection is a delay. Return a peppol network rejection with that request.

Evidence for peppol network is what remains afterwards. Keep the peppol network invoice as exchanged. Keep peppol network status messages with it. Keep any peppol network correction linked to it. An auditor for peppol network asks for that set.

The common peppol network break is simple. For peppol network, check the participant lookup before sending was skipped. For peppol network, the receiver found the problem. For peppol network, the sender must now correct it. For peppol network, the sender must resend it. For peppol network, the sender must explain it.

Illustration, with round numbers only, for peppol network: A seller sends 20 invoices for peppol network. 2 fail on the participant identifier and the document type for peppol network. Checking the participant identifier and the document type first for peppol network costs minutes. A peppol network receiver rejection costs days. Sometimes a peppol network rejection costs a payment cycle. That is why peppol network repeats one check: check the participant lookup before sending.

Before acting on peppol network, verify three things. First, jurisdiction and transaction for peppol network. First, buyer and country for peppol network. Second, OpenPeppol: Peppol BIS Billing 3.0 for peppol network today. Third, the peppol network buyer requirement in writing.

A guide on peppol network organises those questions. A guide on peppol network cannot answer a specific transaction. This guide on peppol network gives general information only. This guide on peppol network is not advice for a specific invoice. For a specific invoice about peppol network, check OpenPeppol: Peppol BIS Billing 3.0. For a specific question about peppol network, ask a qualified adviser.