KSeF invoice in English, German and Ukrainian

KSeF works with a structured invoice, meaning data saved as FA(3) XML. The person on the other side often does not want to analyze XML or a Polish invoice visualization, but needs a readable PDF in the language used in their purchasing process.

In KSeFGPT, an incoming or outgoing invoice can be downloaded as an informational visualization in Polish, English, German or Ukrainian. This makes communication easier, especially when the recipient is based in Germany, works in English, or has a Ukrainian finance team.

The translated version is not a new invoice, does not change the XML sent to KSeF and does not replace UPO. It is a practical communication layer: the source of truth remains the FA(3) data, the KSeF number and the acceptance confirmation.

The safest approach is to separate three concepts: structured invoice, visualization and translated visualization. A structured invoice is a document issued using KSeF and saved as XML compliant with the FA(3) logical structure. This file contains the data that the system can accept, validate and store.

A visualization or PDF is a readable representation of that data for people. It lets accounting, purchasing teams or counterparties see the invoice number, parties, line items, amounts and dates without opening XML.

A translated visualization adds one more layer: labels and document descriptions are shown in the counterparty's language. In practice, the document can be easier to read in English, German or Ukrainian, but it still refers to the same source invoice in KSeF.

A translated invoice version is most useful when the problem is not issuing the document itself, but communication after issuance. A Polish business can correctly issue an invoice in KSeF, while a foreign counterparty still needs to understand what the document concerns, what the payment term is and how to identify the transaction parties.

The German version helps when working with companies from Germany, Austria or Switzerland, where purchasing teams naturally use terms such as Rechnung, Käufer, Verkäufer and Zahlungsfrist. The English version works as a universal language for companies outside Poland, including cases where the counterparty's country does not have a dedicated language version. The Ukrainian version is useful for finance teams, operational staff and counterparties who can verify documents faster in Ukrainian.

This does not decide VAT rules, intra-Community supplies, export of services or place of supply. Those questions should still be assessed separately by accounting. A translated invoice helps the recipient read the document; it does not make tax decisions for the issuer.

The process should stay simple: the user works with the same invoice in the Invoices module, but chooses the language when downloading the PDF. There is no need to create a second invoice or manually copy data into a separate template.

Open the Invoices module from the left main menu. Then open Incoming or Outgoing, depending on where the document is located. For the selected invoice, click the dropdown next to the PDF button and choose the language: Polish, English, German or Ukrainian. After downloading, send the file as an informational copy of the document handled in KSeF.

The message to the counterparty should clearly state that the attachment is a readable invoice version, not a separate document issued outside KSeF. This matters especially when the counterparty archives the PDF in their workflow, while the issuer's accounting relies on XML, the KSeF number and UPO. The KSeF number identifies the accepted invoice and is not an element sent in the XML, while UPO confirms acceptance by the system.

A short good message does two things: sends the file and immediately explains its meaning. The counterparty should understand that they receive a readable version of an invoice issued in KSeF, prepared for convenient work in their language.

In Polish: W załączniku przesyłamy informacyjną wizualizację faktury wystawionej w KSeF. Wersja językowa ma ułatwić odczyt dokumentu. Dane źródłowe faktury pozostają w KSeF.

In English: Please find attached an informational visualization of the invoice issued in KSeF. The language version is provided to make the document easier to read. The source invoice data remains in KSeF.

In German: Im Anhang senden wir Ihnen eine informative Visualisierung der in KSeF ausgestellten Rechnung. Die Sprachversion dient der besseren Lesbarkeit. Die Quelldaten der Rechnung bleiben in KSeF.

In Ukrainian: У вкладенні надсилаємо інформаційну візуалізацію рахунку-фактури, виставленого в KSeF. Мовна версія підготовлена для зручнішого читання документа. Джерельні дані рахунку залишаються в KSeF.

The first mistake is treating an English or German PDF as a separate invoice. If the document is a visualization of data from KSeF, it should not get a new number, a new issue date or a separate workflow that suggests re-issuance.

The second mistake is manually creating a foreign-language document in a text editor. It is easy to copy the amount, NIP, payment term or invoice number incorrectly. A better process is to download the language version from the same source used to handle the invoice.

The third mistake is sending the file without context. If the counterparty only receives an attachment, they may not know whether it is a new invoice, translation, note, duplicate or supporting material. One sentence in the email is usually enough to avoid that misunderstanding.

Foreign invoices have two independent levels. The first is tax and data: counterparty country, tax identifier, currency, VAT rate, reverse charge, intra-Community supply, export of services or another settlement scenario. The second is communication: whether the counterparty understands the document received after issuance.

A translated visualization mainly solves the second problem. It does not say whether a transaction should include Polish VAT, whether it is a service for an EU taxpayer or whether an additional annotation is required. It does help the counterparty's finance team read the invoice and handle payment faster.

That is why this article is worth reading together with guides on document structure and submission. To organize the basics, start with XML and FA(3) format in KSeF, then read Sending invoices to KSeF. The difference between PDF and structured invoice is also explained in Can a PDF be sent to KSeF?. For invoice workflows, see KSeFGPT - invoice import, export and AI analytics app.

The biggest value of a translated visualization is not that it replaces KSeF. It removes a very practical friction point in the counterparty relationship: the recipient understands faster what they should pay for, what data appears on the document and what payment term they should handle.

In communication with foreign companies, this matters. If a document is formally correct but reaches someone who does not speak Polish, the process can stop at a simple question about label meanings. The language version shortens that step without creating a second document.

This is why the article consistently uses the term informational version. Good practice is to keep the formal order in KSeF and at the same time give the counterparty a file they can actually read.

If you want to understand why a translated PDF does not replace source data, read XML and FA(3) format in KSeF. This guide explains the difference between data structure and document visualization.

If acceptance confirmation matters in your process, go to UPO in KSeF. For the full process of issuing and sharing an invoice, also read Sending invoices to KSeF.

For broader product context, including import, export and invoice work, see KSeFGPT - invoice import, export and AI analytics app.