KSeF Invoice in English for a Foreign Counterparty

In KSeFGPT, an incoming or outgoing invoice can be downloaded as an English PDF visualization. A foreign counterparty receives a readable document with English labels, while the source invoice handled in KSeF remains unchanged.

The English PDF is not a second invoice, a certified translation or a replacement for the FA(3) XML, KSeF number and UPO. It is a communication layer that helps a finance team identify the parties, amounts, currency, due date and payment details.

Before sending it, check more than totals and counterparty data. Review line-item names, notes and purchase-order references as well. English visualization labels do not guarantee that every user-entered value has been translated.

For an outgoing invoice, the safest process is to retain the XML, status, KSeF number and UPO, download the English version, compare the key fields and describe the attachment as an English visualization of the invoice issued in KSeF.

KSeF organizes the technical and formal invoice layer, but it does not remove the language barrier. An Accounts Payable specialist may not understand Polish labels and still needs to find the invoice number, amount due, currency, due date and bank account quickly.

An English visualization is useful even when the counterparty is not based in an English-speaking country. English is the shared language of cost approval, purchase orders and payments for many international teams. The broader language workflow is covered in KSeF invoices in English, German and Ukrainian.

This guide focuses on handing the document over in English. It does not determine VAT treatment, place of supply, intra-Community supply, export of services, reverse charge, currency or the buyer's tax identifier. Those decisions must be made before the invoice is issued.

1. What an English KSeF invoice means

2. How to download an English invoice PDF in KSeFGPT

3. How to check the English version before sending

4. What to write to the foreign counterparty

5. Common mistakes with English invoice visualizations

6. Expert perspective

7. Frequently asked questions

The English version helps the recipient read the document, but a reliable process still requires source-data checks, invoice-status control and a review of user-entered content.

The phrase English invoice is convenient, but it can cause confusion. In this workflow, it means an English visualization of the same invoice data, not a reissued document with a new number or date.

What changes: the language of labels and the way information is presented to the recipient. The counterparty can identify the seller, buyer, line items, tax summary and payment terms more easily.

What does not change: the source FA(3) XML, the issuer's invoice number, the data accepted by KSeF, the KSeF number assigned after acceptance and the UPO. Their roles are explained in Translated KSeF invoice, PDF, XML and UPO.

What still needs checking: user-entered wording, the transaction's tax treatment, the delivery channel and any required visualization markings. Changing the language does not perform these checks for the issuer.

With those layers separated, the next step is to download the English document from KSeFGPT.

In KSeFGPT, the language is selected when downloading the readable invoice version. There is no need to copy the data into a separate template or create a new document in a text editor.

Step 1: open the Invoices module and go to Outgoing or Incoming, depending on the document.

Step 2: find the correct invoice and open the options next to the PDF button.

Step 3: select English. Polish, German and Ukrainian versions are available as well.

Step 4: download and open the file before sharing it. Generating the PDF does not replace a human review.

Step 5: compare it with the source data and then use the agreed delivery channel. The distinction between source data and a readable view is explained further in Translated KSeF invoice, PDF, XML and UPO.

After downloading, the key task is to check the fields the same way an Accounts Payable team will read them.

The review should follow the recipient's workflow. A foreign finance team will not begin with XML analysis. It will first look for the invoice number, party data, purchase-order reference, totals and due date.

Invoice number: compare the issuer's invoice number with the source document. Do not replace it with the KSeF number because the identifiers serve different purposes.

Issue date and supply date: verify the invoice date and the sale, service or delivery date when shown on the invoice.

Seller, buyer and VAT ID: check legal names, addresses, country and tax identifiers. An English label does not correct inaccurate counterparty data.

Purchase order or reference: if the counterparty requires a PO, project or contract number, make sure it is present and easy to identify.

Line items: check descriptions, quantities, units, prices and discounts. This is the most important manual check because free-text descriptions may remain in their source language.

