PINT Billing EU
International · OpenPeppol's EU-aligned modelPINT (Peppol International invoice model) is OpenPeppol's framework for extending the Peppol network beyond the EU's EN 16931 rule book — each jurisdiction gets its own PINT specialization. PINT Billing EU 1.0.2 is the specialization for exchanging with EU counterparties on the same rules as Peppol BIS Billing 3.0, plus a small set of EU-alignment rules of its own.
Part of CrateAPI's format coverage — see all formats.
What it is
PINT Billing EU validates in layers: the shared EN16931-aligned rules (mostly the same BR-xx/PEPPOL-EN16931-Rxxx checks Peppol BIS already runs) plus a small jurisdiction-aligned layer specific to the EU specialization — for example ALIGNED-IBRP-004-EU, which checks the CustomizationID matches PINT-EU rather than plain Peppol BIS. CrateAPI validates against the official docs.peppol.eu artefacts, cross-checked with phive-rules-peppol-pint 4.5.3 as a second source.
Where it's mandatory
PINT isn't a national legal mandate — it's OpenPeppol's model for jurisdictions building their own Peppol specialization outside the EU's EN 16931 rule book. PINT Billing EU is the flavor used when a trading partner needs a document that also satisfies PINT-aligned rules; check docs.peppol.eu for which network members currently require it.
What we don't do. CrateAPI doesn't transmit invoices to the Peppol network — we generate and validate the PINT-EU XML; sending it runs over your own Peppol Access Point.
Try it
curl -X POST "https://api.crateapi.com/v1/generate/ubl?profile=pint" \ -H "X-API-Key: YOUR_KEY" -H "Content-Type: application/json" \ -d @invoice.json -o invoice.xml
Relevant endpoints
| Endpoint | Notes |
|---|---|
POST /v1/generate/ubl?profile=pint | EN16931-aligned + EU jurisdiction-aligned rules, on top of the shared Peppol/UBL syntax layer. |
POST /v1/validate/ubl?profile=pintfree | Free, no API key — same free-forever validation as every other profile. |
Convert and render aren't extended to this profile yet — generate and validate are live today, convert/render are next.
Samples & docs
Read the full API reference for exact parameters, or try the format with your own file in the free validator.
FAQ
How is PINT Billing EU different from plain Peppol BIS Billing 3.0?
Same EN16931-aligned rules underneath, plus a small EU jurisdiction-aligned layer — e.g. ALIGNED-IBRP-004-EU checks the CustomizationID matches the PINT-EU urn, not the plain Peppol BIS one. Most PINT-EU findings reuse the same BR-xx/PEPPOL-EN16931-Rxxx IDs you'd see on Peppol BIS.
Who actually needs PINT instead of Peppol BIS?
Trading partners in a jurisdiction running its own PINT specialization — OpenPeppol's model for extending Peppol beyond the EU's EN 16931 rule book. PINT Billing EU is the flavor for exchanges with EU counterparties on that model.
Does CrateAPI submit PINT invoices to the Peppol network?
No — we generate and validate the XML; transmission runs over your own Peppol Access Point, same as any Peppol-based profile.