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.
Firstly, you need to have an identity card with an electronic chip. When you collect your newly issued ID, you may choose a 6-digit personal security code (BOK) which will be activated automatically.
If you wish to use your ID card to sign with a qualified electronic signature, make a request to upload qualified certificates to its electronic chip. You can obtain a security personal code and certificates for creating a qualified electronic signature free of charge at any document department of the district directorate of the police department. In the electronic world, a qualified electronic signature replaces a handwritten signature in official procedures.
You will also need an electronic card reader and the appropriate login software (eID client) installed on your computer, a package of applications for qualified electronic signatures (KEP), and a card reader driver. The software is available in the Software applications for downloadOpens in a new window.
An electronic mailbox is used for the electronic delivery of official decisions, notifications and other messages from public authorities to citizens and businesses.
Delivery of an official decision to an electronic mailbox has the same legal effect as delivery of the decision in paper form by registered mail into the recipient’s own hands.
For a public authority to deliver an official decision to your electronic mailbox, your mailbox must be activated for delivery.
To set up notifications for messages received in your electronic mailbox, log in to the mailbox, click Settings (the gear icon), and then select Notification Settings.
In the table, select the folder for which you want to configure notifications and enter the details of where the notifications should be sent. If you have already entered your contact details in your Profile, these will be filled in automatically.
a message being moved to a folder (in the advanced settings);
both of these events (in the advanced settings).
For each option, notifications can be sent through the notification module, using your preferred channel (SMS or email) selected in the “Profile” section, or to another email address of your choice.
If you choose the latter option, you must enter the email address in the list of addresses.
The supported operating systems are listed separately for the following services:
Logging in to an electronic mailbox: Windows, macOS and Linux.
Submissions to the Commercial Register of the Slovak Republic: Windows, macOS and Linux.
The General Agenda service and other services: Windows, macOS and Linux.
The eID Client application: Windows, macOS and Linux.
For these operating system versions, the Ministry of the Interior of the Slovak Republic guarantees full functionality of the eID Client application.
You can activate your electronic mailbox for delivery by clicking the Activate Mailbox button. This button is located in the upper-right corner of the mailbox, next to the mailbox owner's name.
After clicking the button, an activation request will appear. You must submit this request.
Once the request has been successfully submitted, your electronic mailbox will be activated for delivery on the date specified in the request, but no earlier than the third working day after the request has been delivered.
Important: If you specify the same date for activation as the date on which you submit the request, your mailbox will only be activated three working days later.
You can create a qualified electronic signature using a signing application. Free signing applications are available on the Central Government Portal under the Software applications for downloadOpens in a new windowsection. For MS Windows, the D.Signer/XAdES application is available as part of the D.Suite/eIDAS package. (For Mac OS X and GNU/Linux systems, the Java version of D.Signer/XAdES is automatically downloaded and launched via the D.Launcher application, which must first be installed on these systems.)
To create a qualified electronic signature, you need to have qualified certificates, which can easily be obtained through the eID Client application. For more information, see the video tutorial.Opens in a new window
In the vast majority of cases, problems with electronically signing submissions or documents can be resolved quickly and easily by restarting or updating the software or computer. For this reason, please try the following steps in chronological order:
Close and reopen the eID Application. If the problem persists,
Connect the smart card reader to a different USB port. If the problem persists,
Try using a different internet browser. If the problem persists,
Restart your computer. If the problem persists,
Install the latest version of the D.Suite/D.LauncherOpens in a new window application for qualified electronic signatures and restart your computer. If the problem persists,
To sign a submission using a qualified electronic signature when using the Trade Licensing Register's electronic services through the Single Point of Contact,Opens in a new window you must log in to the portal using the Microsoft Edge browser on the MS Windows operating system.
Attachments included in the submission can be signed using the QSign or Disig Desktop Signer applications, or via the online application at http://zep.disig.skOpens in a new window.
The services of the Single Point of Contact fall under the responsibility of the Ministry of the Interior of the Slovak Republic.
When signing a submission to the Commercial Register, save the electronic form completed on the website of the Ministry of Justice of the Slovak RepublicOpens in a new window to your computer in XML format. Then sign it with a qualified electronic signature or a multiple qualified electronic signature in XAdES format.
The output is an ASiC container (file extension: .asics, .asice, .scsor .sce).
The XAdES_ZEP EPES format is also still supported. The output is an XML file with the .zepxextension.
Signing attachments
Attachments to the submission (e.g. a memorandum of association, articles of incorporation, etc.) must be scanned in PDF format (the preferred format) or TIFF format and signed with a qualified electronic signature or a multiple qualified electronic signature in CAdES or XAdES format.
The output is an ASiC container (file extension: .asics, .asice, .scsor .sce).
The text in the documents must be legible. Documents created through guaranteed conversion are not supported.
The CMS – CAdES EPES format is also still supported. The output is a document with the .zepfile extension. The XAdES_ZEP format is also supported, with the .zepxfile extension.
If you have signed files with the .xzepextension that you need to attach to a submission to the Commercial Register, rename the file extension to .zepx.
Note:The XAdES_ZEP signature format does not prescribe a specific file extension. In practice, both .xzepand .zepxare used interchangeably. However, for submissions to the Commercial Register, the Ministry of Justice requires the .zepxextension.
Attachments can also be signed in the .xzepformat on the Ministry of Justice portal,Opens in a new window or by attaching the document and subsequently downloading it after signing it through the general agenda service.
In this case, you should also use the D.Signer/XAdES application, which is part of the D.Suite/eIDAS package, or the D.Launcher application. Both are available in the Software applications for downloadOpens in a new windowsection.
During installation, we recommend following the relevant installation guide available in the same section.
Yes. Instructional videos are available on the portal. They provide simple explanations of basic situations that may arise when using the portal, working with the electronic mailbox, or installing essential applications and software. The videos, which build on one another, can be found in the newly created section entitled Video Tutorials.Opens in a new window
Files containing electronic signatures or seals may use various file extensions. However, the file extension itself does not guarantee that a file has actually been signed.
ASiC-E signature containers typically use the extensions: .asice, .sce, .zip
ASiC-S signature containers typically use the extensions: .asics, .scs, .zip
Signature containers created under Slovak rules applicable until 30 June 2016, or thereafter by mutual agreement between all parties to the relevant communication
ZEPf signature containers typically use the extension: .zep
XAdES_ZEP signature containers and signatures typically use the extensions:
.xzep, .zepx(the extensions .xmlor .zepare sometimes used incorrectly)
Electronic documents that contain signatures as part of the document
PDF files containing PAdES signatures use the extension: .pdf
XML files containing XAdES enveloped signatures use the extension:
.xml(or another extension)
These signatures are not currently supported by the Central Electronic Registry Office.
Electronic signatures that contain the electronic documents they sign
These signatures are not currently supported by the Central Electronic Registry Office.
CAdES enveloping signatures use the extension: .p7m
XAdES enveloping signatures use the extension: .xml
Electronic signatures detached from the signed electronic documents
These signatures are not currently supported independently by the Central Electronic Registry Office. They must be included in a signature container.
CAdES detached signatures use the extension: .p7s
XAdES detached signatures use the extension: .xml
Timestamps detached from the electronic documents to which they apply
- They use the extension: .tst
Electronic documents signed or sealed within signature containers or electronic signatures may use various formats, such as .pdf, .txt, or .png. Public authorities are required to accept and create electronic document formatsOpens in a new window prescribed by Decree No. 55/2014 Coll. on standards for the information systems of public administration in the Slovak Republic.
Verification of XAdES enveloping signatures (.xml), XAdES enveloped signatures (.xml), CAdES enveloping signatures (.p7m), and standalone document timestamps (.tst) is not currently fully supported on the Central Government Portal (ÚPVS).
These formats therefore require the use of another signature verification service. Detached signatures (.p7s, .xml) can currently be processed and verified on the Central Government Portal only when included in a signature container.
Electronically signed documents are generally transmitted in specific signature or signature-container formats, which require specialised software to open.
The electronic mailboxes on the Central Government Portal (ÚPVS) allow users to download a signed electronic document in its original signed form, usually as a signature container. They also allow users to save the electronic document itself from a supported signature container.
The following functions can be used by clicking on a file in an electronic message:
Download
Download unsigned content
View
However, if the unsigned content option is used, the resulting file will not contain the signature.
Note: The D.Viewer application can also be used to view signed documents stored on a computer. D.Viewer provides basic information about the structure of signatures. Since May 2025, it has also offered informational signature verification and the visualisation of XML data completed using any electronic form published in the electronic forms module, or a historical form stored in a separate repository. Please note that these D.Viewer features are services provided by the software supplier, operated on the supplier's infrastructure and at the supplier's own expense. NASES is not responsible for the proper functioning of these services.
To view files without using the electronic mailbox functions, you can also use the following standalone applications:
The XAdES_ZEP formats (.xzep, .zepx) and ZEPf (.zep), which originated in the Slovak Republic before Regulation No. 910/2014 came into force, are not used outside Slovakia and may not be accepted by other EU Member States.
For users with more technical expertise, ASiC signature containers containing signed PDF, TXT, or PNG files can also be opened using ZIP archive software, as the ASiC format was developed using the ZIP format as its basis.
Users can either open an ASiC file directly in a ZIP archive application or temporarily rename the file extension from .asice or .asics to .zip to open it using the relevant application.
The National Agency for Network and Electronic Services (NASES) is preparing a publicly available application that will support the display of all completed electronic forms.
Until this application becomes available, the only free way to view data completed using all electronic forms published in the electronic forms module is through the electronic mailbox.
Act No. 305/2013 Coll. on e-Government, Section 23(1)Opens in a new window, sets out the rules governing the use of timestamps and valid signatures without timestamps in the exercise of public authority. When exercising public authority, it is necessary to distinguish whether the legal act requires:
Only a handwritten signature(for which official certification is not required for paper documents and, therefore, in the electronic environment, a timestamp is not necessary while the signature certificate remains valid); or
An officially certified handwritten signature, in which case a timestamp is included as part of the authorisation process. It is also recommended to attach a timestamp to a signature whenever it is necessary to prove the time at which the authorisation took place. Further information can be found in the Guidance on Section 23(1)(b) of the e-Government Act, issued by the Office of the Deputy Prime Minister of the Slovak Republic for Investments and Informatization (now the Ministry of Investments, Regional Development and Informatization).
For qualified electronic timestamps, the decisive factor is the “granted” statusshown in the trusted list Opens in a new windowfor the relevant timestamping service. Further details on the validity of timestamps can be found in Question 18.
The following conclusions can be drawn:
If the legal act does not require official certification of the signature and the signature certificate is valid, it does not matter whether the timestamp is valid or whether a timestamp is present at all.
If the legal act does not require official certification of the signature and the signature certificate is no longer valid, but the timestamp attached to the signature is valid and was created while the signature certificate was still valid, the validity of the timestamp becomes decisive.
If the legal act requires official certification of the signature and the signature certificate is no longer valid, but the timestamp attached to the signature remains valid, the timestamp is decisive, provided it was created while the signature certificate was still valid.
The National Security Authority of the Slovak Republic has issued the Supervision Scheme for Qualified Trust ServicesOpens in a new window(based on European Commission Implementing Decision (EU) No 2015/1505Opens in a new window relating to eIDAS). This scheme establishes requirements for qualified trust service providers offering the preservation of qualified electronic signatures and qualified electronic seals. Such providers must ensure that either:
A qualified electronic timestamp is added to the signature or seal; or
A separate qualified electronic timestamp is added while the previous qualified electronic timestamp is still valid. This new timestamp must cover the signature, seal, previous electronic timestamps and the documents that have been signed or sealed.
This means that the validity of a signature can be extended by applying successive timestamps, subject to the following conditions:
The first timestamp must be attached to the signature while the signature certificate is still valid.
Each subsequent timestamp must be applied to the most recent timestamp while that timestamp is still valid, and so on.
Does the electronic mailbox ensure the validity of signatures throughout the entire period during which a message is stored in the mailbox?
The electronic mailbox does not ensure the long-term validity of the authorisation mechanisms (signatures, seals and timestamps) contained in electronic messages stored in the mailbox.
If you leave messages in your electronic mailbox and they contain signatures or seals without timestamps, once the signature certificate expires, it will no longer be possible to verify those signatures or seals as valid using automated means.
If valid signatures or seals contain a qualified timestamp added while the signature certificate was still valid, they can be verified as valid for as long as the timestamping certificate remains listed in the trusted listOpens in a new window with the status “Granted”. A qualified timestamp can therefore ensure long-term validity, potentially for more than 10 years. The validity period is not predetermined and must be established through a risk analysis.
More detailed information on this subject is available, for example, in the FAQs on the following websites:
slovensko.sk (the question “How long are signatures created using certificates whose validity has been revoked valid?”)
If a signature contains a qualified timestamp added while the signature or seal was still valid, its validity may be preserved for significantly longer than the period covered by the free document storage limit in the Long-Term Preservation Module.
In the graphical interface of the electronic mailbox, users can select the “Insert record into LTP”(Vložiť záznam do MDU) function for individual electronic messages. This transfers the messages to the Long-Term Preservation Module, where a qualified timestamp is automatically added to signatures that do not already contain one, provided this is technically possible.
In the Long-Term Preservation Module, individual signatures are protected by an integrity signature throughout the storage period (one year by default). When storage ends automatically, the records are returned to the electronic mailbox in the same state in which they were transferred to the module. Signatures that did not contain a timestamp when transferred to the Long-Term Preservation Module will have a qualified timestamp added to them.
Public authorities, legal entities and natural persons conducting business who are integrated with the services of the Central Government Portal (ÚPVS) can ensure the long-term automated verifiability of signatures and seals by using commercial service providers or the ÚPVS Long-Term Preservation Module. Under the terms agreed in the integration agreement, they can also extend the storage period for records to several years.
If a qualified electronic signature was provided with a qualified electronic timestamp before the signer's qualified certificate was revoked, the signature can be validated as valid throughout the validity period of that timestamp.
The expiry date stated in the certificate of a qualified timestamp does not affect the validity of timestamps created before that date. It only restricts the service provider from creating new timestamps using the private key associated with that certificate (see, for example, Section 9.4 of technical specification ETSI TS 119 312 V1.2.1, May 2017Opens in a new window).
The date on which the service's trusted status may be revoked (for example, changed to “withdrawn”) is not predetermined. The service retains its qualified status even after the private key used to create signatures, including timestamp signatures, must no longer be used. During this period, the service provides information on the status of previously issued certificates, timestamps and other service outputs for long-term use. It must retain at least this information for 10 years after the private key has ceased to be used.
According to the position of the NBÚOpens in a new window, the need to re-timestamp data using qualified timestamps must be determined through a risk analysis. This may take into account factors such as the resilience of cryptographic algorithms and functions, risks, and information about the service provider discontinuing its validation service.
Timestamp chaining must take place at a time when the security risk is still low — that is, before the current timestamp could be weakened by a cryptographic algorithm being broken, security measures being compromised, the service provider being compromised or other risks materialising.
In electronic filing offices, signatures are validated when electronic documents are delivered or processed. At that point, a missing qualified timestamp may be added to the signature, or an external record confirming the existence of one or more signatures may be created using a qualified timestamp. Subsequent signature validation can then rely on this record.
If a valid qualified electronic signature was created without a qualified timestamp before the signer's qualified certificate was revoked, and no trusted record of the signature was created by the relevant filing office before the certificate was revoked (for example, using a qualified timestamp), automated validation of the signature's validity is no longer possible.
In such cases, the signature may still be validated manually by providing evidence that the signature existed or was created before the signer's qualified certificate was revoked. Further details on the validation procedure can be found in the NBÚ supervision scheme.Opens in a new window
Users of the MS Windows operating system are advised to delete old, invalid certificates from their systems before electronically signing documents. This helps avoid confusion when selecting a valid certificate.
For users of GNU/Linux and macOS operating systems, certificates are not stored automatically, so there is no need to remove them manually.
Under the e-Government Act, an electronic official message is considered delivered as follows:
When the electronic official message is stored in the electronic mailbox(the point at which the message becomes objectively accessible to the recipient in the mailbox), if the recipient is a public authority.
On the day immediately following the storage of the electronic official message, if the recipient is not a public authority and the message is not subject to delivery into the recipient's own hands(do vlastných rúk).
At the date, hour, minute and second indicated on the electronic delivery receipt, or upon the expiry of the storage period, whichever occurs first, even if the recipient was unaware of the delivery, if the recipient is not a public authority and the message is subject to delivery into the recipient's own hands.
The electronic delivery receipt contains information about the date and time when an official electronic message (decision) was delivered.
The information is generated automatically after successful authentication and after the message to be delivered has been saved in the electronic mailbox.
The contents of the official electronic message are then made available to the recipient in their electronic mailbox, in the “Received” folder.
However, in the event of system overload, an outage or another technical fault, the official electronic message will only be delivered once the problem has been resolved.
The legislator has also taken into account situations in which, through no fault of your own and for objective reasons (e.g. hospitalisation), you are unable to retrieve delivered official electronic documents and familiarise yourself with their contents.
For this purpose, Section 33(1)Opens in a new window of the e-Government Act establishes the legal concept of the ineffectiveness of electronic delivery.
A legal entity (hereinafter referred to as a “LE”) for which an electronic mailbox has been established is the owner of that mailbox and is entitled to manage it in accordance with the procedure laid down in the e-Government Act.
Access to and management of a legal entity's electronic mailbox may be exercised automatically by operation of law by the statutory body or a member of the statutory body of the legal entity for which the mailbox was established, or by a person who has been granted authorisation.
Full or partial authorisation to access and manage an electronic mailbox, as well as changes to such authorisation, may be granted through a paper-based application available on the slovensko.sk portal in the “FormsOpens in a new window” section, or by using the designated function directly in the electronic mailbox. Further information is available in the relevant guide.Opens in a new window
The owner of an electronic mailbox (in this case, a company) may authorise another company to manage the mailbox. This means that the other company may be granted permission to perform specific actions in the mailbox or to manage the electronic mailbox in full.
PLEASE NOTE:Apply the procedure below only if you are authorised to delegate access rights to other persons and an error message appears when you attempt to grant authorisation electronically through the electronic mailbox function. In practice, this problem has been observed when authorisation is granted through multiple levels between legal entities. Example: The statutory representative of a limited liability company grants authorisation to another limited liability company, including the right to delegate that authorisation. The second company then grants authorisation to a limited partnership whose general partner is another legal entity.
If you are authorised to access and manage a legal entity's electronic mailbox and to delegate this authorisation, log in to www.slovensko.skon behalf of the legal entity. On the portal's home page, click “General Agenda”.
Select the service provider: the National Agency for Network and Electronic Services.
In the subject line, enter: Request for Authorisation to Access and Manage an Electronic Mailbox – Electronic Submission.
In the message body, briefly describe your request. State that you are requesting authorisation to access and manage the electronic mailbox but, despite having the right to delegate authorisation to another person, you have been unable to do so electronically because an error message appears when you attempt to grant the authorisation.
Attach the completed application containing the basic details of who is granting authorisation to whom (first name, surname, personal identification number, and, where applicable, company identification number), the validity period of the authorisation (start and end dates), and the scope of the authorisation (full or partial access).
The application is available in PDF format on the slovensko.sk portal, in the “FormsOpens in a new window” section.
Sign the message using a valid qualified electronic signature (QES) belonging to the person authorised to delegate the access rights.
Send the message.
You will subsequently receive a notification in your electronic mailbox confirming that the authorisation has been delegated.
This is merely an informational result from validating a PDF file against the PDF/A-1a format using a specific validator employed by the Central Government Portal (ÚPVS). In some cases, the validator incorrectly assesses the properties of the file format. This result does not affect the validity of the authorisation.
When reviewing the signature verification results, the key question is whether the authorisation is valid. The validation result for the object displayed further down in the verification results does not affect the validity of the authorisation.
Under the applicable Decree on Standards for Information Systems of Public Administration No. 55/2014 Coll., since March 2018, public administration bodies have been required to accept signed PDF files in versions other than PDF/A-1a. They are also required to use the PDF/A-1 or PDF/A-2 format when sending and publishing signed PDF files.
Currently, object validation is performed only against the PDF/A-1a specification. The Central Government Portal (ÚPVS) does not yet support validation against PDF/A-2. In the past, public administration bodies were required to accept and produce only PDF/A-1a files when dealing with electronically authorised documents.
The IAM (Identity and Access Management) module provides user identity verification functionality and transmits identification data (identity federation) to other connected systems. The advantage of using single sign-on is that users can navigate the entire service provision environment without having to re-enter their identification data. From the user's point of view, it does not matter in which system they log in, as none of the partner systems (Service Provider Portal) will ask them to log in again.
The IAM module works on the principle of Single Sign-On (SSO), which means "single logging in" for the user. The user logs in via the login web page using an authentication method to prove their identity.
You can log in to the slovensko.sk portal using eIDAS Node. This login option is intended for foreign individuals who hold a foreign login credential issued in one of the EU countries. More information...Opens in a new window
Holders of Slovak identity cards with a chip (eID) or Slovak residence permits for foreigners with a chip can use the electronic services of the public sector on the European Commission's portal to support European citizens' initiatives and on the portals of most Member States of the European Union and the European Economic Area. By December 18, 2020, all EU Member States were required to make their electronic services available to citizens of the Slovak Republic and foreigners residing in the Slovak Republic.
PDF (Portable Document Format) technology allows you to create a document with multiple overlapping layers. A document with a PADES signature type may therefore contain text in one of the layers that you would not be able to see. We therefore recommend that you first download the PDF document and open it in a program that allows you to view layers (such as Adobe Reader) and only sign it after reviewing its entire content.