System verification

How can an e-invoicing system be checked against Slovak requirements?

⚠ Machine-translated answer, not yet manually reviewed. For the exact wording, see the Slovak original.

Short answer

The ability to create a PDF or export some form of XML is not enough. Verify that the system produces e-invoice compliant with EN 16931 and Peppol BIS, applies Slovak rules, uses the correct EndpointID, sends and receives through a delivery service, returns status messages, handles errors, and supports attachments, corrective documents and retention of the original XML.

Format

EN 16931/Peppol

The system must produce valid XML, not just PDF.

Slovakia

National rules

EndpointID, VAT number, C5/reporting and local requirements.

Delivery

Postman and estates

Sending, receiving, lookup, errors and monitoring.

Archive

Evidence

Original XML, attachments, metadata and patches.

Detailed explanation

The practical test should cover a standard invoice, an invoice with different VAT rates, an exempt supply, a reverse charge, a credit note, an advance payment, an attachment, a foreign currency and an incorrect participant ID. The software supplier should be able to demonstrate validation, technical logs and a sample transmission via the e-invoicing delivery-service provider. A company should not simply accept a marketing claim that the system is ready for e-invoicing.

As set out in the law and technical rules

The VAT Act specifies the content and obligations, in particular through Sections 71, 74, 76a and 85o. Technical compliance must be verified in accordance with EN 16931, Peppol BIS Billing 3.0 and the Slovak implementation rules.

Practical examples

  • The ERP supplier shall provide sample XML files and the validation results.
  • The postal service provider will display the status ‘Participant not found’ and the procedure for resending.
  • The accountant will test the import of the received e-invoice and the link to the control statement.

Common misconceptions

  • “We have a PDF export; we’re ready.” No. Structured XML and delivery are required.
  • “One test invoice is enough.” No. Both typical and error scenarios need to be tested.
  • “The software handles the tax assessment for me.” No. Validation does not replace an accounting check.

Conclusion

Prove readiness with an end-to-end test covering the accounting source, XML generation, validation, delivery, error handling, receipt and archiving.

Legal and technical basis

  • Act No. 222/2004 Coll. on VAT, Section 71
  • Act No. 222/2004 Coll. on VAT, Section 74
  • Act No. 222/2004 Coll. on VAT, Section 76a
  • Act No. 222/2004 Coll. on VAT, Section 85o
  • EN 16931 a Peppol BIS Billing 3.0

Related questions

This does not constitute legal advice. Sources: Act No. 222/2004 Coll. on VAT, Act No. 385/2025 Coll., official guidance and information materials from the Slovak Financial Administration on e-invoice, EN 16931, Peppol BIS Billing 3.0 and OpenPeppol eDelivery documentation. Verified on 13 July 2026.

Official cases from the Slovak Financial Administration’s FAQs

The following questions and answers are taken from the current July FAQ from the Financial Administration and have been assigned to this topic. Grouping the cases prevents the creation of duplicate pages, whilst retaining the full answer and the exact wording of the question.

Example No. 23: How can you check whether your e-invoicing system meets the mandatory requirements in Slovakia?

Verifying compliance with electronic invoicing involves several key elements, which vary depending on the size of the business and its existing systems. For most businesses, compliance verification is not something they should have to deal with entirely on their own. Basic compliance components: • Confirmation that the system is capable of generating and processing structured electronic invoices. • The ability to connect to the Peppol network (either directly or via a service provider). • Correct handling of all required invoice data fields. • Checks to ensure the authenticity of invoices and prevent tampering. For businesses using modern accounting software: • The software provider will likely take care of a large part of the technical compliance. • Emphasis should be placed on the correct configuration of e-invoicing functions. • Testing the sending and receiving of e-invoices with business partners. For businesses with more complex needs: • Technical compliance becomes more complex with in-house or legacy systems. • Regular audits may be necessary to ensure ongoing compliance. • Specialised expertise is usually required for a comprehensive verification.

Primary source: Financial Administration of the Slovak Republic, FAQ 9/VAT/2025/IM k e-invoice, July 2026 update. Processed and checked on 13 July 2026.