November offer: EXTRA 30% off all courses & bundles. Use NOVEMBER30 at checkout. Ends 30 Nov.

Slovakia E-Invoicing 2027: What Changes and How to Prepare

Slovakia’s e-invoicing mandate starts on 1 January 2027. Check who must issue and receive, what changes for AP and AR, and what to test before go-live.
Nov 21 / Peter Ilas, FCCA
After 1 January 2027, your customer may be able to read the PDF you emailed. That does not make it an e-invoice. And when a supplier’s XML reaches your company, that does not mean the invoice is ready to post or pay.

That is the practical issue with Slovakia’s 2027 e-invoicing mandate. It changes how invoices enter and leave the business. I would test both directions before go-live, and make sure someone in finance can see when either one fails.

The short answer

From 1 January 2027, Slovak-established VAT payers must issue structured e-invoices for covered domestic transactions. Domestic businesses and other legal entities must be able to receive them where required, even if they are not VAT payers. A PDF alone does not meet the structured-invoice requirement.

Who has to issue and who has to receive?

Start with the transaction, not the VAT number. For the 2027 domestic phase, the main questions are: where is the supply for VAT purposes, how is the supplier registered, and in what capacity is the customer buying? Under the Slovak VAT Act, § 85o, a Slovak-established VAT payer generally issues an e-invoice for an in-scope domestic supply or related advance payment to a domestic taxable person or qualifying non-taxable legal person. That brings ordinary business-to-business sales and many supplies to public bodies into scope.
Who issues and who receives?
  • Domestic VAT payerIssue and receiveIssue for in-scope Slovak supplies. Be able to receive from covered suppliers.
  • Domestic non-VAT businessReceiveNo general issuing duty under this mandate. Be ready to receive when the supplier must issue.
  • Public body or non-profitReceive; check issuingBe ready to receive. If you are a VAT payer, check whether your sales are in scope.
  • Foreign business registered under § 5Check establishmentSlovak VAT registration alone does not bring you into the transitional rules.
For the 2027 domestic phase, check the transaction as well as the entity.
A sole trader who is not a VAT payer generally does not have to issue structured invoices under this domestic mandate. They still need to be able to receive an e-invoice when their supplier must issue one. The receiving rule also matters for municipalities and non-profits, including those that are not VAT payers. An office that handles accounting centrally should check which legal entity is actually the recipient, rather than assuming its own registration covers everyone.

Ordinary sales to consumers are outside this domestic mandate. Certain VAT-exempt supplies and qualifying simplified invoices are also excluded; check the transaction rather than declaring an entire business exempt. The Financial Administration’s 20 November 2026 FAQ also explains that foreign businesses merely registered for Slovak VAT under §5 are outside the transitional §85o rules. A Slovak establishment can change the answer. For a group, record the conclusion separately for each entity and transaction type.

The dates to plan around

Businesses can use 2026 to test voluntary exchanges with partners that are ready. 1 January 2027 is the domestic start date. 1 July 2030 is the next phase for covered intra-EU transactions under VAT in the Digital Age (ViDA). Do not put all cross-border invoices into the 2027 workstream just because the customer has an EU VAT number. Use the Financial Administration’s phase-by-phase guidance to distinguish the dates and scopes.
The dates to plan around
  1. 2026Prepare and testUse voluntary exchanges with partners that are ready.
  2. 1 January 2027Domestic startIssue and receive structured invoices where required in Slovakia.
  3. 1 July 2030Intra-EU phaseE-invoicing and digital reporting for covered intra-EU transactions under ViDA.
The 2030 cross-border phase does not move the 2027 domestic start.
Under the published 2027 rules, reporting certain invoice data ato the Financial Administration is a separate obligation from delivering the invoice. The published text includes supplier reporting and certain VAT-registered buyer reporting. Parliamentary bill 1454 proposes changes to purchase-invoice reporting and temporary relief for specified penalties. The 20 November FAQ still treats the amendment as proposed. Do not treat the proposed relief as a postponement: prepare to issue and receive on 1 January, and check the final reporting rules before configuring January workflows.

From your invoicing system to your customer

The invoice is structured XML that follows the European standard EN 16931. Your accounting system can read the invoice lines and tax fields directly. A PDF rendering can help people read the invoice, but it is not a substitute for the XML.

The standard delivery route is through a certified digitálny poštár (digital postman), Slovakia’s term for the service provider that exchanges e-invoices over Peppol. The VAT Act permits sending compliant XML another way with the recipient’s consent; that does not remove the recipient’s obligation to be able to receive through a delivery service. Keep delivery to the customer and tax reporting separate when discussing responsibilities with your provider.

For an ordinary covered supply, the Financial Administration explains that suppliers generally have 15 calendar days from supply to issue and send the invoice. A qualifying advance payment can start its own clock, and corrections and summary invoices have separate triggers. Check which date your system uses. A document generated in your ERP but still in a failed outbound queue is not evidence it was sent.

