PDF vs. XML

Why do some accounting teams request a PDF in addition to the archived XML?

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

Short answer

A separately stored PDF is not required merely to satisfy the archiving rule. The original XML must be retained for ten years, and readability can be ensured by displaying its content in a comprehensible form on request, for example through an XML visualization tool. A parallel PDF is therefore usually an organizational convenience rather than a separate statutory requirement.

Legal status

Enough. XML + display tool

PDF is not legally required permanent part of the archive.

Approval processes

Habit for visual inspection

Part of the companies is not yet comfortable XML a wiener in a regular workflow.

Persistence

Transitional period

Trust in the new format grows gradually with experience.

Risk of chaos

Unsynchronised channels

The solution is one reliable XML a wiener, not a permanent duplicate PDF.

Detailed explanation

In practice, this most often involves three aspects: firstly, many internal approval processes (who approves which invoice for payment, who verifies its accuracy) have historically been based on the assumption that a person simply views the document as an image or PDF, and not every company already has a convenient tool built into its software to view XML directly. Secondly, it is a matter of inertia and mistrust of the new format, which will likely fade over time as tools for viewing XML become a standard feature of accounting software. Thirdly, your observation from abroad — where XML is sent via post and the PDF separately by email — is a valid concern: if these two channels are not synchronised, there is a risk that someone will work with an out-of-date or incorrectly assigned PDF, whilst only the XML remains legally binding. The correct solution is not to abandon PDFs altogether, but to have a single secure tool capable of displaying the XML in a readable format at any time upon request, without the need to maintain a parallel, separately delivered file.

As set out in the Act

The obligation to retain an electronic invoice for ten years in its original XML format is laid down in Section 85o(15) of Act No. 222/2004 Coll. on VAT. The requirement for the invoice to be legible and for this to be met by displaying it on request rather than permanently storing it in a legible form is confirmed by the interpretation of Section 71(3) of the VAT Act, according to which it is not necessary to have the invoice permanently available in a legible form (for example, as a PDF file stored alongside the XML) — a mechanism that generates a legible output from the XML on request is sufficient.

Practical examples

  • The company will integrate an XML viewer into its accounting software, and the approval process will be just as convenient as it was previously with PDFs.
  • A foreign partner sends the XML via Peppol and the PDF separately by email, which causes confusion as to which document is the current one.
  • Once a reliable tool for viewing XML has been introduced, the company will no longer require PDFs to be retained alongside the XML.

Most common mistakes

  • “The law requires the permanent concurrent storage of both XML and PDF.” The law requires the archiving of XML and readability on request, not the permanent duplication of PDFs.
  • “Insisting on PDFs is always justified by a legal requirement.” In most cases, this is a matter of organisational habit or the incomplete digitisation of approval processes.
  • “The solution to the confusion between XML and PDF is to stop using PDF altogether.” The solution is a reliable XML viewer that generates a readable output on demand, not a rejection of the readable format as such.

Conclusion

Retain the XML and ensure that it can be displayed in human-readable form; keeping a parallel PDF is generally an internal practice, not a statutory duty.

Legal basis

  • Act No. 222/2004 Coll. on VAT, Section 85o(15)
  • Act No. 222/2004 Coll. on VAT, Section 71(3)

Related questions

This does not constitute legal advice. Sources: Act No. 222/2004 Coll. on VAT, as amended by Act No. 385/2025 Coll., official methodological and information materials from the Slovak Financial Administration on e-invoice. Verified on 7 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. 16: Visualisation consistency: If the recipient generates a visualisation (a human-readable form) from the received XML in their own system, how is it guaranteed that this visualisation is identical to the sender’s intention? Is there a recommended style sheet (XSLT) for the uniform display of invoices on the Slovak market?

An electronic invoice is legally and technically represented by a structured XML document in accordance with the relevant standard (e.g. BIS 3); it is the data content in the XML that is binding, not its visual appearance. If the recipient generates a visualisation in their own system, its factual accuracy is determined by the unalterable XML content – standard BIS XML visualisation tools are sufficient for display. No binding, uniform style sheet (XSLT) has been specified for the Slovak market for the display of invoices; the legislation requires assurance of the authenticity of origin, the integrity of the content and legibility, not a uniform graphic design.

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.