Peppol BIS Billing 3.0 · CEN EN16931

Peppol Validation API

Validate Peppol BIS Billing 3 invoices via a single REST endpoint. The same Schematron rules that the well-known phive reference engine uses. Built for developers integrating ERP systems with the Peppol network.

Get API key — free 200/mo View OpenAPI spec

Quick start

curl -X POST https://api.eleata.io/v1/validate?format=peppol-bis-3 \
  -H "Authorization: Bearer ela_live_..." \
  -H "Content-Type: application/xml" \
  --data-binary @invoice.xml

What we validate

We use Mustang 2.23.0 (the MIT-licensed Schematron engine by Jochen Stärk and the FNFE-MPE working group) under the hood. Mustang implements the same CEN/PEPPOL rule sets as phive. That means we validate against:

· Peppol BIS Billing 3.0 — the current published version (OpenPeppol revises the rule set roughly twice a year; we track the latest)
· Underlying CEN EN16931 schematron rules (BR-* business rules)
· Peppol-specific business rules (PEPPOL-EN16931-R* — Peppol's CIUS on top of EN16931)
· 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. Standalone reference web forms do none of that. We are the API layer.

Pricing

Free 200 validations/month for testing your integration. Paid tiers from €29/month (Builder), €89/month (Team), €299/month (Platform). See full pricing.