KSeF invoice visualization in English or two languages
When an invoice visualization can be prepared in another language and how to optionally compare its content with the XML submitted to KSeF.
An invoice visualization can be prepared in another language, including English or a bilingual version. However, an important condition applies: after translation, the visualization must be substantively consistent with the data in the XML file submitted to KSeF. This answer appears in question 16 of the official KSeF frequently asked questions.
Different language, consistent content
The choice of language concerns the visualization. Translation should not be equated with permission to change invoice data in the system: the data in the XML submitted to KSeF remain the reference point for substantive consistency.
This applies to both English-language and bilingual visualizations. In both cases, the same condition of consistency after translation must be met. Choosing a language does not replace compliance with this condition.
This guide concerns only the language of the visualization and its consistency with the XML content. It is neither a general guide to international invoicing nor instructions for changing invoice data in KSeF.
Optional checklist for comparison with XML
As an organizational recommendation, we suggest comparing the prepared visualization with the XML submitted to KSeF. The following checklist is an optional suggested workflow, not an official requirement or a guarantee of translation accuracy.
- Compare the details identifying the parties and the invoice with the corresponding data in the XML.
- Check whether translated descriptions preserve the meaning of the content recorded in the XML.
- Compare the dates, numbers and amounts displayed in the visualization with the data in the XML.
- For a bilingual version, compare the meaning of both language versions with the XML content.
- Flag unclear wording for another check rather than treating it as consistent without comparison.
You can adapt the way you organize this comparison to your own workflow. The optional nature of the checklist does not make the condition of substantive consistency stated in the official KSeF answer optional.
The key principle
An English-language or bilingual visualization is possible, but after translation it must be substantively consistent with the data in the XML submitted to KSeF. Translation concerns the language of presentation, not unrestricted changes to the invoice content.