Error codes · ksef · Poland

KSEF-440Partly

KSeF Duplicate Invoice Rejection (HTTP 440)

This is the rejection, word for word: „[KSEF-440] The KSeF system rejected your invoice because it detected a duplicate submission. KSeF checks the combination of seller NIP, invoice number, and invoice date against all invoices submitted in the last 10 years. If a match is found, the API returns HTTP status 440 and the invoice is not accepted.“

KSeF performs duplicate detection by hashing three fields: the seller's NIP (Numer Identyfikacji Podatkowej), the invoice number (P_2), and the invoice issue date (P_1). This check uses a 10-year lookback window. The FA(3) schema enforces these as mandatory fields, so the duplicate check always runs. The error is returned as an HTTP 440 status code from the KSeF REST API v2.0 endpoint /online/Invoice/Send.

What to have readyThe correct figures from your bookkeeping; we show you which field is affected.
What we doEnsure the invoice number (P_2) is unique per seller NIP and issue date combination. If this is a correction, use the correction invoice type with a reference to the original KSeF invoice number.
If you enter it yourself in your invoicing software
Before
<Fa>\n  <P_1>2026-03-25</P_1>\n  <P_2>FV/2026/03/0041</P_2>\n</Fa>
After
<Fa>\n  <P_1>2026-03-25</P_1>\n  <P_2>FV/2026/03/0042</P_2>\n</Fa>
What the finding looks likeExample
FindingNeeds your check · KSEF-440
From youThe correct figures
ThenChecked again
ProofSHA-256 and /verify link after the check