Peppol identifier verification
Before an account can send invoices in production, each Peppol identifier is verified against a public business registry. This page explains what that means, why we do it, and what to do if verification fails.
Why we verify
The Peppol network assumes senders are who they say they are. Our Integrator agreement with OpenPeppol requires us to make a reasonable effort to prevent invoices from being sent on behalf of entities unrelated to the sender. Verification is how we do that.
What we check
- That your identifier (e.g. a UK Company Registration Number) exists in the relevant public registry.
- That the legal name you declared is a close match to the registered name.
We currently verify UK identifiers against Companies House. Support for other EU registries (VIES, INSEE, KBO) is rolling out.
What happens at registration
- You add a production Peppol identifier in the dashboard, including the declared company name and the attestation checkbox.
- We begin verification immediately. Most checks complete in under a minute.
- Until verification succeeds, invoice sending is paused for that identifier.
- We email you when the outcome is resolved.
Verification states
The API returns a verificationState field on every Peppol
identifier. The dashboard surfaces a human-readable badge for each.
| API value | Dashboard badge | Meaning |
|---|---|---|
sandbox_auto | Sandbox auto-approved | Sandbox only — auto-approved without registry lookup. |
unverified | Queued… | Waiting for verification to start. |
verifying | Verifying… | Currently checking against the registry. |
verified | ✓ Verified | Matched. Invoice sending is unlocked for this identifier. |
mismatch | ⚠ Needs review | Identifier exists but the declared name doesn't match closely enough. |
not_found | ⚠ Not found | Identifier not found in the registry, or the entity is dissolved. |
api_error | Temporarily unavailable | Registry is down. The cron retries automatically every 5 minutes. |
manually_approved | ✓ Approved (reviewed) | Manually approved by our team after review. |
If verification fails
Reply to the notification email with proof of authorisation (for example your Articles of Incorporation or an extract from the public registry showing your entity), or email us at hello@getpeppr.dev. Our team typically responds within one business day.
Sandbox accounts
sandbox_auto. Platform customer Legal Entities are different: their requested
identifiers still go through the sub-tenant verification and network-registration flow, so
fake or unsupported numbers can fail even in sandbox.
Privacy and legal basis
We process verification data under UK GDPR Article 6(1)(f) (legitimate interest — fraud prevention) and Article 6(1)(c) (compliance with our OpenPeppol Integrator obligations). See our Privacy Policy and Terms of Service §6 for full details.