Peppol BIS 3.0.18 · CEN EN16931
Peppol Validation API
Validate Peppol BIS Billing 3 invoices via a single REST endpoint. Same Schematron rules Helger's phive uses. Built for developers integrating ERP systems with the Peppol network.
Quick start
curl -X POST https://api.eleata.io/v1/validate?format=peppol-bis-3 \ -H "Authorization: Bearer evk_live_..." \ -H "Content-Type: application/xml" \ --data-binary @invoice.xml
What we validate
We use phive 4.0.4 (the official MIT-licensed validator from Philip Helger) under the hood. That means we validate against:
- · Peppol BIS Billing 3.0.18 (current version, June 2024 release)
- · Underlying CEN EN16931 schematron rules (BR-* business rules)
- · Peppol-specific CIUS constraints (PEPPOL-EN16931-R*)
- · UBL 2.1 schema validation
- · Code list validation (currencies, country codes, unit codes, payment means)
Why API + SDK over web form
If you're integrating Peppol BIS 3 into an accounting platform, e-commerce flow, or government tender system, you need: programmatic validation, retries, batch processing, and CI/CD integration. Helger's web form does none of that. We're the API layer with the same accuracy.
Pricing
Free 100 validations/month for testing integration. Production tiers from €29/month. See full pricing.