Duplicate Invoices in KSeF: Where They Come From and How to Stop Them

The most common cause of duplicate invoices in KSeF is not a system bug. It is the sender resubmitting during processing. The second most common is parallel delivery: the invoice goes through KSeF, and a PDF visualisation goes by email. The buyer's accountant receives both and books both.

Grant Thornton's April 2026 survey found that 74% of businesses experienced e-invoicing errors in the first month. Duplicate invoices are not always counted as errors, because both copies are technically valid KSeF documents with their own KSeF numbers. The error surfaces in accounting: double booking, double payment, VAT overstatement.

How Duplicates Happen

Resend during processing

The user submits an invoice. KSeF returns status 100 (accepted, processing) or the request times out. The user panics and resubmits. The first submission succeeds. The second submission hits code 440 (duplicate invoice number). But if the invoice number was auto-incremented between submissions, both go through with different numbers. Now there are two invoices for the same transaction, each with its own KSeF number.

Parallel app and Aplikacja Podatnika

A user issues an invoice through their invoicing app and, unsure whether it worked, also issues it manually through Aplikacja Podatnika. Two submissions, two KSeF numbers, one transaction.

PDF plus KSeF

The issuer submits through KSeF and emails a PDF visualisation to the buyer. The buyer's accountant receives the PDF by email and sees the KSeF invoice in their KSeF inbox. If the accountant does not realise they are the same invoice, they book both. The PDF's bank details may also differ from what KSeF displays, creating a payment discrepancy on top of the booking duplicate.

How to Detect Duplicates

KSeF does not detect duplicates across different invoice numbers. It detects only exact invoice-number duplicates (code 440). If two invoices have different numbers but the same buyer, amount, and date, KSeF accepts both.

Detection is a product feature, not a platform feature. Pre-send validation should check:

• Same buyer NIP, same net amount, same date, different invoice number
• Same buyer NIP, same amount, within 24 hours of a previous submission
• Invoice number patterns that suggest auto-increment on resend

Prevention Checklist

1. Never blind-resend. Before resubmitting, query KSeF by your own invoice number. If the first submission succeeded, adopt it.
2. Check session status. Status 100 or 150 means processing. Poll. Do not resend.
3. One submission channel. Use either your invoicing app or Aplikacja Podatnika. Not both for the same invoice.
4. Stop emailing PDFs. KSeF delivery is the legal delivery. A PDF visualisation is a courtesy that creates a duplicate risk. If you must send a PDF, mark it clearly as a visualisation of KSeF invoice number [X].
5. Auto-increment protection. Configure your invoicing tool to not auto-increment the invoice number on resend. The same invoice number should be reused until the submission succeeds.
6. Buyer communication. Tell your buyers that invoices arrive through KSeF and that emailed PDFs are visualisations, not separate invoices.

This material is information of a general nature and does not constitute legal or tax advice. For a specific situation, verify the current rules or consult a qualified adviser.