Proposals & Invoices ยท Article 5.7
Peppol โ IDs, network routing, error states
Peppol is the EU's universal e-invoicing network. Submit a Peppol UBL invoice via Clozo and it routes through your Access Point, the Peppol directory, the client's Access Point, and into their accounting system โ usually within 1โ10 minutes.
Peppol is one of those acronyms that looks intimidating but is actually one of the simpler e-invoicing channels. It's a four-corner network: you, your Access Point (AP), the recipient's AP, and the recipient. The Peppol directory tells your AP where to deliver; the format is standardised; the certificates are managed centrally. Once both parties are registered, sending an invoice is a single API call.
Step by step
Register your Peppol ID
(one-time):
/settings/paymentsโ Peppol section โRegister. Approve the consent screen. Wait for the "Registered" badge (~5 minutes setup, ~1โ4 hours for directory propagation).Add the client's Peppol ID
:
/clients/{id}โ Peppol section โ enter the full Participant ID (e.g.,iso6523-actorid-upis::0007:1234567890).Generate and send
: from the Documents dropdown next to any invoice, pick "Send via Peppol". The submission fires; the Timeline records the attempt.
Monitor delivery
: within 1โ10 minutes, the Timeline updates with "Delivered to recipient AP" (success) or an error code.
Retry if needed
: from the Timeline event, click
Retry Peppol deliveryif it failed. Useful for transient issues (network blip, AP timeout). For "Recipient not found", fix the ID first.
a "Send via Peppol" action on each invoice in the Documents area. Timeline events for submission, delivery acknowledgement, and any errors. The proposal banner shows "Invoice delivered via Peppol on [date]" once successful.
Why this works this way
Peppol Participant IDs (the "ID at the corner of the network"). Every party in Peppol has a unique ID in a specific scheme. For most EU countries, the scheme iso6523-actorid-upis is used with a sub-scheme identifying the country's authority:
- 0007 โ Sweden (Organisationsnummer)
- 0088 โ Norway (Foretaksregister)
- 0192 โ Norway (Mva-register)
- 0009 โ France (SIRET)
- 0204 โ Italy (IPA)
- 0184 โ Denmark (CVR)
- 9925 โ Belgium VAT
- 9930 โ Germany VAT
- 9931 โ France VAT
- 9932 โ Spain VAT
- 9933 โ Italy VAT
- 9934 โ Netherlands VAT
- 0007:1234567890 is then a complete Participant ID for a Swedish business with org no 1234567890.
Clozo registers your Peppol ID using your VAT number under the appropriate scheme for your country (auto-selected from your profile country code). Registration is a one-time process that takes about 5 minutes and propagates across the Peppol directory in 1โ4 hours.
The four-corner model.
``
[You] [Recipient]
โ โ
[Your AP] [Recipient's AP]
โ โ
โโโโโ Peppol network โโโโโโโ
(SMP directory + certificates)
``
Your AP is the gateway your invoices leave through. The Peppol SMP (Service Metadata Publisher) maps Participant IDs to AP endpoints โ your AP queries it to find where to deliver. The client's AP is the gateway invoices enter through; from there, it's pushed into their accounting/ERP system via whatever local integration they've configured (usually plug-ins for SAP, Microsoft Dynamics, NetSuite, Visma, Exact, etc.).
Clozo uses a pre-integrated AP provider; you don't need to choose one. Your invoices leave through that AP automatically; the recipient's side is theirs to configure.
The format: UBL EN 16931. EN 16931 is the European Norm for the semantic data model of an e-invoice. UBL is one of the two syntax bindings (the other is UN/CEFACT CII; both convey the same EN 16931 model). Peppol uses the Peppol BIS Billing 3.0 profile, which is essentially EN 16931 with a few Peppol-specific constraints. Clozo emits BIS Billing 3.0 conformant XML.
The routing flow:
1. You click "Download as Peppol UBL" or auto-deliver via the Send action. 2. Clozo packages the invoice as Peppol BIS Billing 3.0 UBL. 3. Clozo's AP queries the Peppol SMP for the recipient's AP endpoint. 4. The AP submits the invoice over AS4 (an industrial-strength messaging protocol). 5. The recipient's AP receives, validates, and pushes into their accounting system. 6. The recipient's AP returns a delivery acknowledgement to your AP within ~1โ10 minutes. 7. Clozo records the acknowledgement on the proposal Timeline.
Common error states:
- Recipient not found: the Participant ID you provided isn't in the SMP directory. Either the client gave you the wrong ID, or their AP isn't registered. Verify with their accountant. - Schema invalid: the UBL document doesn't pass Peppol BIS Billing 3.0 validation. Almost always a Clozo-side issue โ contact support. - Rejected by recipient AP: the recipient's AP enforces local rules above and beyond Peppol BIS (e.g., requiring a specific PO number format). The error message will identify the rule. - Delivery timeout: rare; the recipient's AP didn't respond within 24 hours. Clozo can retry on demand.
Troubleshooting
Keep reading
Proposals & Invoices
E-invoicing formats: which one for which country, and why
EU member states are migrating to mandatory structured e-invoicing on different timelines. Clozo supports the six major formats โ Peppol UBL, Factur-X, ZUGFeRD, FacturaE, KSeF, FatturaPA โ with the right one auto-selected by the client's country.
Configuration
Peppol participant ID and e-invoicing channels: when each is required
Peppol, KSeF, FatturaPA, Factur-X, FacturaE โ the EU's e-invoicing networks each route invoices a different way. This article maps which channel applies in which country and what to fill in.
Proposals & Invoices
The final invoice (INV-) โ Schlussrechnung, facture de solde
The final invoice closes the project. It states the full work value, then explicitly references the deposit invoice and **deducts both the deposit amount and the deposit VAT**, so you don't pay tax twice. This deduction is mandated by ยง14 UStG and parallel rules across the EU.