10xxx · Message header
CESOP error 10110
“CorrMessageRefId wrongly used in MessageSpec”
Caught before you file
What it means
MessageSpec carries a CorrMessageRefId, but the message is not a correction. The element names the message being corrected, so it belongs only in a CESOP101 message.
Why files get it
- A template for correction messages reused for a regular filing.
How to fix it
- Remove CorrMessageRefId from new-data (CESOP100) and no-data (CESOP102) messages.
Check a file for 10110 before you submit
The free validator runs the CESOP business rules against your file and names the error each finding would become — 10110 included — so the Validation Result is not where you first hear about it.
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. The explanation is ours; it describes the file format and is not tax advice.