Slovakia eKasa Receipt Requirements: 2026 Guide

Slovakia eKasa receipt requirements in 2026 are practical and specific: if your business has to record a sale through eKasa, you must record the takings without undue delay and give the buyer a compliant receipt. Under Act No. 384/2025, that receipt needs the core seller and receipt identifiers, the goods or services sold, the relevant prices and totals, and a readable QR code. If you are a VAT payer, the receipt must also show the VAT base, the VAT rate or exemption, and the VAT amount.

For day-to-day compliance, check five things early: issue the receipt whenever eKasa applies, make sure the receipt includes the mandatory identifiers and VAT data where required, use electronic delivery only with buyer consent before printing, keep paper outputs and paragons readable for five years, and prepare for the cashless-payment rule for covered sales above EUR 1 from May 1, 2026.

This guide is not a broad summary of Slovak tax law. It is a practical 2026 reference for businesses checking fiscal receipt rules at checkout, at the till, and during reconciliation.

When a sale has to be recorded through eKasa

From January 1, 2026, the practical rule is straightforward: if you are acting as a business or self-employed seller, you sell goods or provide a service, and you accept an in-scope payment at the place where the sale is made, you generally have to record that sale through eKasa without undue delay and issue an eKasa receipt. The 2026 regime broadened scope substantially, covering sales of goods and, in practice, all services unless a specific statutory exception applies. That is why edge-case activities still need to be checked against the exceptions rather than assumed either way.

For most operators, the real scope question is whether the payment creates an in-scope sale at the point of sale. If yes, eKasa is usually triggered. That includes not only the main sale amount, but also prepayments and balance payments taken at the point of sale. If, by contrast, you are paid only by bank transfer from account to account outside the point of sale, for example after sending an invoice, that payment is generally outside eKasa. If the same invoice is later settled in cash or another in-scope form at the counter, that checkout event falls back into eKasa.

Your first compliance decision is not which cash register brand to buy. The real question is whether the sale must create an eKasa record and a valid receipt. ORP, SORP, and VRP are just three ways to do that:

• ORP is the classic online cash register setup, a physical register with the required software and protected storage, typically used at a fixed checkout.
• SORP is a software online register. In practice, it is the same eKasa obligation handled through a software-based setup rather than a traditional hardware-led register.
• VRP is the tax authority's virtual cash register service, accessed through its web environment or mobile app, and is often the most relevant option for smaller, occasional, or mobile sellers.

Whichever route you use, the compliance result is the same: if the sale is in scope, the system must create the eKasa record and produce the receipt output the customer is entitled to receive.

A few edge cases are worth flagging. Occasional, temporary, or mobile selling does not automatically take you out of eKasa. If you sell at markets, seasonal stands, pop-up locations, delivery points, or customer sites and you accept in-scope payment there, that location is still treated as the place of sale for that transaction. The law also allows an eKasa setup to be used across different sales locations at different times, which matters for portable operations. Some narrow statutory exceptions still exist, so if your activity sits in a grey area, resolve that classification first, because eKasa attaches to the status of the seller as well as the way the payment is taken.

What a valid eKasa receipt must show

Under Slovakia's current eKasa rules, a receipt is valid only if it contains the mandatory fields. For finance teams checking Slovakia fiscal receipt requirements, the practical test is simple: if the original receipt handed to the buyer is missing any required field, the checkout process is not fully compliant. This checklist covers the standard sales receipt, not the special invoice-payment receipt discussed later.

Use this field-by-field check for Slovakia eKasa mandatory receipt fields:

