How to Convert KSeF XML into a Readable PDF Invoice

A KSeF XML file stores invoice data in the FA(3) structure, but it is not as convenient to read as a traditional document. A converter can arrange the data in a readable PDF with details of the seller, buyer, line items, tax and totals.

Generating a PDF does not change the source document, repair errors or confirm that KSeF has accepted the invoice. A complete check still requires the XML file, validation and system data such as the status, KSeF number and UPO, the official acknowledgement of receipt.

After conversion, compare the parties, invoice number, dates, currency, number of line items, VAT rates and amounts with the XML file. If the PDF will be sent to a customer or used outside KSeF, also check whether the specific case requires the correct QR verification code.

You receive a file with an XML extension and see tags, technical field names and a long stream of data instead of a readable invoice. This is normal. A structured invoice is designed primarily for automatic processing by KSeF and accounting software, not for viewing like a text document.

A PDF solves the readability problem at only one level. It presents the data to a person. On its own, it does not show whether the structure complies with FA(3), whether KSeF has accepted the invoice or whether its tax treatment is correct.

1. What happens when XML is converted to PDF

2. How to convert KSeF XML to PDF step by step

3. What to check in the visualisation before downloading the PDF

4. What a PDF does not confirm

5. When a visualisation needs a QR code

6. Expert perspective

7. Frequently asked questions

The table below separates the parts of the process that distinguish a working data preview from a visualisation of an invoice already processed by KSeF.

The FA(3) structure stores data in organised sections. The header contains technical information, the entity sections describe the seller, buyer and other parties, and the invoice section includes the document number, dates, currency, line items, VAT rates and totals.

A converter reads these fields and arranges them in a format that resembles a traditional invoice. It does not use OCR because the data is already stored in the file. Its purpose is to map the XML structure to headings, tables and totals that a person can read.

Transaction parties: check the seller's and buyer's name, identifier and address.

Document: compare the invoice number, dates, currency and payment details.

Line items and totals: check descriptions, quantities, prices, VAT rates and the net, VAT and gross amounts.

Conversion changes how the invoice is presented, not its content. Once you know what the generator does, you can move safely to the conversion process itself.

In the KSeF XML-to-PDF converter, you can paste the invoice content or upload a file from your device. The tool is intended primarily for invoices using the current FA(3) structure.

In the current version of the tool, the XML content is read and processed in the browser. The server checks the usage limit, while the PDF itself is created on the user's device. You need to provide an email address before downloading the result. The free limit is 3 uses within 24 hours.

Preparation: keep the original XML file unchanged and work on a copy.

Upload: open the converter, paste the content or select a file from your device.

Generation and download: start the process, enter your email address and download the prepared PDF.

Check: compare the visualisation with the source data before sharing it.

The tool accepts files up to 5 MB. If a file is larger, unusual or contains extensive additional data, check it separately and do not assume that an incomplete visualisation means the invoice itself is incorrect.

The best check is not simply to read the PDF from top to bottom. First identify the fields whose incorrect value would change the meaning of the document, then compare them with the XML file, order, contract or accounting-system data.

Parties: compare the seller's and buyer's name, NIP or another identifier, and address.

Document: check the seller's invoice number, dates and currency.

Line items: compare the number of rows, units of measure, quantities, prices and discounts.

Tax and payment: check VAT rates, net, VAT and gross amounts, as well as the due date and payment account.

Example from an accounting office: a client sends a purchase invoice as XML. The accountant generates a PDF to review the parties, line items and amounts quickly, but also retains the unchanged XML file as part of the records. Before posting the invoice, the accountant runs validation and, if the invoice comes from KSeF, also compares its KSeF number and document status.

This process takes several dozen seconds longer than downloading a PDF without reviewing it, but reduces the risk of posting a readable document with incorrect data. After checking the visualisation, you still need to determine what the PDF itself cannot prove.

A PDF can look correct even when the XML file fails validation or contains data that requires clarification. A generator is responsible for presentation. A validator checks technical compliance. KSeF provides the processing status and assigns the system number.

Structure: a PDF does not confirm compliance with the complete FA(3) schema or that every required field has been completed.

Status: a PDF does not prove that KSeF has accepted the invoice, assigned a KSeF number or made a UPO available.

Tax: a readable visualisation does not confirm that the VAT rate or transaction classification is correct.

To check the structure, read the guide to XML validation and processing in KSeF. If you need help identifying fields and numbers, see How to read KSeF XML.

Keeping these layers separate leads to the final important question: can the generated PDF be sent to the customer without any additional action?

A PDF prepared solely as an internal preview is not automatically the same document that a company uses outside KSeF. The Polish Ministry of Finance states that, in situations specified by law, an invoice made available to the buyer or used outside KSeF must carry the appropriate verification code.

The code provides access to the invoice and allows the data stored in KSeF to be checked. For an online invoice used outside the system, it is linked to the KSeF number. In offline modes, the number and labelling of codes depend, among other things, on whether the invoice has already been sent to the system.

Purpose: is the document only for internal review, or will it be provided to the recipient?

Status: is the invoice already in KSeF and does it have a system number?

Marking: does the visualisation contain the correct code for the way the invoice was issued and shared?

The free converter helps create a readable document, but you should not automatically assume that every PDF downloaded from it is a complete visualisation for every KSeF scenario. If the document will leave the company, verify the QR code and invoice status.

The most common mistake is to equate readability with correctness. When a document has a line-item table and totals that look right, it is easy to assume that the process is complete. In reality, the generator may only have displayed correctly the values it received in the XML file.

A safe working set has several layers. The XML file stores the invoice data. Validation answers technical questions. The KSeF number, status and UPO document the process in the system. The PDF allows a person to read and compare the invoice quickly.

In a small company, this can be a simple manual process. An accounting office or an organisation processing many invoices should standardise it: retain the original XML file, generate a preview, check an agreed set of fields and only then send the document for further approval or posting.

To understand the file structure first, read How to read KSeF XML. For a broader explanation of fields and the schema, see XML and the FA(3) format in KSeF.

Before using the document in accounting, also review XML validation and processing in KSeF. If you are starting with a PDF and need the reverse process, read Can you send a PDF to KSeF?.