Supported business processes

Slovakia exchange is built on five-cornerPEPPOL, where delivery and tax reporting happen in parallel. See which flows, document types, and use cases Sovos supports.

Slovakia uses a five-corner PEPPOL architecture where invoice exchange is a single, integrated network transmission with automatic tax reporting to the Slovak FA.

Outbound invoice process flow

Seven stages take an outbound invoice from your API call to a confirmed Tax Data Document report. Most of them are handled by Sovos and the network partner.

The following steps describe a standard outbound invoice submission.

You submit an invoice in Sovos Canonical Invoice format to the Sovos API.
Sovos validates the invoice against PEPPOL BIS Billing 3.0 rules and Slovak requirements.
Sovos routes the invoice through the PEPPOLnetwork to the buyer's Access Point, using the buyer's DIČ to look up their endpoint in the SMP.
The buyer's Access Point delivers the invoice to the buyer.
Unimaze generates a TDD and reports it to the Slovak FA (Corner 5). This happens automatically.
You poll for network status notifications. You receive an MLR confirming delivery, and an eMLR confirming TDD reporting to the Slovak FA.
You acknowledge each notification to confirm receipt.

If the buyer is not registered on the Slovak PEPPOL network, the invoice can't be delivered through PEPPOL.

For inbound invoices, the process is reversed: a buyer polls for invoices that arrive from Slovak suppliers through the PEPPOL network, then acknowledges delivery.

Supported document types

Slovakia supports invoices and credit notes, identified by UNTDID 1001 codes 380 and 381. Check the local names and the reference each document type requires.

Table 1. Supported document types
Document type	UNTDID 1001 code	Local name	Description
Invoice	380	Faktúra	Standard B2B invoice. Used for domestic and cross-border transactions.
Credit note	381	Dobropis	Full or partial credit against an original invoice.

Supported use cases

The inbound and outbound scenarios Sovos supports for Slovakia, with the routing condition that applies to each.

Table 2. Supported use cases
Use case	Direction	Notes
Standard B2B domestic invoice.	Outbound	Supplier submits invoice to a Slovak buyer registered on the PEPPOL network.
Credit note against an original invoice.	Outbound	Supplier submits a credit note correcting a prior invoice. Follows the same submission flow as an invoice.
Inbound invoice from a Slovak supplier.	Inbound	Buyer polls for invoices received from Slovak suppliers through PEPPOL.
Inbound credit note from a Slovak supplier.	Inbound	Buyer polls for credit notes received from Slovak suppliers through PEPPOL.

Out of scope

The following scenarios are explicitly not supported for Slovakia:

B2C invoicing: The Slovak mandate covers B2B only.
Payment registration: Not a legal obligation in Slovakia.
Rejection registration: Not a legal obligation in Slovakia.
Product classification codes: Slovakia does not require line-item product classification codes.
B2C fiscalization: Not in scope.

e-invoicing