Zero correction in KSeF and VAT dispute risk

An invoice accepted by KSeF, the Polish National e-Invoice System, cannot be fixed by editing, cancelling or deleting it. If the document has received a KSeF number, the error is corrected with a corrective invoice, which creates another trace in the system.

A zero correction is the right tool in specific cases: full return, cancellation of the entire transaction, invoice issued by mistake, wrong buyer or a document that should not create any tax effect. It is not an automatic method for every error in price, VAT rate, description or additional data.

The biggest risk appears when KSeF shows the following sequence: original invoice, zero correction and a new invoice for the same real sale, even though correcting the specific mistake would have been enough. That setup can raise questions about double VAT reporting, the buyer's deduction right and whether the documents match the economic reality.

In traditional invoice flows, some companies treated an invoice like a file that could be fixed, resent or replaced with a newer version. KSeF changes that reflex. After acceptance by the system, a structured invoice has a KSeF number, UPO, the official receipt, and remains in the document history.

The key question is not only how quickly the error can be fixed. The more important question is what tax effect the documentation should show after the correction. If the transaction really happened and the parties are correct, reducing the whole invoice to zero may go too far.

The simplest operating rule is this: correct only what actually needs correction. If the error concerns one line item, the correction should concern that line item. If the error concerns the entire business relationship or the document should not remain in the tax settlement, only then consider a zero correction.

A zero correction is not wrong by itself. What may be wrong is using it without a reason that justifies neutralizing the entire economic effect of the invoice.

A zero correction makes sense when the entire effect of the original invoice has to be removed from tax settlements. This is not about technically deleting the document in KSeF, because that cannot be done. It is about issuing a corrective invoice that neutralizes the original document for tax purposes.

In its guidance, the Ministry of Finance gives an example of a structured corrective invoice reducing the value to zero in connection with a full return of goods. In that case, the seller reduces the taxable base in the period when the correction is issued in KSeF, without separate receipt confirmation from the buyer, because the buyer receives the document in the system.

In practice, the same direction may be justified when an invoice was issued to the wrong entity, was issued by mistake or when the transaction did not happen at all. In each of these cases, keep evidence of the correction reason: correspondence, order cancellation, return protocol, accounting note or agreement with the counterparty.

The risk starts when the transaction really happened, the seller and buyer are correct, and the error concerns only part of the invoice. In that case, a zero correction can make the picture less clear instead of organizing it.

Example: the invoice has the correct buyer and the correct supply, but the price of one line item is wrong. If the seller reduces the whole invoice to zero and issues a new one, KSeF shows two sales documents and a zero correction. The tax authority may ask why the document was fully withdrawn if the transaction was not withdrawn.

The same applies to an incorrect service description, order number or additional data. If the core transaction is correct, correcting the specific field or line item is clearer. Interpretations concerning Podmiot3 data show that even auxiliary data can be sensitive and requires precise identification of what is actually wrong.

A major gap in many guides is mixing two different issues: a wrong buyer in Podmiot2 and wrong additional data in Podmiot3. In KSeF this is not just a technical detail, because Podmiot2 identifies the invoice buyer, while Podmiot3 may indicate, for example, a recipient, subordinate unit or another entity connected with the document.

If the buyer's NIP in Podmiot2 is wrong, the invoice may reach the wrong entity. In that case, a zero correction and issuing a new invoice to the correct buyer has stronger practical justification. But if Podmiot2 is correct and the problem concerns only Podmiot3, automatically reducing the whole invoice to zero may be too broad a response.

This point matters especially for Polish local government units, VAT groups and companies with branches, where an invoice may show the main entity and an additional unit or recipient. With this type of error, first determine whether the mistake changes the invoice buyer or only describes the wrong recipient in the structure.

For the seller, the problem may be a document sequence that looks like two invoices for one real sale. If the original invoice should not have been reduced to zero and then a new invoice was issued, the seller has to explain which invoice documents the sale and how to treat VAT from the documents visible in the system.

For the buyer, the risk concerns the right to deduct VAT. The Ministry of Finance stresses that KSeF does not change substantive VAT rules: deduction depends on purchases being used for taxable activities and on the absence of negative conditions. An invoice does not give a safe deduction only because it exists in KSeF.

The most problematic scenario is one in which the buyer deducts VAT from the original invoice, then books the zero correction, and then deducts VAT from the new invoice for the same transaction without a consistent explanation. This process should be clarified before closing the Polish SAF-T VAT file, JPK_VAT, not only during a tax audit.

First stop automatic issuing of further documents. Another correction without analysis can deepen the problem. The goal is not to multiply documents, but to make the KSeF history, VAT records and settlements show one real sale or one real cancellation.

The first step is to classify the error. If the invoice was issued to the wrong buyer or the transaction did not happen, the sequence of zero correction plus new invoice may be defensible. But if the error concerned only value or description, determine with accounting whether it is better to reverse the effects of the wrong sequence and return to the original invoice as the primary document.

The second step is to agree the settlement with the buyer. Without this, the seller may be organizing its VAT while the buyer works on a different assumption. In KSeF both sides see the documents, but that does not mean they automatically understand them in the same way.

A company or accounting office should establish that a zero correction requires additional approval. It should not be a normal shortcut for a user who saw an error and wants to quickly start again.

A good procedure should separate three decisions: whether to correct data, whether to correct values, or whether to reduce the whole document to zero. Each decision has a different VAT effect and a different communication path with the counterparty.

In KSeFGPT, a correction can start from source data: an invoice fetched from KSeF, an XML file or a selected counterparty. This helps reduce manual retyping of invoice numbers, NIPs and line items, but it does not replace the accounting decision about which correction type is appropriate.

A zero correction can be tempting because it looks like the simplest way to return to the starting point. In KSeF, this is misleading. The original document does not disappear, and the correction and any new invoice create additional events that must be explained.

From a tax audit perspective, what matters is not only whether a single XML file is correct, but the logic of the whole sequence. If the sale was real and the buyer was correct, the authority may expect a simple correction of the specific error instead of full zeroing of the document and issuing the invoice again.

The safest correction processes are plain and well documented: they identify the invoice, state the specific reason, show the net/VAT/gross effect, agree the settlement with the other party and keep the UPO. KSeF rewards exactly this discipline, because every stage remains in the data.

If you want to organize the whole document correction process, start with Corrective invoice in KSeF.

For buyer-side risk, read What to do when a KSeF account shows an invoice for purchases that are not ours?.

If corrections affect VAT records, also check KSeF and JPK.

After each correction submission, track confirmations. See UPO in KSeF.