Slovak Republic Tax Data Document — Version 1.0.0
Slovak Republic TDD Release notes

Version 1.0.0

Maintained by Peppol Slovak Republic Pilot Team

Applies to

Slovak Republic Tax Data Document

Release Date

TBD

Status

Review

What’s New in This Release

This is the initial release of the Slovak Republic Tax Data Document specification. The release includes the following components:

  • Tax Data Document BIS Documentation.

  • Semantic Model.

  • Syntax Binding.

  • Normative Codelists.

  • Tax Data Document-specific Schematron rules.

  • Referenced Schematron artefacts in use.

Overview

This release introduces the first official version of the Slovak Republic Tax Data Document Specification.

The specification defines:

  • The Semantic Model (business information requirements).

  • The Syntax Binding (technical representation).

  • BIS documentation and implementation guidance.

  • Applicable normative codelists.

  • Validation artefacts, including Schematron rules.

The objective of this release is to establish a clear and governable framework that ensures semantic consistency, validation accuracy, and implementation certainty for all stakeholders.

Data Model

  • Semantic Model:

    • A Semantic Model in Peppol is a structured, technology-independent representation of the business information, constraints, and relationships required for electronic document exchange, forming the authoritative source for syntax binding, validation rules, and conformance profiles.

      • Business Terms (what the information means).

      • Cardinality rules (how many times information may occur).

      • Data types and formats (how information is represented conceptually).

      • Business rules and constraints (conditions governing usage).

      • Relationships between business elements.

  • Syntax Binding:

    • A Syntax Binding in Peppol is the formally governed, technology-specific mapping of a Semantic Model to a concrete document syntax, defining the exact structural representation, cardinalities, data types, and validation constraints required for an implementation.

      • Technology-Specific Representation.

      • Deterministic Mapping.

      • Normative for Implementation.

      • Constrained by Peppol Governance.

Documentation

  • Peppol Model for Tax Data Document:

    • Introduction and Scope.

    • Audience and Benefits.

    • Business processes.

    • Technical details:

      • BIS Identifiers.

      • Data types.

      • XML Schemas and Namespaces.

      • Glossary.

  • Compliance:

    • Sending Compliance to TDD.

    • Receiving Compliance to TDD.

    • Enveloping Compliance.

Code Lists

  • Standard codelists:

    • UNCL5189 (Allowance reason code).

    • UNCL7161 (Charge reason code).

    • ISO3166-1:Alpha2 (Country codes).

    • ISO4217 (Currency codes).

    • UNCL2005 (Date/Time/Period code).

    • UNCL1001 (Credit note type code).

    • UNCL1001 (Invoice type code).

    • EAS (Electronic address scheme).

    • ICD (ISO 6523 ICD list).

    • UNCL7143 (Item type identification code).

    • UNCL4461 (Payment means code).

    • UNECERec20 (Unit codes).

    • VATEX (VATEX code list).

  • Slovak Republic:

    • SK-TAXCAT (Slovak Republic VAT category codes).

  • Tax Data Document:

    • TDD-RR (Tax Data Document Reporting Role).

    • TDD-DS (Tax Data Document Scope).

    • TDD-DTC (Tax Data Document Type Code).

Schematron

Schematron artefacts provide rule-based validation to ensure semantic and technical conformance.

  • CEN EN 16931:

    • The CEN EN 16931 Schematron rules define automated validation constraints aligned with the European semantic data model for electronic invoices.

    • These rules verify:

      • Compliance with mandatory business terms.

      • Cardinality constraints.

      • Code list validity.

      • Mathematical consistency (e.g. VAT calculations, totals).

    • Their purpose is to ensure legally compliant cross-border electronic invoicing within the EU.

  • Peppol EN 16931:

    • The Peppol EN 16931 Schematron rules extend the core CEN EN 16931 validation set with additional interoperability and network-specific constraints required for Peppol participants.

    • These rules enforce:

      • Additional usage restrictions.

      • Peppol-specific code list limitations.

      • Network-level business rules.

    • Their purpose is to ensure consistent semantic interpretation and interoperability across the Peppol network.

  • Tax Data Document Choreography:

    • The Tax Data Document Choreography Schematron rules validate structural and choreography-level compliance.

    • These rules ensure that:

      • The document strictly follows the defined Syntax Binding.

      • Only permitted elements and structures are used.

      • No undefined or non-conformant elements are introduced.

    • Their purpose is to guarantee technical conformance to the specified document structure.

Action Items for Implementers

Implementers SHALL perform the following actions to ensure conformance:

  • Review and understand the Semantic Model and the associated Syntax Binding before implementation.

  • Ensure that all code values strictly comply with the applicable normative codelists.

  • Validate implementations against the published validation artefacts, including:

    • XML Schema Definitions (XSD).

    • Schematron rules.

  • Develop the Tax Data Document in full compliance with the Semantic Model, Syntax Binding, and validation artefacts.

  • Notify the relevant Peppol Authority of any identified critical defects, inconsistencies, or required change requests.

Support

For support and clarification:

https://peppol.org/tools-support/service-desk/