Be careful and always make sure that you share information only through the secure website of the Slovak public administration. A secure page always starts with https:// before the domain name of the website.
Joint authorization on the ÚPVS (Central Government Portal)
Dear integration partners and representatives of public authorities, We would like to inform you about the rules and issues relating to the use of joint authorization.
Last updated: 25 June 2026 Published: 29 March 2018
combining an endorsement of legal force and enforceability with an electronic official document through joint authorization (§ 28(3)); and
combining an attestation clause with a newly created electronic document in the process of guaranteed conversion through joint authorization.
Authorization (signature) must be linked to a specific legal act and is required whenever the relevant act, submission or attachment requires a signature. Maintaining the link between a submission and its attachments must not be based on joint authorization. Consequently, where attachments are submitted together with a submission – for example, where a power of attorney is accompanied by scanned documents – it is incorrect to authorize those attachments jointly with the power of attorney.
We would like to inform you about the functions and documents provided by NASES in connection with the rules governing the joint authorization of electronic official documents in cases involving the procedure under § 28(3), or an attestation clause relating to guaranteed conversion under § 36 of the e-Government Act, as well as electronic official documents under the former § 28(6), which was in force until 31 October 2022.Opens in a new window
1. Joint authorization functionality
The joint authorization functionality, intended for employees of public authorities, can be used in the following ways:
through integration with the Central Electronic Registry (CEP), in the case of authorization using a qualified electronic seal;
through the user interface of the slovensko.sk portal (in the so-called message composer), in the case of joint authorization using mandate certificates or a qualified electronic seal.
In the user interface of the slovensko.sk portal, this functionality is available for all electronic forms assigned to services for which the National Agency for Network and Electronic Services (NASES) has enabled this functionality on the slovensko.sk portal. For newly registered electronic forms (with a new identifier) submitted from 22 September 2018 onwards, NASES has automatically enabled this option in all cases. For older forms, a specific request must be submitted to the National Agency for Network and Electronic Services (NASES) to enable joint authorization. Instructions for the joint authorization of electronic documents by public authorities are available on the slovensko.sk portal.
Joint authorization does not require any modifications to existing electronic forms or the registration of new electronic forms. When integrating with the Central Electronic Registry, any electronic form can be jointly authorized together with other electronic documents, provided that their formats are supported.
2. Integration Manual for the Central Electronic Registry
An Integration Manual for the Central Electronic RegistryOpens in a new windowis available on the Partner Framework Portal. It contains specifications and examples relating to joint authorization in the ASiC-E XAdES format using the "DITEC_CEP_PODPISANIE_DOKUMENTOV2" service of the Central Electronic Registry. The joint authorization functionality has been available in the Central Electronic Registry since the beginning of 2017.
The Office of the Deputy Prime Minister of the Slovak Republic for Investments and Informatization prepared new endorsements of legal force and enforceability, which are published in the electronic forms module under the following identifiers:
Since October 2019, the endorsement form has also been accessible via the green "Mark Endorsement" button directly in sent electronic official messages containing electronic official documents, i.e. messages with the EGOV_DOCUMENT class (decisions). It was also added in bulk to the forms available through the "Create Notification/Request" function, which every public authority (OVM) has in its electronic mailbox (in the upper-left corner).
In accordance with the amendment to the e-Government Act, effective from 1 August 2019, public authorities can correctly create an endorsement not only through joint authorization but also by attaching the entire decision as an attachment. If a decision is attached to an electronic official message, the electronic official document must also be clearly and unambiguously identified in the endorsement itself. If the electronic official document was created through the joint authorization of a PDF document and data from an electronic form, the attachment to the endorsement of legal force must contain the entire original electronic official document. This means that the attachment must include a file containing all parts of the electronic official document (e.g. an ASiC container containing a PDF jointly authorized with the form data). Attachments that do not constitute electronic official documents must not, according to the interpretation of the Office of the Deputy Prime Minister of the Slovak Republic for Investments and Informatization, be jointly authorized with the electronic official document or the endorsement.
An electronic official document delivered as part of an electronic official message and consisting of multiple jointly authorized files, created in accordance with § 28(3) or § 60j(9) of Act No. 305/2013 Coll. (or under the former § 28(6), which was in force until 31 October 2022Opens in a new window), must be transmitted in the electronic official message within the Object element with the attribute Class="FORM".
While most electronic messages contain only one authorized file or one unsigned file in the Object element, in cases involving the procedure under § 28(3), § 36 or § 60j(9) of the Act, the Object element will contain a signature container, typically comprising two or three files.
For example, this may include data completed using an electronic form containing part of a decision, together with a PDF file containing the remaining part of the decision. Data completed using the electronic form for the endorsement of legal force and enforceability may also be added.
Messages containing joint authorization in the main message object will not be automatically rejected by the Central Government Portal (ÚPVS) after 30 September 2024. It is the responsibility of public authorities to incorporate these requirements into their own systems.
In the case of guaranteed conversion into a newly created electronic document under § 36 of the Act, jointly authorized files will typically be transmitted in the Object element with the attribute Class="ATTACHMENT".
Joint authorization of multiple electronic documents under § 28(3) or § 36 of Act No. 305/2013 Coll., as well as under the former § 28(6), which was in force until 31 October 2022, results in the creation of a single signature container, usually in ASiC format, containing the individual files and their respective authorizations.
Further information about joint authorization and its principles can also be found in the presentation on the transition to the ASiC format (page 79).
Since it is generally not possible to determine which of several signed documents in a signature container is the main document, the order in which documents are processed by the Central Government Portal is determined by the order in which the signed documents are referenced within the signature container.
Details for individual signature containers are provided in the technical documentation for the CEP and eDesk modulesOpens in a new window on the slovensko.sk portal.
In the case of joint authorization under § 28(3) and § 60j(9), it is recommended that the XML data completed using the electronic form be placed as the first document in the signature container.
However, due to limitations of the services used to create qualified electronic signatures and seals, which do not always allow the order of files to be specified after joint authorization, situations may arise in which the PDF file is stored as the first document in the ASiC container. Information systems processing ASiC containers must therefore be designed to handle such situations.
For example, if an electronic official document is created under § 27(5) as a PDF file in an ASiC signature container and an endorsement of legal force and enforceability is subsequently added, the result when using CEP services will be an ASiC container in which the PDF file is stored first, followed by the XML data of the endorsement of legal force and enforceability.