Generate, validate, and deliver e-invoices from one API.
Europe is mandating structured e-invoicing country by country, each with its own format and network. Beliq gives you one integration for the whole lifecycle, with compliance you can verify against the exact authority ruleset. Generate and validate are live today. Managed delivery is next.
One API, the whole e-invoice lifecycle.
One integration covers generating the file, proving it against the authority rules, and delivering it over the right network. Two of the three are live today, and the third is what we build next.
Also live today: parse structured data from incoming hybrid PDFs, and convert between CII and UBL.
JSON in, compliant XML or hybrid PDF/A-3b out. Factur-X, ZUGFeRD, XRechnung, Peppol BIS 3.0, UBL and CII.
XSD, EN 16931 and the country rules in one pass. Failures come back as rule ID, XPath and a message you can act on.
Routed across certified EU networks, chosen per destination. Billed per delivered invoice.
Every format, and exactly how we check it.
We list every format we support and the strongest check we can run against each. Where the format authority publishes a rulebook, we run it, pinned by version and hash. Where none exists, we validate against the official XSD schema. The badge on each card tells you which.
Final acceptance is decided by the authority's own system at submission.
Ordinary VAT invoices in PLN. KSeF decides acceptance at submission, and Beliq does not operate KSeF submission.
Correctness you can verify, not just trust.
Pinned, checksummed sources
Beliq's compliance engine pins every Schematron, schema and codelist by version and SHA-256 from CEN, KoSIT, OpenPeppol, FNFE-MPE, FeRD, DGFiP and NEN. Drift detection runs on a pinned schedule against the authorities' own artefacts.
Validation in one call
XSD plus EN 16931 Schematron plus the country CIUS in a single round-trip. Errors return as rule ID, XPath and a human-readable message your support team can paste into a ticket.
PDF/A-3b out of the box
Factur-X PDFs are assembled as PDF/A-3b with the invoice XML embedded, and that XML is validated before the response is returned. The same call returns the structured invoice plus the PDF.
Deterministic, within reason
XML output is byte-identical for a fixed input and pinned ruleset. PDF metadata, embedded fonts and XML attachment positions are pinned per release, so audit fingerprints stay stable across deploys even when PDF bytes do not.
Signed webhooks, structured errors
Every webhook is HMAC-SHA256 signed; every error carries rule ID, XPath, the offending value and a stable error code so you can route by exception class without parsing strings.
European, on purpose
EU-resident infrastructure on Hetzner, GDPR-aligned data handling, and engineering that overlaps your auditors' working hours. No surprise transatlantic data transfers.
One integration, never locked to one network.
When it ships, Beliq routes each invoice over the right national network automatically, across certified EU networks we select per destination and keep interchangeable. You integrate once and never wire up a network yourself, and you are never locked to one provider. Billed per delivered invoice.
One integration, many certified networks, selected per destination. We pick the network and can reroute, and your integration never changes.
Today, Beliq's compliance engine builds and proves the file, and you send it through the vendor you already use.
Where Beliq stops today ↗Five callers, one signature.
Call Beliq straight over REST, from the Node, Python, MCP and CLI developer tools, or with no code from n8n, Zapier, Directus and more. Generate from a Shopware or WooCommerce store, or add an independent check to the e-invoices your accounting tool already emits. Every path speaks the same envelope and the same JSON error shape.
POST JSON. Get a wire-ready document.
REST and cURL, available today. Every other path here wraps this API, so REST gives you full flexibility to integrate Beliq into your own software. One envelope, one error shape, every endpoint.
Call Beliq from your own stack.
Typed Node and Python SDKs, an MCP server for AI agents, a CLI, and a GitHub Action, all wrapping the same API.
Drop Beliq into your workflow tool.
Drop Beliq into n8n, Zapier, Directus, Activepieces, Pipedream or Power Automate. Map your fields and ship compliant invoices without writing code.
Invoice straight from your store.
Plugins for Shopware and WooCommerce turn store orders into compliant invoices, generated and validated on the order status you pick. You keep sending and filing.
A second opinion on what your tools emit.
Validate and convert the e-invoices your accounting tool already generates, as an independent authority-pinned check. In this flow Beliq does not re-generate or send the invoice.
Run the real engine, before you write a line of code.
Generate, validate, parse and convert against the live API. Edit the request, see the real response: the file, the verdict, the parsed JSON, the converted XML.
- The live engine, not a mock
- Bot-checked and rate-limited
- Nothing you send is stored
$ curl -X POST api.beliq.eu/v1/generate \ -H "Authorization: Bearer $BELIQ_KEY" \ -d @invoice.json ✓ 200 · application/pdf x-validation pass · 0 err · 2 warn x-pdf-kind hybrid x-request-id 4f1a9c02-7b3e-4d18-9a06-2c5e8d41b7f0
Your branding on top, the validated XML inside.
Design your invoice PDF in the dashboard (logo, colours, layout), then generate by template ID. Your Factur-X or ZUGFeRD comes back as a PDF/A-3b with the structured XML embedded, validated exactly like the default output.
- Drag-and-drop designer in the dashboard, the preview is the output
- Templates are org-scoped and encrypted at rest
- Data is rendered from the validated invoice, so the layout can't contradict the XML
Not a developer? Make one compliant invoice, free.
Pick a format, fill the essentials, and generate a real validated e-invoice to download. No account, no card, no watermark.
Two things to price: the engine, and delivery.
Same engine on every plan, same EN 16931 conformance. You pay for the documents you process by volume, and for the invoices you deliver per invoice. Nothing is gated by format. Prices in EUR; annual billing saves about 20%.
The full engine, no card. Every feature the paid plans have, at the smallest volume.
Start free →For a first integration running in production at a small, steady volume.
Start Starter →For teams that have outgrown Starter but are not yet at enterprise volume.
Start Growth →For SaaS platforms running e-invoicing in production, with the throughput to match.
Start Business →For ERPs and accounting suites sending tens of thousands of documents a month.
Start Scale →For volumes above the largest plan, priced to your volume.
Contact sales- Every live format
- Validate · generate · parse · convert
- Webhooks + signed events
- Byte-stable XML · PDF/A-3b
- EU-hosted · GDPR-aligned
- Test-mode sandbox keys
Accounts and paid plans are for businesses only (entrepreneurs, Section 14 BGB), so there is no consumer right of withdrawal. The prices shown are final prices: the applicable VAT is included, and Creem as merchant of record itemizes it at checkout. The free tools on this site are open to everyone.Terms of Service · Free offerings
One integration, many certified networks, selected per destination. You never wire up a network yourself and are never locked to one provider.
Questions, answered.
The honest version. If something here is unclear, talk to the engineers who build it.
Contact Us ↗Do you deliver invoices to Peppol, KSeF or SDI?
Not yet for Peppol and SDI. Generate, validate, parse and convert are live today. Managed delivery is what we are building next: automatic routing across certified EU networks we select per destination, billed per delivered invoice. Until then, build the compliant file with Beliq's compliance engine and send it through the access point or portal you already trust. KSeF is different: Beliq does not operate KSeF submission, so Polish invoices go via your chosen intermediary. Subscribe to the newsletter below and we will tell you the moment delivery goes live.
Which formats are live right now?
XRechnung, Factur-X, ZUGFeRD, Peppol BIS 3.0 and NLCIUS are Authority-checked: run against the format authority's own rulebook, pinned by version and hash. FatturaPA, Facturae, e-SLOG and KSeF FA(3) are Schema-checked: validated against the official XSD schema since no machine-readable rulebook is published for them. All nine formats are live to generate and to validate. KSeF FA(3) generation covers ordinary VAT invoices in PLN, and Beliq does not operate KSeF submission. The five Authority-checked formats build on EN 16931. The four Schema-checked ones are national formats, and no EN 16931 rules run on them. Peppol reaches 30+ participating countries on top.
How do I integrate?
Start with the REST API and cURL, which every other path wraps. From there: typed Node and Python SDKs, a CLI, a GitHub Action, and an MCP server for AI agents; no-code connectors for n8n, Zapier, Power Automate, Activepieces, Pipedream and Directus; plugins for Shopware and WooCommerce; and an accounting and ERP path that runs an independent authority-pinned check on the e-invoices tools like sevDesk already emit. Every path speaks the same envelope and the same JSON error shape.
Can I test before I go live?
Yes. Every API key is either live or test. A test key (blq_test_…) runs the same engine, the same authority-pinned rulesets and the same validation verdict as a live key, but it never counts against your quota, never bills, and can never reach a real network. Its output is stamped as a sandbox specimen (a watermark on PDFs, a comment in the XML) so it can never pass as a production invoice. Mint one from the dashboard, build and rehearse your integration, then switch to a live key. Test keys work against generate, validate, parse and convert today.
What happens if I go over my plan's quota or rate limit?
Both are hard limits, not metered overage. When you reach your monthly document quota or your per-minute rate limit, further calls return HTTP 429 (with a Retry-After hint on the rate limit) until the window resets, so there is no surprise bill. Upgrade or downgrade any time from the dashboard.
How do validation errors come back?
As structured JSON, not prose you have to scrape. Each finding carries the rule ID (a stable code), the severity, the document location (XPath) it fired on, and a plain-language message your support team can paste into a ticket. Every response also returns an x-request-id for tracing.
How do you keep rulesets current?
Each Schematron, schema and codelist is pinned by version and SHA-256 from the authority, then re-verified on a published schedule against its source. Every change lands in the public changelog.
Where is my data processed?
In the EU only, on Hetzner infrastructure across several EU data centers, with no US subprocessors. Payloads are processed and not retained beyond what a request needs. The Trust Center has the detail.
When can I send and receive invoices, not just validate them?
Managed delivery (Peppol and national channels, not KSeF) is in active development, targeting Q4 2026, subject to certification. Today Beliq produces and checks the compliant document; transmission stays with your access point. Subscribe to the newsletter below and we will tell you the moment delivery goes live.
Do you sign a DPA? Are you GDPR-compliant?
Yes. For the invoice data you send, you are the controller and we are your processor under the Data Processing Agreement linked in the footer. Every subprocessor that touches that invoice data is EU-based with no US data transfer, and the Trust Center lists them alongside hosting, retention and provenance.
Do I need a credit card, and can I cancel any time?
No card for the free tier: 20 documents a month, no strings. On a paid plan you can upgrade, downgrade or cancel any time from the dashboard, with downgrades taking effect at the end of the billing period.
Can I use Beliq as a private individual?
Accounts and paid plans are for businesses: you register on behalf of a company or an organization, or as a self-employed professional. The free tools on this site need no account and no contract, and anyone can use them:
- Invoice generator: pick a format, fill the essentials, download a real validated e-invoice.
- Live playground: generate, validate, parse and convert against the live API in the browser.
Why not for individuals?
Selling to consumers brings its own legal regime with it: withdrawal periods, cancellation flows, different price display.
Shipping in the open.
invoicingPeriod (BG-14) takes a startDate, an endDate or both, on the invoice and on a line (BG-26). An end before the start is a 400, and so is a line period that leaves the invoice's. On an intra-community supply (VAT category K), BR-IC-11 accepts the period in place of a delivery date. vatPointDate (BT-7) is the date the VAT becomes accountable. vatPointDateCode (BT-8) names it when you do not know the date yet: 3 the invoice date, 35 the delivery date, 432 the payment date. Sending both is a 400 (BR-CO-03). Factur-X and ZUGFeRD write the invoice period and the code from BASIC WL, the line period from BASIC and the date from EN16931. FatturaPA, Facturae, KSeF and e-SLOG accept all four and do not write them.
Eight optional fields: projectReference (BT-11), contractReference (BT-12), salesOrderReference (BT-14), receivingAdviceReference (BT-15), despatchAdviceReference (BT-16), tenderReference (BT-17), invoicedObjectIdentifier (BT-18, an id with an optional schemeId) and buyerAccountingReference (BT-19). UBL requires a purchase order reference beside a sales order reference, so without an orderReference Beliq writes NA there, the value the Peppol BIS binding gives. NA does not count as one under PEPPOL-EN16931-R003. Factur-X and ZUGFeRD write BT-12, BT-16 and BT-19 from BASIC WL and the rest from EN16931. FatturaPA, Facturae, KSeF and e-SLOG accept all eight and do not write them.
Romanian CIUS-RO results now carry verificationTier reconstructed-rules and the Community-checked badge, not Authority-checked. The rules that judge your document did not change; what we claim about them did. The two XSLT files Beliq runs are the open-source phive-rules project's compilation of ANAF's CIUS-RO 1.0.9 Schematron, not ANAF's own files, and we have not yet compared them with ANAF's. ANAF also publishes no sample invoices to check them against. Verdicts, rule IDs and rulesetSha256 stay the same. The badge goes back to Authority-checked once both gaps close; the docs page How verification works explains the tiers.
Five minutes to your first compliant invoice.
Sign up, paste an invoice, and watch the engine validate it against EN 16931 and the country CIUS in one round-trip. No card. 20 free documents every month.