コンテンツへスキップ
ブログに戻る
Slovakia公開日 2026年10月6日10 分で読めます

Slovakia 2027: Act 385/2025, the Digital Postman and what the mandate actually asks

Slovakia’s B2B e-invoicing mandate starts 1 January 2027 under Act 385/2025 Z. z. The five-corner Peppol model, the Digital Postman, EN 16931 formats, penalties up to €100,000 and how to prepare.

Slovakia is one of the fastest-moving mandates in Europe, and one of the least written about in English. The law was adopted on 19 December 2025. The voluntary phase is running through 2026. From 1 January 2027, a PDF sent by email is not a valid invoice for in-scope domestic transactions.

That is a short runway, and the model Slovakia chose is not the one most of its neighbours picked.

The law

Act No. 385/2025 Z. z. amends the VAT Act, the Tax Code and the Act on Guaranteed Electronic Invoicing. It was approved by the National Council on 9 December 2025 and published on 19 December. It is explicitly framed as the national implementation of the EU’s ViDA package (Directive (EU) 2025/516) — which matters, because it means the Slovak design was drawn from the direction of European travel rather than from an earlier national fraud-control system.

The Financial Directorate of the Slovak Republic (Finančné riaditeľstvo SR) is the designated national Peppol Authority.

The timeline

  • 2019 onwards — B2G through the national IS EFA platform.
  • 2026 — voluntary phase. Digital Postman providers are accredited, businesses can test, and sending over Peppol is optional.
  • 1 January 2027 — mandatory. All VAT-registered Slovak businesses must issue and receive structured e-invoices for in-scope domestic B2B and B2G transactions over Peppol. Penalties apply from this date.
  • July 2028 — EU ViDA platform-economy obligations.
  • July 2030 — EU ViDA cross-border digital reporting.

The voluntary phase is not a soft opening in the usual sense. It is the only window you have to test with real counterparties before the penalties switch on, and it closes at the end of this year.

Note also that draft amendments have been moving through the Slovak legislative process during 2026, including transitional relief around the buyer-side reporting obligation and a softer landing in the first months of 2027. Those are proposals, not enacted rules at the time of writing, and the 1 January 2027 go-live itself is unchanged. Do not plan around relief that has not passed.

The five-corner model and the Digital Postman

Slovakia adopted a decentralised five-corner architecture: the four familiar Peppol corners — sender, sender’s access point, receiver’s access point, receiver — plus a fifth, the tax authority, receiving reporting data.

The Slovak-specific piece is the Digital Postman (digitálny poštár): an accredited service provider that acts as the intermediary between a business and the network, and between the business and the Financial Directorate. Every business needs one. You cannot simply connect to Peppol yourself and consider the obligation met, because the reporting leg to corner five runs through the accredited provider.

Two practical consequences follow.

  • Choosing a provider is a compliance decision, not a procurement convenience. Confirm accreditation status, not marketing claims.
  • Software vendors serving the Slovak market need to be connected and tested, not just “Peppol-ready”. If your ERP vendor tells you they support Peppol BIS 3.0, that is necessary and not sufficient.

Recipients are identified by DIČ, the Slovak tax identification number, under the Slovak Peppol participant addressing scheme. Cleaning that master data is a task somebody has to own before December.

Format

E-invoices must be EN 16931-compliant XML, in either UBL 2.1 or CII (D16B) syntax. Peppol BIS Billing 3.0 is the working profile; Slovak guidance also refers to a national CIUS layered on top of it, and the exact delta was still being settled in secondary legislation at the time of writing.

Two things are explicitly not acceptable: PDF and EDIFACT. That second one matters more than it looks. If you are a manufacturer or a wholesaler running EDIFACT INVOIC with your Slovak trading partners, that channel does not satisfy the mandate. You either convert or you build a parallel path — and this is the same conversation that Germany’s expiring EDI grandfathering is forcing, so if you operate in both markets, solve it once.

Read: EDIFACT to Peppol — migrating INVOIC and ORDERS to EN 16931

