Validate EU invoices in 5 lines of code.
REST API on top of phive (the official MIT validator). SDKs for Node, Python, Go. GitHub Action included. No enterprise sales calls.
Free tier: 100 validations/month. No credit card. Upgrade at any time.
curl -X POST https://api.eleata.io/v1/validate?format=xrechnung-2.x \
-H "Authorization: Bearer evk_live_..." \
-H "Content-Type: application/xml" \
--data-binary @invoice.xml
# {
# "valid": true,
# "format": "xrechnung-2.x",
# "errors": [],
# "duration_ms": 142,
# "report_url": "https://peppol.eleata.io/r/vR3kP9aZxQwL"
# }Helger is great. We're the API on top.
phive is the official MIT-licensed Java validator (Philip Helger maintains it — he's on the EN16931 working group). It's the most accurate rules engine in the EU.
But it's a JSP web form from 2010. No API. No SDKs. No GitHub Action. No way to wire it into your CI.
We added all that. Same accuracy, modern DX:
- ✓ REST API + 3 SDKs (Node, Python, Go)
- ✓ GitHub Action —
uses: eleata/validate-xrechnung@v1 - ✓ Async batch + webhooks for >100 files
- ✓ Public shareable validation reports
- ✓ Stripe metered billing — pay only for what you use
- ✓ 50 anonymized test fixtures, free under CC0
Validate in CI. One line.
Add the action to your workflow. Add the badge to your README. Never ship a broken invoice again.
- uses: eleata/validate-xrechnung-action@v1
with:
files: ./invoices/**/*.xml
api-key: ${{ secrets.ELEATA_KEY }}Simple pricing. No tiers complex.
No annual contracts. No "contact sales". Stripe metered billing — pay only for what you use.
- ✓ Async batch endpoint
- ✓ Webhook callbacks
- ✓ Priority support
Overage: €0.005 per validation, billed monthly via Stripe Metered Billing.
FAQ
Why not just use Helger directly?
Helger is a JSP web form. We expose the same validator (phive 4.x) as a REST API with SDKs, GitHub Action, async batch, webhooks, and public reports. If you're integrating, that matters.
What about Ecosio / B2BRouter / Pagero?
Those are full Access Points (€€€/mo, sales calls, multi-month onboarding). We're the validator-as-an-API layer. Different product.
Is this compliant?
We use phive — the official MIT-licensed lib. Same Schematron rules CEN/PEPPOL publish. Same accuracy as Helger's web form.
Data retention?
Validation files auto-delete after 72h. Metadata kept for billing. Full DPA available.