Credential setup for Slovakia

Slovakia exchange requires two credentials: a PEPPOL network registration through Unimaze, and Sovos API credentials. Complete the prerequisites and setup in order.

Configure your PEPPOL network registration and Sovos API credentials to enable invoice transmission for Slovakia.

Slovakia uses the PEPPOL network for e-invoice exchange. Instead of the tax authority certificates used in clearance countries, PEPPOL registration uses a participant identifier, which is a unique network address tied to your DIČ. You need to register your business in the Slovak PEPPOL network before you can send or receive invoices.

Before you begin

Confirm the following before starting credential setup:

Your organization and companies are created in Compliance Network. See Set up account.
Your DIČ is active and verified with the Slovak FA.
Slovakia e-invoicing products are assigned to your organization (sk_Invoice__1.0, sk_Invoice_Polling_1.0), or both.

Setup sequence

Understand your participant identifier.
Register in the Slovak PEPPOL network.
Generate Sovos API credentials.
Test your configuration in UAT.

About your participant identifier

Your participant identifier is your address on the Slovak PEPPOL network, built from your DIČ and scheme 0245. See how the identifier is composed and where it is used.

Identifier type: DIČ (Daňové identifikačné číslo).
Scheme ID: 0245
Format: 0245:{DIČ}
Example: 0245:2270000997

Register with Unimaze

Before Sovos can send or receive invoices on your behalf in Slovakia, you need to complete two registration steps: one with the Slovak government, and one with Unimaze (Sovos's accredited network partner).

Register Unimaze as your software provider.

Each legal entity must go to the Slovak Financial Administration portal and register Unimaze as their software provider. This is a legal requirement. The representative of the legal entity must complete it directly.

Important:
Don't skip this step. If the Slovak FA doesn't have Unimaze registered as your provider, invoice transmission will fail regardless of how your Sovos configuration is set up.
Create your Unimaze account.

Contact the Unimaze helpdesk at helpdesk@unimaze.com. Unimaze will explain what information is required and will typically ask you to deliver it through Excel or CSV file. Each legal entity gets its own isolated account with a unique username and password.

You need to complete this process for both UAT and production environments. Each environment has separate accounts.

Note:
Sovos Professional Services handles this step on behalf of customers during implementation. If you're managing the integration yourself, contact the Unimaze helpdesk directly.

Generate Sovos API credentials

API credentials authenticate your system's calls to the Sovos API.

Log in to the Sovos Developer Portal.
Go to API Credentials.
Click Generate New Credentials.
Copy your API key and secret immediately.

You won't be able to retrieve the secret again.
Store credentials securely using an encrypted secrets manager or key vault.

Important:
Never commit API credentials to source control or include them in application code. Use environment variables or a secrets management system.

Test your configuration in UAT

Before going to production, verify your configuration in the UAT environment using the Unimaze sandbox.

Note:

Slovakia e-invoicing is available for testing in UAT environments only. Production access will be enabled in October 2026. The Unimaze sandbox for Slovakia is the only environment available for end-to-end testing at this stage.

Use the following sandbox participants to run end-to-end tests:

Table 1. Sandbox test participants
Participant	Company name	Participant identifier
Test participant 1	Danubia LogisTech s.r.o.	`0245:2270000997`
Test participant 2	Tatra Digital Solutions s.r.o.	`0245:2270001998`

Sandbox login credentials include tatradig-sbx and danubialogi-sbx. Contact your Sovosimplementation team if you need access.

Submit a test invoice from one sandbox participant to the other.

See Send invoices for the submission process.
Poll for the Message Level Response (MLR) to confirm the invoice reached the buyer's Access Point.
Poll for the Extended Message Level Response (eMLR) to confirm Tax Data Document (TDD) reporting to the Slovak FA.
Acknowledge each notification to confirm receipt.
Test at least one validation error scenario to verify your error handling.