CESOP · reference
CESOP error codes
When CESOP rejects payment data, the Validation Result names the problem with a five-digit code from DG TAXUD’s published catalogue. These are all 39 of them: what each one means, how files usually come to carry it, and how to fix it.
29 can be caught before you file, and 4 more partly — the free CESOP XML validator checks for them in your browser. The other 6 compare your file with data CESOP already holds, so only CESOP can raise them; their pages say how to avoid them.
10xxx · Message header
MessageSpec: references, period, timestamp and message type.
- 10010MessageRefID is not uniqueOnly CESOP can raise it
- 10020The 'Timestamp' element refers to a wrong valueCaught before you file
- 10030The period is before 01/01/2024Caught before you file
- 10040Wrong CorrMessageRefIDPartly caught before you file
- 10050Wrong format of the MessageRefIDCaught before you file
- 10060Wrong format of the CorrMessageRefIDCaught before you file
- 10070An initial Payment Data message can only contain new dataCaught before you file
- 10080A correction message can only contain corrections and/or deletionsCaught before you file
- 10090The message is not a payment data messageCaught before you file
- 10100The reporting period cannot be updatedOnly CESOP can raise it
- 10110CorrMessageRefId wrongly used in MessageSpecCaught before you file
- 10120Wrong TransmittingCountryPartly caught before you file
20xxx · Payee references and the reporting PSP
DocSpec references on each payee, and the Reporting PSP's identifier.
- 20010DocRefID is not unique within the messageCaught before you file
- 20020DocRefID is not unique within the systemOnly CESOP can raise it
- 20030Wrong DocRefID formatCaught before you file
- 20040Wrong CorrDocRefId valuePartly caught before you file
- 20050CorrDocRefId for new dataCaught before you file
- 20060Missing CorrDocRefIdCaught before you file
- 20070CorrDocRefId no longer validOnly CESOP can raise it
- 20100Invalid PSP's BIC formatCaught before you file
- 20110Missing ReportedPayeeCaught before you file
30xxx · Representative
The PSP acting for a payee who holds no payment account.
40xxx · Reported payee
Who received the payments: account identifiers, representative, cross-border test.
- 40010The reported transaction does not represent cross-border paymentCaught before you file
- 40020Wrong IBAN formatCaught before you file
- 40030IBAN is not validCaught before you file
- 40040ReportedPayee listed in the No Payment Data for the requested period messageCaught before you file
- 40050The 'ReportedTransaction' element is missingCaught before you file
- 40060Discrepancy in the 'AccountIdentifier' attributesCaught before you file
- 40070Invalid Representative's BIC formatCaught before you file
- 40080Discrepancy between 'AccountIdentifier' and 'Representative'Caught before you file
45xxx · Reported transaction
Each payment: amount, refund sign, dates and identifiers.
- 45010Wrong value of the 'IsRefund' element in the 'AmountCurrency' elementCaught before you file
- 45030The 'DateTime' element refers to a wrong valueCaught before you file
- 45040The 'TransactionIdentifier' element is not unique within the Payment Data messageCaught before you file
- 45050The 'TransactionIdentifier' element is not unique within the systemOnly CESOP can raise it
- 45060Zero value for 'Amount' elementCaught before you file
- 45080Same transaction date provided more than onceCaught before you file
50xxx · The file itself
Well-formedness, size and the error ceiling.
Find these before CESOP does
A rejected quarter means resubmitting under a deadline. The validator runs the same rules against your file first and names the CESOP error each finding would become — 33 of the 39 codes above.
The file is parsed in your browser tab. No upload, no account.
Source: the error catalogue in the Payment Data XSD User Guide — CESOP, v4.40 (DG TAXUD), §2.2.3.18, quoted as published. The explanations are ours; they describe the file format and are not tax advice.