eliDocs
/
Compliance

Scope

What Beliq does and where the transmission boundary sits today. Beliq generates, validates, converts, and parses e-invoices; you deliver them over the channel you choose, and managed delivery is coming next. Provider independence is the throughline.

Beliq is the platform for European e-invoicing. Its correctness engine builds a structured e-invoice, validates it against the authority’s own pinned ruleset, converts between the EN 16931 syntaxes, and parses a document back into canonical data.

Today, getting that document onto the wire is a separate step: Beliq builds and checks the file, and you transmit it over the channel you choose. Managed delivery is coming next. This page sets out where that line sits today, and the principle that holds wherever it moves: your transmission choice stays yours, and you are never locked to one network.

What Beliq does

  • Generate a valid e-invoice from your data, as XML or as a Factur-X / ZUGFeRD PDF/A-3.
  • Validate an existing invoice and return a pass or fail against the authority’s published rules, with the specific rule IDs that failed.
  • Convert across the EN 16931 family (CII, UBL, XRechnung, Peppol BIS) without dropping structured data.
  • Parse an invoice into canonical, machine-readable fields.

Every result is judged against a ruleset pinned by version to its authority. See How verification works.

What Beliq does not do today

Beliq does not put the invoice on the wire. Specifically, it is not:

  • a Peppol Access Point (it does not route documents over the Peppol network);
  • a Plateforme Agréée (PA) for the French reform;
  • an SDI submitter for Italy;
  • a KSeF submitter for Poland;
  • a government portal, an email relay, or an EDI gateway.

Beliq hands you a correct, validated file. Getting that file to your buyer or to a tax authority is the transmission step, and today that runs over the channel you choose. Managed delivery is coming next, and it will stay provider-independent: you choose the network, and Beliq never locks you to one.

Provider independence, by design

Whatever carries your invoice, that choice stays yours. That is the throughline today, and it stays the throughline once managed delivery ships.

  • Transmission is country-specific and regulated. Each mandate (France, Italy, Poland, and the Peppol network across the EU) has its own accredited channels, onboarding, and legal responsibilities, and they move on their own timelines.
  • The transmission vendor is a relationship you own. Access Points, Plateformes Agréées (PA), and portals are yours to choose. Beliq does not force your routing through us, so changing your transmission vendor never touches your compliance layer.
  • Correctness is the foundation. Pinning every ruleset to its authority and re-verifying it on a calendar is a full-time job, and it is what makes a Beliq verdict something you can prove. That is the base the rest of the platform builds on.

So Beliq works with whichever transmission vendor you trust today, and managed delivery, when it arrives, keeps that same door open across networks.

Where Beliq stops, in practice

A typical flow looks like this today:

  1. You call POST /v1/generate or POST /v1/validate.
  2. You get back the file and its verdict.
  3. You hand that file to your Access Point, Plateforme Agréée (PA), or portal for delivery.

If you want to automate that hand-off, the integrations plug Beliq into the rest of your stack. The delivery leg runs through your chosen channel. When managed delivery ships, Beliq can run that third step for you over the network you pick; until then it is yours to run.

Nothing is retained

Invoice content is processed in memory and is never persisted to disk or used to train models. Because Beliq neither transmits nor stores documents, no copy of your invoice sits in a queue after a request completes. See the Trust Center for data residency and subprocessor detail.