CESOP payment data message root element. The MessageSpec element represents the header of the CESOP payment data message. The PaymentDataBody element represents the body of the CESOP payment data message. The ValidationResult element represents the body of the CESOP validation result message. Schema version of the CESOP XSD. The Member State of the national TAX administration through which the Payment data transits (ISO-3166 Alpha 2). The element declares the type of the message like Payment data or Validation result. The element declares if the message contains new data, correction/deletion for previously sent data, or there is no data to report. The Message Reference ID element contains a unique identifier for the message in form of a UUID version 4. The Correlation Message Reference ID element allows correlation of dependent messages. Examples of dependent messages are the following: any message which failed the validation and the related Validation result message, initial Payment data message and the related Correction payment data message. The Sending PSP element uniquely defines the Payment Service Provider, which centralises the submission of the payment data to national TAX administration for its subsidiaries. This element must be omitted if the SendingPSP and the ReportingPSP are the same entity. Article 243d (2a). The Reporting Period element defines the quarter and the year, to which the payment data submitted by the Payment Service Provider refers. The exact date and time when the PSP has generated the message. The Reporting PSP element uniquely defines the Payment Service Provider, which reports the payment data to national TAX administration. The Reported Payee element defines the payee, to which the payment data submitted by Payment Service Provider relates. The 'ReportedPayee' element is repeatable as a PSP can report data from many Payees. This element is mandatory as soon as transactions are reported. It can only be omitted in case there is no transaction to report. Article 243d (1a). The BIC or any other business identifier code that unambiguously identifies the Payment Service Provider. The name of the Payment Service Provider reporting the payment data to national TAX administration. Article 243d (1e). The BIC or any other business identifier code that unambiguously identifies, and gives the location of, the payment service provider acting on behalf of the payee where the payee receives funds without having any payment account. The name of the Representative of the Payee. Article 243d (1b). The name of the Reported Payee company or natural person. Article 243d (1d). The country of the payee's origin (ISO-3166 Alpha 2). Article 243d (1f). The address of the payee as it appears in the records of the payment services provider. From the legal basis, this element must be provided if available. Otherwise it can be empty. The email address of the payee. The web page of the payee. Article 243d (1c). Any VAT identification number or other national tax number of the payee. From the legal basis, this element must be provided if available. Otherwise it can be empty. Article 243d (1d). The IBAN of the payee’s payment account or any other identifier which unambiguously identifies, and gives the location of, the payee. This field is mandatory when funds are transferred to a payment account of the payee. From the legal basis, this element must be provided if available. Otherwise it can be empty. Article 243d (1g and 1h). The parent Reported Transaction element listing all the received payments and payment refunds for the given payee reported by the PSP. This element is optional only in case of deletion of the related Reported Payee. Otherwise the element is mandatory. Article 243d (1e). The payment service provider acting on behalf of the payee where the payee receives funds without having any payment account. This element is mandatory only when the payee receives funds without having a payment account. The DocSpec type defines data to make it possible to correct records in the message. Article 243d (2d). Any reference which unambiguously identifies the payment for the PSP. The reference of the correlated transaction. Used, in case of 'transaction refund', to indicate the reference of the related 'received payment'. Article 243d (2a). The element expresses the date and the time of the related transaction. Article 243d (2b). The amount and the currency of the payment or of the payment refund. The currency code refers to ISO-4217 three-byte alpha version. The payment method used. Article 243d (2e). Information that the payment is initiated at the physical premises of the merchant. The element has a value 'TRUE' if the payment is initiated at the premises of the merchant. Otherwise, the element has a value 'FALSE'. Article 243d (2c). Member State of the payer. The payer is the Principal of the transaction, always located in EU. (ISO-3166 Alpha 2). The role of the Payment Service Provider acting on behalf of the payee. Article 243d (1g and 1h). The element identifies the refund. Value 'FALSE' represents a 'payment', value 'TRUE' represents a 'payment refund'. This attribute is optional. If not provided, the default value 'FALSE' will be assigned. Article 243d (2a). The element represents the quarter to which the payment data refers. Article 243d (2a). The element represents the year to which the payment data refers. Article 243d (1a and 1e). The BIC or any other business identifier code that unambiguously identifies the Payment Service Provider. As the identifier may be not strictly numeric, it is just defined as a string of characters. Attribute 'PSPIdType' defines the type of identification number. Type of identification number. Type of location identifier identifying the country of the Payer. The country code of the location (ISO-3166 Alpha 2). Must be provided only if an account identifier is provided. Type of the location identifier. Must be provided only if an account identifier is provided. Article 243d(1c) If a TAX identifier is available, it must be reported. Otherwise it can be empty. The EU confirmed VAT identification number of the payee. Any taxation identifier of the payee. The message type is 'Payment data' (or 'No Payment data'). The message type is 'Validation result message'. The message contains new data. The message contains corrections or deletions of previously sent data. The message indicates there is no data to report. Indicates if the payment data message has been successfully validated, partially rejected or fully rejected. List of detected errors. Error code related to the error detected during the validation of the related payment data message. Indicates how many times the related error has been raised for the related Payment Data Message, including the current one. Short description of the error code. Full description of the error code. Transaction identifier, which identifies the erroneous transaction. The unique reference of the parent element in form of a UUID version 4. When the error is related to a Reported Payee or a Reported Transaction, this field allows to link the error to the related DocSpec. The message has been positively validated. The message has been partially rejected. The message has been fully rejected. MessageRefID is not unique. The ‘Timestamp’ element refers to a wrong value. The period is before 01/01/2024. Wrong CorrMessageRefID. Wrong format of the MessageRefID. Wrong format of the CorrMessageRefID. An initial Payment Data message can only contain new data. A correction message can only contain corrections and/or deletions. The message is not a payment data message. The reporting period cannot be updated. CorrMessageRefId wrongly used in MessageSpec. Wrong TransmittingCountry DocRefID is not unique within the message. DocRefID is not unique within the system. Wrong DocRefID format. Wrong CorrDocRefId value. CorrDocRefId for new data. Missing CorrDocRefId. CorrDocRefId no longer valid. Invalid PSP's BIC format. Missing ReportedPayee. Business identifier of the Representative is equal to the Business Identifier of the Reporting PSP. The reported transaction does not represent cross-border payment. Wrong IBAN format. IBAN is not valid. ReportedPayee listed in the No payment data for the requested period message. The 'ReportedTransaction' element is missing. Discrepancy in the 'AccountIdentifier' attributes. Invalid Representative's BIC format. Discrepancy between ‘AccountIdentifier’ and ‘Representative’. Wrong value of the ‘IsRefund’ element in the ‘AmountCurrency’ element. The ‘DateTime’ element refers to a wrong value. The ‘TransactionIdentifier’ element is not unique within the Payment data message. The ‘TransactionIdentifier’ element is not unique within the system. Zero value for ‘Amount’ element. Same transaction date provided more than once. The XML message is not well formed. Failed Decryption. Failed Decompression. Failed Signature Check. Failed Threat Scan. Failed Virus Scan. Message size exceeded. Too many errors detected. Custom error.