Missing UPO in KSeF: how to download the official receipt?

A missing UPO after sending an invoice to KSeF is not a diagnosis on its own. First check the invoice or session status, KSeF number, reference number, NIP context and the tool that sent the document.

UPO can be downloaded only for an invoice successfully accepted by KSeF or for a closed and processed session, if session UPO was generated. Status 100 or 150 means that you should keep monitoring the same submission, not immediately create another one.

If the invoice was rejected, it will not receive a KSeF number or UPO. Read the error code, fix the source problem and only then submit the corrected FA(3) XML again.

The worst reaction to missing UPO is to resend the invoice automatically without checking the status. You may create a duplicate or make it harder to identify the original operation.

A missing UPO may result from processing, a document error, a wrong session, an expired download link or limitations of the tool where you are looking for the receipt. The procedure always starts with the status of the same invoice or session.

Submission status tells you more than a message that a file was sent to the system. In the KSeF API, status 100 means that the invoice was accepted for further processing, status 150 means processing is in progress and status 200 means success.

Only a successful invoice lets you move to the KSeF number and UPO. Error statuses require diagnosis. In that case, looking for UPO makes no sense until you know whether the document was accepted at all.

For a manual path, start with the correct taxpayer context. Sign in to the KSeF 2.0 Taxpayer Application, choose the right entity or NIP and find the invoice by its own number, KSeF number, date or submission data.

Then check the document status. If the invoice is accepted and has a KSeF number, download UPO from the action available next to the invoice or session. If the status shows an error, diagnose the rejection instead of downloading a receipt that was not created.

This article does not treat button labels as fixed, because the Taxpayer Application interface can change. Before publishing a strict click-by-click procedure, compare it with the current Ministry of Finance manual or current application screen.

In an API integration, first retrieve the session list or a specific session status, then invoices in the session or a single invoice status. Only after you know that the document was accepted should you call the UPO endpoint.

CIRF documentation describes two paths for a single invoice UPO: by invoice reference number and by KSeF number. For session UPO, the documentation provides a separate endpoint using the UPO reference number.

In practice, the integration should store the session reference number, invoice reference number, KSeF number, status, acceptance date and the link or downloaded UPO XML. Without these data, finding the receipt later is much harder.

In everyday work, it is easy to confuse invoice UPO with session UPO. Invoice UPO concerns a single document. Session UPO is a collective receipt that appears after a session has been closed and processed.

For small volumes, you usually need the receipt for one concrete invoice. For batch submission, you also need control over the whole package: how many documents were accepted, how many were rejected and which KSeF numbers must be linked with UPO.

The KSeF number identifies an invoice accepted by the system and is returned in UPO, but session-based download endpoints also need the session context. A KSeF number alone, without knowing where and how the invoice was sent, may not be enough to reconstruct the receipt efficiently.

Another common problem is mixing identifiers. The invoice's own number comes from the seller's system, the session reference number describes the technical operation, and the KSeF number is created only after the invoice has been accepted. Each serves a different purpose.

If you only have the invoice number from field P_2, start by finding the document in the tool that sent it. Then read the KSeF number, session number and UPO path.

A KSeF number is a strong sign that the invoice was accepted, but a UPO download problem may still occur because of the link, permissions, context or application. Do not create a new invoice and do not resend the same document.

First refresh the invoice status. If the response contains a UPO link, check its expiry date. OpenAPI describes `upoDownloadUrl` as a link generated when querying status, downloaded with HTTP GET and expiring after a defined time.

If the link expired, generate it again through the status. If you work through an application, check whether you are in the right NIP context and whether that application supports UPO for this invoice. In KSeFGPT, UPO is available for invoices sent through this application.

If there is no KSeF number and no UPO, the case is still open. The document may still be processing or it may have been rejected. Do not automatically send another version until you know the final status.

Check whether the status is still 100 or 150. If the status shows an error, retrieve the details, including code, description, details and possible extensions. For code 440, check the original session and original KSeF number because the problem may be a duplicate.

The full error procedure is described in Invoice rejected by KSeF. This article only answers why UPO is missing and how to determine whether the receipt should already exist.

KSeFGPT organizes the post-submission process: the user sees the document status, reference number, processing result and next actions on the invoice. This matters because missing UPO should not lead to guessing whether the document was accepted.

If the invoice was sent through KSeFGPT, the application can show its status and make UPO available in the same process. If the document was sent by another system, look for the receipt in that tool, the KSeF Taxpayer Application or through an API integration.

This gives the accounting team one procedure: check status, read the KSeF number, download UPO after success or move to error diagnosis. It reduces the risk of resending an invoice only because the receipt was not visible on the first screen.

The Ministry of Finance technical FAQ states that there is no obligation to download and archive KSeF UPO. Still, in operational work it is worth saving UPO locally because it helps with audit, status control and contractor questions.

The best set includes the invoice XML, KSeF number, UPO, invoice's own number from P_2, acceptance date, seller NIP, taxpayer context and information about the tool that submitted the invoice.

A simple file naming convention can look like this: `seller_NIP-invoice_number-KSeF_number-upo.xml`. The name matters less than the team's ability to connect UPO with a concrete invoice rather than only with a package or session.

When UPO is missing, do not start by resending the invoice. First check the status of the same invoice or session, KSeF number, reference number, NIP context and submission source. Only the status tells you whether to wait, regenerate the link, search in another tool or fix an error.

If the status is 200, download UPO and save it with the KSeF number and invoice's own number. If the status is 100 or 150, keep monitoring. If the status shows an error, diagnose the rejection instead of creating a new version of the document.

Read next: UPO in KSeF, Invoice rejected by KSeF, Sending invoices to KSeF and How long to send an invoice to KSeF.