Trusted Digital Transformation Partner

Home / E-Invoicing / Slovakia

Slovakia · 1 January 2027 · Invoicing AND reporting

E-Invoicing in Slovakia

Slovakia introduces two obligations at once from January 2027: structured B2B e-invoicing, and near real-time reporting of both the invoices you issue and the ones you receive.

Talk to us about Slovakia

In short

E-invoicing in Slovakia requires domestic B2B invoices to be issued as structured electronic documents through certified Peppol Access Points, using EN 16931 XML (UBL 2.1 or CII) over Peppol. Following final approval by the National Council on 9 December 2025, Slovakia implements mandatory B2B electronic invoicing and reporting from 1 January 2027. The mandate introduces two parallel obligations for domestic B2B transactions: structured electronic invoicing, and near real-time e-reporting to the Financial Administration. Invoices must follow EN 16931 in XML using UBL 2.1 or CII syntax and be exchanged through certified Peppol Access Points. Both issued (sales) and received (purchase) invoices must be reported no later than 15 days after issuance or receipt. A voluntary adoption phase is scheduled from May 2026. The previously planned IS EFA platform is being replaced by a new Peppol-based national solution. Whatever the local mechanism, the invoice still has to come out of your ERP correctly — and in our experience that is where projects actually succeed or fail. ROSTAN builds the integration into Oracle EBS and Fusion Receivables so compliance is generated from the invoice the business already raises.

The deadline

1 January 2027

Dates reported from published guidance. Confirm your own obligation with your tax adviser — ROSTAN implements the ERP integration and does not provide tax or legal advice.

What Slovakia requires

Following final approval by the National Council on 9 December 2025, Slovakia implements mandatory B2B electronic invoicing and reporting from 1 January 2027. The mandate introduces two parallel obligations for domestic B2B transactions: structured electronic invoicing, and near real-time e-reporting to the Financial Administration. Invoices must follow EN 16931 in XML using UBL 2.1 or CII syntax and be exchanged through certified Peppol Access Points. Both issued (sales) and received (purchase) invoices must be reported no later than 15 days after issuance or receipt. A voluntary adoption phase is scheduled from May 2026. The previously planned IS EFA platform is being replaced by a new Peppol-based national solution.

EDICOM — Mandatory e-invoicing in Slovakia 2027

What makes Slovakia different

The details that change the integration

Purchases must be reported too

This is the part that catches projects out. It is not only the invoices you issue — invoices you RECEIVE must also be reported to the Financial Administration within 15 days. That makes Accounts Payable a compliance system, not just a processing one.

15 days, not month-end

Reporting is near real-time rather than periodic. A monthly batch process will not satisfy it, and neither will a reconciliation that happens after close.

Peppol, via certified access points

Exchange runs over Peppol through certified access points, using EN 16931 XML in UBL 2.1 or CII syntax — so the invoicing half is familiar if you already operate in another Peppol country.

Use the voluntary phase

A voluntary adoption phase from May 2026 lets you test structured invoicing and reporting before the obligation bites. Organisations that use it go into January 2027 with a proven integration rather than a hopeful one.

The portal is rarely the problem

Statutory e-invoicing is the single largest workload on our own Oracle service desk. These are the causes we see behind rejections, wherever the mandate is.

Tax or product master data that does not match what the schema expects — the most common single cause.

Party identifiers (VAT numbers, registration IDs, addresses) missing or formatted for a human rather than a validator.

A payload that validates in test and fails in production because a real invoice carries a case the sample never did.

No controlled retry path — a rejected invoice is not a valid invoice, and manual re-keying does not scale.

Nobody owning reconciliation: invoices issued in the ERP but never confirmed as accepted downstream.

The receiving side left out of scope, so supplier invoices arrive in a format Accounts Payable cannot process.

FAQ