1.1.
The central hub will provide both synchronous and asynchronous interfaces for the exchange of messages. Member States may choose the most suitable technology to interface with their own applications.
1.2.
All messages exchanged between the central hub and the national systems must be UTF-8 encoded.
1.3.
Member States will ensure that their national systems can receive and process messages containing Greek or Cyrillic characters.
2.1.
The general structure of XML messages shall follow the format defined by the XSD schemas installed in the central hub.
2.2.
The central hub and the national systems shall transmit and receive messages that conform to the message XSD schema.
2.3.
National systems will be capable of sending, receiving and processing all messages corresponding to any of the functionalities set out in Annex II.
2.4.
The XML messages shall include at least the minimum requirements laid down in the Appendix to this Annex.
Common Header | Mandatory
Version | The official version of the XML specifications will be specified through the namespace defined in the message XSD and in the version attribute of the Header element of any XML message. The version number (‘n.m’) will be defined as fixed value in every release of the XML Schema Definition file (xsd). | Yes
Test Identifier | Optional id for testing. The originator of the test will populate the id and all participants in the workflow will forward/return the same id. In production it should be ignored and will not be used if it is supplied. | No
Technical Identifier | A UUID uniquely identifying each individual message. The sender generates a UUID and populates this attribute. This data is not used in any business capacity. | Yes
Workflow Identifier | The workflowId is a UUID and should be generated by the requesting Member State. This id is then used in all messages to correlate the workflow. | Yes
Sent At | The date and time (UTC) that the message was sent. | Yes
Timeout | This is an optional date and time (in UTC format) attribute. This value will be set only by the central hub for forwarded requests and is calculated based on the date/time the initial request has been received by the central hub. This will inform the responding Member State of the time when the request will be timed out. This value is not required in initial requests sent to the central hub and all response messages. | No
From | The ISO 3166-1 Alpha 2 code of the Member State sending the message or ‘EU’. | Yes
To | The ISO 3166-1 Alpha 2 code of the Member State to which the message is being sent or ‘EU’. | Yes
Check Good Repute Request | Mandatory
Business Case Identifier | A serial or reference number identifying each individual request. | Yes
Requesting Competent Authority | The competent authority that has issued the search request. | Yes
Transport Manager Details | Yes, if no CPC details
Family Name | Transport manager’s family name(s) as indicated on the CPC. | Yes
First Name | Transport manager’s complete given name as indicated on the certificate of professional competence. | Yes
Date of Birth | Transport manager’s birth date in ISO 8601 format (YYYY-MM-DD). | Yes
Place of Birth | Transport manager’s place of birth. | No
Address | The address, city, postcode and country of the transport manager. | No
CPC Details | Yes, if no transport manager details
CPC Number | Number of certificate of professional competence | Yes
CPC Issue Date | Date of issuance of the CPC, in ISO 8601 format (YYYY-MM-DD). | Yes
CPC Issue Country | Issuing country of the CPC in ISO 3166-1 alpha 2 format. | Yes
Check Good Repute Response | Mandatory
Business Case Identifier | A serial or reference number matching the business case identifier of the request. | Yes
Requesting Competent Authority | The competent authority that has issued the search request. | Yes
Responding Competent Authority | The competent authority that has responded to the search request. | Yes
Status Code | The status code of the search (e.g. found, not found, error, etc.). | Yes
Status Message | An explanatory status description (if necessary). | No
Found Transport Manager Details | Yes if Status Code is Found
Family Name | Transport manager’s family name(s) as recorded in the register. | Yes
First Name | Transport manager’s complete given name as recorded in the register. | Yes
Date of Birth | Transport manager’s birth date in ISO 8601 format (YYYY-MM-DD) as recorded in the register. | Yes
Place of Birth | Transport manager’s place of birth as recorded in the register. | No
CPC Number | Number of certificate of professional competence as recorded in the register. | Yes
CPC Issue Date | Date of issuance of the CPC, in ISO 8601 format (YYYY-MM-DD) as recorded in the register. | Yes
CPC Issue Country | Issuing country of the CPC in ISO 3166-1 alpha 2 format as recorded in the register. | Yes
CPC Validity | Declaration of either ‘Valid’ or ‘Invalid’ | Yes
Total Managed Undertakings | The number of transport undertakings with which the transport manager is associated. | Yes
Total Managed Vehicles | The total number of vehicles with which the transport manager is associated. | Yes
Fitness | Declaration of either ‘Fit’ or ‘Unfit’. | Yes
Start Date of Unfitness | Start date of unfitness of the transport manager in ISO 8601 format (YYYY-MM-DD). | Yes if ‘Fitness’ is ‘Unfit’.
End Date of Unfitness | End date of unfitness of the transport manager in ISO 8601 format (YYYY-MM-DD). | Yes if ‘Fitness’ is ‘Unfit’.
Search Method | The method used to find the transport manager: NYSIIS, CPC, Custom. | Yes
Transport Undertaking (for each found Transport Manager) | Yes if Managed Undertakings > 0
Transport Undertaking Name | The name of the transport undertaking (name and legal form) as recorded in the register. | Yes
Transport Undertaking Address | The address of the transport undertaking (address, postal code, city, country) as recorded in the register. | Yes
Community Licence Number | The serial number of the Community licence of the transport undertaking (free text alphanumeric field with length 1 to 20). | Yes
Community Licence Status | The status of the community licence of the transport undertaking as recorded in the register. | Yes
Managed Vehicles | The number of vehicles managed as recorded in the register. | Yes
[Commission Regulation (EU) 2016/403 of 18 March 2016 supplementing Regulation (EC) No 1071/2009 of the European Parliament and of the Council with regard to the classification of serious infringements of the Union rules, which may lead to the loss of good repute by the road transport operator, and amending Annex III to Directive 2006/22/EC of the European Parliament and of the Council (OJ L 74, 19.3.2016, p. 8).]
Notification of Check Result | Mandatory
Business Case Identifier | A serial or reference number identifying each individual notification. | Yes
Notifying Competent Authority | The competent authority that issues the notification. | Yes
Transport Undertaking | Yes
Transport Undertaking Name | The name of the transport undertaking being object of the check. | Yes
Community Licence Number | The serial number of the community licence or of the certified true copy of the transport undertaking (free text alphanumeric field with length 1 to 20). | Yes
Vehicle Registration Number | The vehicle registration number of the vehicle checked | Yes
Vehicle Registration Country | The country in which the vehicle checked is registered | Yes
General information about the check |
Date of check | Date of check in ISO 8601 format (YYYY-MM-DD) | Yes
Clean check | Yes/No | Yes
Minor infringements | Yes, if minor infringement(s) detected during the check
Date of minor infringement | Date of the infringement in ISO 8601 format (YYYY-MM-DD) | Yes
Number of minor infringements | The number of minor infringements detected. | Yes
Serious infringement | Yes, if serious infringement detected during the check
Date of Infringement | Date of the infringement in ISO 8601 format (YYYY-MM-DD) | Yes
Category |
The category of the infringement:
MSI: Most serious infringement
VSI: Very serious infringement
SI: Serious infringement
Yes
Infringement Type | In accordance with the classification provided in Annex IV to Regulation (EC) No 1071/2009 and Annex I to Commission Regulation No (EU) 2016/403 | Yes
Appeal Possible |
If an appeal against the infringement is still possible at the time of notification.
Yes/No
Yes
Penalty Imposed (for each serious infringement) | Yes, if relevant
Penalty Imposed Identifier | The serial number of the individual penalty imposed. | Yes
Final Decision Date | The final decision date of the penalty imposed in ISO 8601 format (YYYY-MM-DD). | Yes
Penalty Type Imposed |
Declaration of either:
101: ‘Warning’
201: ‘Temporary ban on cabotage operations’
202: ‘Fine’
203: ‘Prohibition’
204: ‘Immobilisation’
102: ‘Other’
Yes
Start Date | The start date of the penalty imposed in ISO 8601 format (YYYY-MM-DD) | No
End Date | The end date of the penalty imposed in ISO 8601 format (YYYY-MM-DD) | No
Executed | Yes/No | Yes
Penalty Requested (for each Serious Infringement) | No
Penalty Requested Identifier | The serial number of the individual penalty requested. | Yes
Penalty Type Requested |
Declaration of either:
101: ‘Warning’
301: ‘Temporary withdrawal of some or all of the certified true copies of the Community licence’
302: ‘Permanent withdrawal of some or all of the certified true copies of the Community licence’
303: ‘Temporary withdrawal of the Community licence’
304: ‘Permanent withdrawal of the Community licence’
305: ‘Suspension of the issue of driver attestations’
306: ‘Withdrawal of driver attestations’
307: ‘Issue of driver attestations subject to additional conditions in order to prevent misuse’
Yes
Duration | The duration of the requested penalty (calendar days). | No
Notification of Check Result Response | Mandatory, if infringement(s) detected during the check
Business Case Identifier | A serial or reference number matching the business case identifier of the notification. | Yes
Originating Competent Authority | The competent authority that issued the original infringement notification. | Yes
Licensing Competent Authority | The competent authority responding to the infringement notification. | Yes
Status Code | The status code of the infringement response (e.g. found, not found, error, etc.). | Yes
Status Message | An explanatory status description (if necessary). | No
Transport Undertaking | Yes
Transport Undertaking Name | The name of the transport undertaking as recorded in the register. | Yes
Transport Undertaking Address | The address of the transport undertaking (address, postal code, city, country) as recorded in the register. | Yes
Community Licence Number | The serial number of the community licence of the transport undertaking as recorded in the register (free text alphanumeric field with length 1 to 20). | Yes
Community Licence Status | The status of the community licence of the transport undertaking as recorded in the register. | Yes
Penalty Imposed | No
Penalty Imposed Identifier | The serial number of the individual penalty imposed (given in the Penalty Requested Identifier of the Notification of Check Result). | Yes
Competent Authority Imposing Penalty | The name of the competent authority imposing the penalty. | Yes
Is Imposed | Yes/No | Yes
Penalty Type Imposed |
Declaration of either:
101: ‘Warning’
301: ‘Temporary withdrawal of some or all of the certified true copies of the Community licence’
302: ‘Permanent withdrawal of some or all of the certified true copies of the Community licence’
303: ‘Temporary withdrawal of the Community licence’
304: ‘Permanent withdrawal of the Community licence’
305: ‘Suspension of the issue of driver attestations’
306: ‘Withdrawal of driver attestations’
307: ‘Issue of driver attestations subject to additional conditions in order to prevent misuse’
102: ‘Other’
Yes
Start Date | The start date of the penalty imposed in ISO 8601 format (YYYY-MM-DD). | No
End Date | The end date of the penalty imposed in ISO 8601 format (YYYY-MM-DD). | No
Reason | Reason if penalty is not imposed. | No
Notification of Check Result Acknowledgement | Mandatory
Business Case Identifier | A serial or reference number matching the business case identifier of the notification or the response. | Yes
Status Code | Status code of the acknowledgement. | Yes
Status Message | Status Message String | No
Originating Competent Authority |
For a NCRN_Ack: in the legislation this field is represented as ‘Destination Competent Authority Identifier’.
For a NCRR_Ack: in the legislation this field is represented as ‘Acknowledging Competent Authority Identifier’.
Yes
Licensing Competent Authority |
For a NCRN_Ack: in the legislation this field is represented as ‘Acknowledging Competent Authority Identifier’.
For a NCRR_Ack: in the legislation this field is represented as ‘Destination Competent Authority Identifier’.
Yes
Acknowledgement Type |
Defining Acknowledgement Type
Possible Values:
‘NCRN_Ack’
‘NCRR_Ack’
Yes
Check Transport Undertaking Data Request | Mandatory
Business Case Identifier | A serial or reference number identifying each individual request. | Yes
Originating Competent Authority | The competent authority issuing the search request. | Yes
Transport Undertaking Identification | Yes
Transport Undertaking Name | The name of the transport undertaking. | At least two of the search fields are required.
Community Licence Number | The serial number of the community licence or of the certified true copy (free text alphanumeric field with length 1 to 20).
Vehicle Registration Number | The registration number of one of the vehicles of the transport undertaking.
Vehicle Registration Country | The country of registration of the vehicle. | Yes, if vehicle registration number provided.
Request All Vehicles |
To request the registration numbers of all vehicles managed by the undertaking.
Yes/No
Yes
Check Transport Undertaking Data Response | Mandatory
Business Case Identifier | A serial or reference number identifying each individual request | Yes
Originating Competent Authority | The competent authority issuing the search request. | Yes
Responding Competent Authority | The competent authority providing the response. | Yes
Status Code | The status code of the response (e.g. found, not found, error, etc.). | Yes
Status Message | An explanatory status description (if necessary). | No
General Information about the Transport Undertaking | Yes, if status code is found
Transport Undertaking Name | The name of the transport undertaking (name and legal form). | Yes
Transport Undertaking Address | The address of the transport undertaking (address, postal code, city, country) as recorded in the register | Yes
Number of Managed Vehicles | The number of vehicles managed as recorded in the register. | Yes
Number of People Employed | The number of people employed in the undertaking on last 31 December. | Yes
Risk Rating | The risk rating of the undertaking. | Yes
Risk Rating Band | The risk rating band of the undertaking (green, amber, red, grey). | Yes
Community Licence Details | Yes, if status code is found
Licencing Competent Authority | The competent authority that issued the community licence to the transport undertaking | Yes
Community Licence Number | The serial number of the community licence of the transport undertaking as recorded in the register (free text alphanumeric field with length 1 to 20) | Yes
Licence Status | The status of the community licence of the transport undertaking as recorded in the register | Yes
Licence Type |
The type of the community licence as recorded in the register. A declaration of:
‘Community licence for passenger transport’
‘National licence for passenger transport’
‘Community licence for goods transport’
‘Community licence for goods transport, exclusively ≤ 3,5 t’
‘National licence for goods transport’
Yes
Start Date | The start date of the community licence | Yes
Expiry Date | The expiry date of the community licence | Yes
Withdrawal Date | The withdrawal date of the community licence | Yes, if found
Suspension Date | The suspension date of the community licence | Yes, if found
Suspension Expiry Date | The date on which the community licence suspension expires | Yes, if found
Certified True Copy Details | Yes
Certified True Copy Number | The serial number of each certified true copy of the community licence of the transport undertaking as recorded in the register (free text alphanumeric field with length 1 to 20) | Yes
Start Date | The start date of each certified true copy of the community licence. | Yes
Expiry Date | The expiry date of each certified true copy of the community licence. | Yes
Withdrawal Date | The withdrawal date of each certified true copy of the community licence. | Yes, if found
Suspension Date | The suspension date of the certified true copy of the community licence. | Yes, if found
Suspension Expiry Date | The date on which each certified true copy of the community licence suspension expires. | Yes, if found
Vehicle Details | Yes, if value of ‘Request All Vehicles’ in CTUD Request is ‘Yes’.
Vehicle Registration Number | The registration number of each of the vehicles of the transport undertaking | Yes
Vehicle registration country | The registration country of each of the vehicles of the transport undertaking. | Yes
Notification of Unfitness | Mandatory
Business Case Identifier | A serial or reference number identifying each individual notification. | Yes
Notifying Competent Authority | The competent authority that issues the notification. | Yes
Transport Manager Details | Yes, if no CPC details
Family Name | Transport manager’s family name(s) as indicated on the CPC. | Yes
First Name | Transport manager’s complete given name as indicated on the certificate of professional competence. | Yes
Date of Birth | Transport manager’s birth date in ISO 8601 format (YYYY-MM-DD). | Yes
Place of Birth | Transport manager’s place of birth. | No
CPC Details | Yes, if no transport manager details
CPC Number | Number of certificate of professional competence | Yes
CPC Issue Date | Date of issuance of the CPC, in ISO 8601 format (YYYY-MM-DD). | Yes
CPC Issue Country | Issuing country of the CPC in ISO 3166-1 alpha 2 format. | Yes
Declaration of Unfitness | Yes
Start Date of Unfitness | Start date of unfitness, in ISO 8601 format (YYYY-MM-DD). | Yes
Notification of Unfitness Acknowledgement | Mandatory
Business Case Identifier | A serial or reference number matching the business case identifier of the notification. | Yes
Originating Competent Authority | The competent authority issuing the notification. | Yes
Responding Competent Authority | The competent authority providing the acknowledgement. | Yes
Status Code | Status code of the acknowledgement. | Yes
Status Message | Status Message String | No