What changes for AP and AR teams?

Accounts receivable (AR) needs to know which entity and document type to send, whether the recipient can be reached, and which errors require intervention. Verify the Slovak tax identification number (DIČ) used for routing where applicable, not just the VAT number stored on the customer record. Agree with your provider what each status means, where the evidence is kept, and who handles a failed invoice before the deadline.

Accounts payable (AP) receives data, not approval. The XML still needs to be checked for duplicates, matched to the purchase order and receipt where relevant, and approved under the normal process. If a line cannot be matched, send it to an exception queue rather than silently posting it. That distinction matters whether you handle invoices manually or automate AP from receipt to payment.

Tax and accounting should decide where originals and evidence live. The VAT Act requires VAT payers to retain in-scope e-invoices for ten years from the end of the calendar year concerned. The Financial Administration says to retain the original XML. Test that finance can retrieve it and produce a readable view; do not assume your provider’s delivery log is your archive. Non-VAT recipients should check their applicable accounting retention obligations separately.
Delivered ≠ approved
  • DeliveryThe XML arrivesConfirm it reached the right entity. Keep the original XML and delivery evidence.
  • AP approvalCheck before postingMatch against the order and receipt where relevant. Route exceptions for review.
Network delivery does not replace your AP approval controls.

Eight checks before go-live

  • Confirm scope. Tax signs off a list of legal entities, typical sales and purchases, exceptions, and the route each transaction will use.
  • Ask the software vendor what works now. Have IT or the ERP owner demonstrate that your system can create, send, receive and import structured data in a test environment, including a correction. Ask for a date on anything still missing.
  • Confirm the delivery provider. Check certification on the Financial Administration’s eFaktúra hub. Agree who monitors delivery, reporting and rejected documents, and how your team can export originals and status records.
  • Clean the master data. Have AR and AP confirm legal names, tax identifiers and routing information for representative customers and suppliers. Resolve duplicates and mismatches before the first live exchange.
  • Map invoice fields and VAT codes. Test tax treatment, line quantities, prices, allowances and references. Check that every field needed for posting or matching actually reaches the receiving system.
  • Keep approval and archiving separate from delivery. Agree who clears a failed match, where the original XML is stored, and how finance retrieves it without asking the vendor to reconstruct it.
  • Run an end-to-end test. Send, receive and post a normal invoice in test. Then force a routing or validation failure. Resend through the controlled process and confirm that the buyer does not post a duplicate.
  • Name the owners before January. Put the AP, AR, tax and IT contacts on one page, with named cover for absences. Run through who acts when the send queue fails or the purchase invoice arrives without a usable reference.

A test I would run before the first live invoice

Take a fictitious Slovak supplier billing for a partial delivery. In the first test, the XML fails validation because a mandatory field is missing. AR must see the error, fix the source field, and confirm that the corrected transmission reaches the customer.

In the second test, the invoice arrives but the order reference does not match. AP should see it in an exception queue, verify the delivery and route it to the right person. It should not appear in the payment run simply because it passed network validation.

Ask for three pieces of evidence: the outbound status, the AP decision, and the original XML retrieved from the archive. If the team cannot produce one of these without chasing someone, the process is not ready.

Key takeaways

  • Confirm who must issue and who must receive for each entity and transaction type.
  • Plan for 1 January 2027. Keep proposed penalty relief and reporting changes separate from the start date.
  • Test one successful invoice and one exception from source data through posting and archive retrieval.

FAQ

Will I still be able to use PDF invoices?

A PDF alone is not a structured e-invoice for a covered supply. It can be a readable copy, and invoices outside this mandate are subject to their own rules. Where an alternative delivery route is permitted and agreed, the invoice still needs to be compliant XML.

Do I have to do anything if I am not a VAT payer?

You generally do not have to issue under the domestic mandate. If a supplier must issue a structured e-invoice to you, however, you must be able to receive it. Check that the provider account is set up for the legal entity or business that is actually buying.

What if a customer is not ready to receive my e-invoice?

Ask your provider to confirm reachability and escalate early. Where legally permitted, agree another route for the compliant XML with the recipient and retain evidence of consent and delivery. Do not assume a PDF or the customer’s silence is an acceptable fallback. Ask your tax team to confirm how the rules apply to the specific case.

Prepare the process, not just the file

If your team needs to understand both what mandates require and how structured invoice data works, start with the E-Invoicing Mandates + Formats & XML programme.
For the regulatory side on its own, see Comply with E-Invoicing Mandates Globally or browse all E-Invoicing courses.

Peter Ilas, FCCA

Founder, RSAgile | E-LITE Consulting
30 years in finance, accounting, audit and internal controls.
Builds practical AI tools for finance teams.
Created with