eliDocs
/
Format Reference

Slovenia e-SLOG 2.0

Slovenia's national e-invoice XML standard, what Beliq generates and validates against the GZS/ePOS authority XSD, and where the UJP transmission boundary sits.

e-SLOG 2.0 is Slovenia’s national e-invoice XML standard, published by GZS (Chamber of Commerce and Industry of Slovenia) and stewarded by ePOS, the Slovenian National eBusiness Centre. It is EN 16931-aligned at the semantic level but uses its own syntax: a root Invoice element in namespace urn:eslog:2.00 wrapping an M_INVOIC UN/EDIFACT segment structure. It is not EN 16931 UBL or CII and there are no BR-* Schematron rule IDs on Beliq’s validation path. e-SLOG validation is W3C XSD only, against the authority-published schema from the epos.si invoice package.

Beliq targets the e-SLOG 2.0 invoice package (August 2020, the current release) and the single eracun profile. The legacy e-SLOG 1.6 is not supported.

What Beliq emits

What Beliq emits

Call POST /v1/generate with standard: "eslog" and output: "xml". e-SLOG has no hybrid PDF form, so output: "pdf" returns a visualization PDF instead — a rendering with no embedded XML, and it needs a template or pdfTemplateId. The legal artifact is the XML. The profile field defaults to eracun and can be omitted. No Slovenia-specific input fields are required: the builder maps the generic Beliq invoice onto the M_INVOIC segment structure (the invoice.slovenia namespace exists and is intentionally empty today).

Credit notes are supported. documentType: "creditnote" emits document type code 381 in the S_BGM segment (D_1001); invoices emit 380. Both use the same M_INVOIC message shape, as sanctioned by the GZS specification.

Validation pipeline

Validation pipeline

For e-SLOG, the validation chain is XSD-only. There is no EN 16931 Schematron layer:

Input -> e-SLOG 2.0 XSD (eSLOG20_INVOIC_v200.xsd + xmldsig-core-schema.xsd) -> Result

Structural failures surface in the API response with ruleId: "XSD". Responses carry e-SLOG-specific metadata fields (sloveniaEslogXsdBundle, sloveniaEslogRuntimeVersion) instead of schematronVersion, and report profileDetected: "slovenia-eslog-v2-0". Use format=eslog on POST /v1/validate or rely on auto-detect (the engine matches the urn:eslog:2.00 root namespace).

The runtime XSD bundle is e-SLOG 2.0 INVOIC XSD (v200; GZS/ePOS invoice package 08-2020), pinned as 2.0-08-2020 in the engine and listed on the validation artifacts page.

Verification

Verification

e-SLOG is Schema-checked: Beliq validates against the GZS/ePOS official XSD bundle. GZS/ePOS publish no machine-readable business rules for e-SLOG (validation is offered upstream only as web tools), so no Schematron layer exists and EN 16931 business rules are not enforced on the e-SLOG syntax. XSD structural validation is the highest check any client-side tool can run for this format.

Coverage details: golden round-trip paths (generate → XSD validate) for both invoice and credit note, plus the two authority sample invoices from the official package as positive fixtures.

What Beliq does NOT do

What Beliq does NOT do

  • UJP B2G submission (UJPnet portal flows). Not offered; BYOC via your chosen intermediary.
  • ZIERDED e-route provider services. The mandate’s official provider list is due by October 2027; Beliq is not an e-route provider.
  • Document signing (XML-DSig). ds:Signature is optional in the authority XSD and Beliq emits none; your intermediary signs before transmission where required.
  • e-SLOG 1.6 (legacy). Detection targets the urn:eslog:2.00 namespace only.
  • Other e-SLOG 2.0 document types (order, order response, despatch advice, reminder). Beliq ships the eInvoice message only.
Related