Net, VAT and gross: compare the taxable amount, tax and gross amount for each rate and the entire invoice. Confirm the currency as well.

Due date and payment details: the recipient must be able to find the due date, bank account or IBAN and any agreed transfer instructions. An error here can delay payment even when the invoice itself is valid.

Before sending an outgoing invoice, retain the XML, status, KSeF number and UPO; compare totals and currency; read the line-item descriptions; verify payment details; confirm the delivery channel and any markings required in the specific case. For an incoming invoice, do not assume access to the issuer's UPO.

Once the fields are checked, prepare a message that clearly defines the attachment.

A good message sends the file, states the invoice number and explains the attachment. It does not need a lengthy KSeF explanation or additional tax claims.

First message to Accounts Payable: Please find attached the English visualization of invoice [invoice number], issued in the Polish KSeF system. The language version is provided for readability and is not a separate invoice. Please use the due date and payment details shown in the document.

Request for confirmation or forwarding: Please confirm receipt of invoice [invoice number]. If another person or Accounts Payable team is responsible for processing it, please forward this message or share the correct billing contact with us.

Clarification of the document's role: The attached English PDF is an informational visualization of the invoice issued in KSeF. It does not create a second invoice or change the source invoice data. The invoice reference, amounts and payment terms remain the same.

Accounts Payable is the team that processes supplier invoices and liabilities. Invoice reference identifies the invoice or order, due date is the payment deadline and payment details include the account and transfer information.

For a United States buyer, check the buyer data and transaction context separately in How to issue an invoice to a US company in KSeF.

Once the email is clear, remove the errors that most often create a second, inconsistent document flow.

A second document number: an English visualization should not receive a new number merely because the label language changed. It remains a readable version of the same invoice.

Manual retyping: recreating an English invoice in a text editor increases the risk of differences in price, tax, currency or payment deadline. Generate the visualization from the same data instead.

Assuming complete translation: service names, project numbers, notes and other free-text content may require a separate check or deliberate wording that the recipient understands.

Confusing identifiers: invoice number is the issuer's document number, while the KSeF number is assigned after the system accepts the document. They are not interchangeable.

No email context: an unexplained attachment may look like another invoice, a duplicate or a replacement. One sentence about the English visualization of a KSeF invoice prevents this confusion.

Deriving tax from language: an English PDF does not confirm VAT, reverse charge, intra-Community supply or place of supply. Language and tax correctness are separate checks.

Secure data consistency first, then optimize the language and delivery channel. The English version will support payment instead of creating uncertainty.

The main value of an English visualization is not the creation of another document. It removes friction between a correctly handled KSeF invoice and the day-to-day work of the person who must approve and pay it.

The counterparty's finance team should be able to identify five elements immediately: invoice number, transaction parties, amount and currency, due date and payment details. When these match the source, the readable PDF can materially speed up processing.

The language version must not obscure substantive checks. An incorrect buyer identifier, VAT treatment or bank account remains incorrect under a proper English label. Data, tax and delivery-method reviews must therefore remain separate.

A reliable process combines both layers: for an outgoing invoice, the company retains the XML, status, KSeF number and UPO, while the counterparty receives a document it can read and route for payment.

KSeFGPT lets users prepare an invoice in a form or AI Chat, review the data, submit the document to KSeF and download a readable visualization in the recipient's language. The user works with the same invoice instead of manually creating a second file with separate amounts.

Visualizations are available in Polish, English, German and Ukrainian. Selecting a language supports communication but does not replace free-text review or the tax decision for the transaction.

For the full multilingual workflow, start with KSeF invoices in English, German and Ukrainian.

To distinguish documents and confirmations, read Translated KSeF invoice, PDF, XML and UPO.

For an English-speaking buyer outside the EU, see How to issue an invoice to a US company in KSeF.

When the recipient works in German, continue with KSeF invoice in German for a German counterparty.