Scope and exclusions

  • In scope: domestic B2B and B2G transactions between VAT-registered taxable persons established in Slovakia. Every legal entity and every entrepreneur who is a taxable person must be able to receive e-invoices via Peppol.
  • Out of scope: B2C is excluded from the mandate entirely. Non-VAT payers and VAT-exempt transactions are largely outside it.
  • Prohibited: e-invoices must not be issued where the recipient is the Slovak Information Service (Slovenská informačná služba) or Military Intelligence (Vojenské spravodajstvo), or where classified information is involved. If you supply defence or security customers, this is a routing rule you have to encode, not an edge case you can ignore.

Reporting: the Tax Data Document

Alongside the invoice itself, in-scope transactions carry a reporting obligation to the Financial Directorate. This is the fifth corner, and it is where Slovakia diverges from a pure Peppol market like Belgium.

The reporting is derived from the invoice but is a separate submission with its own structure — the Tax Data Document. In practice this means the same architectural point that applies in Croatia and Romania: your system needs to represent two independent outcomes per invoice. Delivered to the customer and reported to the tax authority are different states, and they can fail independently.

If your invoice status model has two values, it is already wrong.

Penalties

From 1 January 2027, failure to report or late reporting attracts fines of up to €10,000 per infraction, rising to up to €100,000 for repeated violations.

The per-infraction structure is the point. This is not an annual cap. A systematic failure — a misconfigured output type, a whole customer segment with bad DIČ data — multiplies.

What to do between now and December

  • Confirm your Digital Postman. Accredited, contracted, and tested with at least one real counterparty. This is the long-lead item.
  • Validate your DIČ master data. Every Slovak counterparty, checked against the register, and checked for Peppol reachability. A valid DIČ that is not registered on the network is still an undeliverable invoice.
  • Handle the receive side. Every taxable person must be able to receive from 1 January 2027. Companies that thought of this as an outbound project discover in January that their accounts-payable inbox has stopped filling up.
  • Deal with EDIFACT now. If Slovak trading partners are on EDIFACT INVOIC, decide whether you convert upstream or run two channels, and tell your partners which.
  • Map your tax codes to EN 16931 VAT categories. Slovak VAT rates and exemptions need to become S, Z, E, AE, K, G or O with the right exemption reason. Your ERP does not know this; a lookup table has to be built and signed off by tax.
  • Use the voluntary phase. It exists for exactly one reason. A test transaction in November is worth more than three months of specification review.

Where MyInvoice fits

We convert whatever your ERP already exports — SAP IDoc INVOIC02, EDIFACT, CSV, Excel, legacy XML — into EN 16931-compliant UBL 2.1 or CII, validated against XSD and Schematron before it leaves. Sending and receiving run over the Peppol network through our access point partner, on the same API:

curl -X POST https://api.myinvoice.llc/v1/convert \
  -H "X-API-Key: ek_live_..." \
  -F "[email protected]" \
  -F "format=csv" \
  -F "profile=peppol-bis-3"

If you already produce Peppol BIS 3.0 for another market, Slovakia is mostly a routing and reporting problem rather than a format problem, and we would rather tell you that than sell you a new project. One thing we will not wave away is corner five: accreditation as a Digital Postman is a Slovak-specific status, so confirm it with whichever provider carries your reporting leg — ours included — before you rely on it.

Try the sandbox — send a sample invoice and get validated output back

Related reading

If Slovakia is your first reporting-model market, these three explain the ground it stands on.

Peppol BIS 3.0 and the Peppol network explained

Post-audit, clearance or Peppol — Slovakia is a hybrid, and the differences between the models are what make corner five matter.

The three models of e-invoicing

Act 385/2025 is written as ViDA implementation; the 2028 and 2030 dates come from there.

What is ViDA?

General information, not tax or legal advice. Slovak secondary legislation and guidance were still being issued at the time of writing — verify current rules with the Financial Directorate before making compliance decisions.

Read the API docs