• Seller and registration identifiers: The receipt must show the eKasa cash-register code, the seller's tax ID or VAT ID as applicable, the seller's business name, and the registered address or place of business. If the point of sale is different from that registered address, the sales location must appear too.
• Document and verification identifiers: The receipt must include the receipt identifier, the seller verification code, and the receipt number. These are core control fields, not background system data.
• QR code for verification: A readable QR code must appear on the original receipt. That code, together with the verification identifiers, allows the buyer or an inspector to check the receipt against the Financial Administration's receipt-verification service. In other words, Slovakia QR receipt requirements are part of receipt validity, not a decorative extra at the bottom of the slip.
• Date and time: The receipt must show when it was issued, down to the transaction date and time.
• Goods or service description: Each item or service must be described clearly enough to identify what was sold and distinguish it from something else. A shortened name is allowed, but a pure code or SKU on its own is not. Staff should be able to look at the receipt and understand what the customer actually bought.
• Quantity, scope, and price: The receipt must show the quantity of goods or the extent of the service, plus the item price or service price.
• VAT breakdown for VAT payers: If the seller is VAT-registered, the receipt must also show the VAT base, the VAT rate or exemption status, and the VAT amount, broken down by rate. In practice, that means the VAT detail is not optional formatting. It is part of the receipt content whenever the normal VAT rules apply.
• Rounding and total paid: The receipt must show any rounding adjustment and the total amount paid.

At the till, this means your staff must print or send one original receipt that contains all of the mandatory content above. The buyer should receive the same legal information whether the receipt is printed or delivered electronically. If your POS layout drops the seller identifiers, uses item codes nobody can interpret, omits the VAT breakdown for a VAT payer, or prints an unreadable QR code, the document is not complete.

If your team also works with other fiscal systems, Croatia's fiscal receipt fields and QR verification rules highlight the same practical point: the QR-based verification layer belongs on the receipt itself, not in a separate back-office record.

---

When electronic receipts are valid and what changed in 2026

For 2026, keep two dates separate. January 1, 2026 is when the current eKasa regime under the new receipts law took effect, so this guide reflects the live rules rather than pre-2026 practice. May 1, 2026 is a later operational date, because that is when the separate cashless-payment duty starts for covered sellers.

The rule on electronic receipts is about delivery, not about changing the receipt content. The Financial Administration of the Slovak Republic says that paper and electronic eKasa receipts are equivalent, and that a receipt may be sent or made available electronically only if the buyer agrees and requests it before printing, with no paper receipt printed instead, according to Financial Administration guidance on Slovakia's eKasa rules. In practice, Slovakia electronic receipt consent has to be built into the checkout flow before staff hit print.

Your process for electronic receipts should be straightforward: ask the buyer first, confirm how the receipt will be delivered, and then issue it electronically instead of on paper. You can send it or make it available electronically, but you should not treat e-delivery as an afterthought once the paper receipt has already been produced. If you compare neighboring regimes, Moldova's electronic receipt and virtual cash-register rules raise a similar operational question about when electronic delivery is valid and what still has to appear on the receipt.

The Slovakia cashless payment rule 2026 is different. From May 1, 2026, sellers who are required to record sales through eKasa generally must allow a cashless payment over EUR 1. That rule is about how the customer can pay, not about what the eKasa receipt must contain. It does not create a new receipt-content checklist by itself.

For daily operations, that usually means three checks at the till:

• Get buyer consent before printing if you want to use an electronic receipt.
• Keep the eKasa receipt content intact whether the receipt is paper or electronic.
• Confirm your checkout setup offers a compliant cashless option for covered sales above EUR 1 from May 1, 2026.

Retention rules and invoice-payment receipts

Slovakia's retention rules focus on keeping receipt outputs and paragon copies readable and retrievable for five years. Copies of paragons must be kept in chronological order for five years from the end of the calendar year in which they were issued, and paper outputs from eKasa must remain readable for that same five-year period. In practical terms, a paper output or paragon created at any point in 2026 needs to stay legible through December 31, 2031. That means your archive cannot rely on faded thermal paper alone.

For a normal over-the-counter sale, your retention file should let you prove the receipt event from start to finish: when it was issued, for how much, and which sales record it supports. That means you should be able to retrieve the receipt identifiers, issue date and time, total paid, and the underlying sales entry the receipt belongs to. If a paragon was used because of an interruption, keep that copy in order and make sure it can still be matched back to the later eKasa record.

