KSeF rejected an earlier XML: must invoice numbering change?
Invoices 8 and 9 accepted while 7 was rejected? Issuer numbering and KSeF acceptance order are different.
You prepared invoices in order, but an earlier XML failed validation while later invoices received KSeF numbers. That sequence alone does not require renumbering your sales.
The issuer’s number is separate
Each invoice has a successive number within one or more series that identifies it unambiguously. This is the issuer’s number in P_2. The KSeF number is a separate identifier. Do not change P_2 merely to mirror system processing order.
The Ministry’s example
Invoices 7, 8 and 9 were prepared in the correct order. Invoice 7 was rejected for a structure mismatch, while 8 and 9 were accepted. After repair, invoice 7 was sent and accepted on the same day. The Ministry requires no correction solely because it was accepted later. The example does not settle issue-date consequences of retrying the following day.
Separate XML failure from invoice errors
Read the rejection, fix its cause and retain the relationship between attempts and the same document. Do not automatically issue another invoice or a correction just for sequence. Errors in sale data, dates or duplicates need separate assessment; this guide covers numbering order only.
FAQ
Does an acceptance-order gap require a correction?
Not by itself, where the invoices were originally prepared with correct numbering.
Should I erase the rejected attempt?
Keeping its message and the repaired attempt’s result makes checking easier. This is a practical recommendation, not an additional requirement from the example.
Can I freely change the issue date?
No. The example describes repair and acceptance on the same day, not a general rule for other dates.
Source
Ministry of Finance: KSeF 2.0 handbook.
Next step
Describe your issue in the Oxyok form. Do not send passwords or access keys..