The invoice-payment crossover is narrower than many businesses expect. From January 1, 2026, an eKasa receipt can be used when an invoice or part of an invoice is paid through eKasa, but that does not turn eKasa into a full e-invoicing system. Slovakia's separate structured e-invoicing rollout for domestic B2B and B2G invoices starts later and follows different format, exchange, and reporting rules. The invoice still carries the underlying commercial and VAT detail, while the eKasa receipt works as payment evidence tied to that invoice through the cash-register workflow.

For example, if a customer pays part of an already issued invoice at the counter, the eKasa receipt proves the payment event, the amount received, and the register-level identifiers tied to that payment. The invoice still carries the line items, tax logic, and original commercial terms. Your accounting team then needs to match the receipt to the open invoice balance and the daily eKasa totals so the payment trail, the receivable, and the receipt archive all point to the same transaction.

That distinction matters in VAT and audit work. If you are reviewing a Slovakia eKasa invoice payment receipt, you should not expect it to replace the invoice. You need both documents tied together: the invoice for the taxable transaction details, and the eKasa receipt for the payment evidence, timestamp, total paid, and traceable register record. Without that link, reconciliation gets messy fast, especially when you are matching cash or card receipts to open receivables, daily takings, or the Slovakia VAT control statement section map and filing deadline. If you also issue invoices in neighboring markets, Slovenia's fiscal verification of invoices and miniBlagajna fallback rules show how invoice confirmation duties can attach to the invoice itself rather than only to the payment receipt.

A finance team should be able to retrieve the following during the retention period:

• The readable paper output or, where applicable, the stored electronic receipt record.
• Any paragon copy, kept in chronological order.
• The receipt number, identifier, QR-based verification elements, and issue date and time.
• The total amount paid and whether it settled all or part of the balance.
• The related invoice number for any invoice-payment receipt.
• The underlying invoice itself, with the VAT and transaction detail that the invoice-payment receipt does not show.
• The ledger, receivables, or sales-record reference that ties the receipt back to your accounting trail.

---

A practical eKasa compliance checklist for daily operations

Use this as a working control document once your checkout rules are set and you need them to hold up in bookkeeping and reconciliation.

• Check whether the payment triggers eKasa before you close the sale. If you are taking a covered payment at the point of sale, including cash and other covered payment instruments, record it through eKasa. If the customer pays later by ordinary account-to-account transfer outside the sales point based on an invoice, do not treat that as an eKasa receipt event.
• Issue the receipt immediately after recording the transaction. Do not hand over a non-fiscal slip instead of the eKasa receipt. The same discipline applies to returns, corrections, and refunded payments.
• Verify that the receipt shows all mandatory data. In practice, that means the receipt should identify the seller and sales point, show the date and time, describe the goods or service clearly, show the price and total, include VAT details where applicable, and include the eKasa-specific fiscal elements such as the cash-register code, document sequence details, unique document identifier, readable QR code, and verification code.
• For invoice settlements, confirm the receipt is tailored to that use case. If the eKasa document records payment of an invoice or part of an invoice, make sure the receipt includes the invoice reference needed for later matching in accounting and audit work.
• Only send an electronic receipt when the legal conditions are met. The buyer must agree, must request electronic delivery before printing, and you must not also print the paper receipt.
• Build the cashless-payment rule into checkout controls. From May 1, 2026, sellers that fall under the eKasa recording obligation generally must allow a cashless payment option for transactions above EUR 1.
• Retain records on the right timetable. Keep receipt copies in chronological order for five years from the end of the year in which they were issued, and make sure printed outputs remain legible for that full period.
• Reconcile eKasa against the books, not just the drawer. Match eKasa receipts to cash, card, voucher, refund, and invoice-payment postings. Investigate gaps such as missing QR-based fiscal identifiers, missing invoice references, or reversals that do not tie back to the original sale.
• Review the checklist across locations. Multi-site and cross-border teams can compare Slovak controls with North Macedonia's fiscal receipt and cash-register requirements, then keep those checks aligned with wider receipt and invoice data workflows so checkout records feed cleanly into bookkeeping and document handling.