OpenLegislation

Appendix

United Kingdom

Changes not yet applied. Later legislation changes this provision in ways not yet written into the text below:

Minimum requirements for the content of the XML messages

Common HeaderMandatory
VersionThe 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 IdentifierOptional 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 IdentifierA 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 IdentifierThe 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 AtThe date and time (UTC) that the message was sent.Yes
F1Timeout 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
FromThe ISO 3166-1 Alpha 2 code of the Member State sending the message or ‘EU’.Yes
ToThe ISO 3166-1 Alpha 2 code of the Member State to which the message is being sent or ‘EU’.Yes

Check Good Repute

Check Good Repute RequestMandatory
Business Case IdentifierA serial or reference number identifying each individual request.Yes
Requesting Competent AuthorityThe competent authority that has issued the search request.Yes
Transport Manager Details Yes, if no CPC details
Family NameTransport manager's family name(s) as indicated on the CPC.Yes
First NameTransport manager's complete given name as indicated on the certificate of professional competence.Yes
Date of BirthTransport manager's birth date in ISO 8601 format (YYYY-MM-DD).Yes
Place of BirthTransport manager's place of birth.No
CPC Details Yes, if no transport manager details
CPC NumberNumber of certificate of professional competenceYes
CPC Issue DateDate of issuance of the CPC, in ISO 8601 format (YYYY-MM-DD).Yes
CPC Issue CountryIssuing country of the CPC in ISO 3166-1 alpha 2 format.Yes
Check Good Repute ResponseMandatory
Business Case IdentifierA serial or reference number matching the business case identifier of the request.Yes
Requesting Competent AuthorityThe competent authority that has issued the search request.Yes
Responding Competent AuthorityThe competent authority that has responded to the search request.Yes
Status CodeThe status code of the search (e.g. found, not found, error, etc.).Yes
Status MessageAn explanatory status description (if necessary).No
Found Transport Manager Details Yes if Status Code is Found
Family NameTransport manager's family name(s) as recorded in the register.Yes
First NameTransport manager's complete given name as recorded in the register.Yes
Date of BirthTransport manager's birth date in ISO 8601 format (YYYY-MM-DD) as recorded in the register.Yes
Place of BirthTransport manager's place of birth as recorded in the register.Yes
CPC NumberNumber of certificate of professional competence as recorded in the register.Yes
CPC Issue DateDate of issuance of the CPC, in ISO 8601 format (YYYY-MM-DD) as recorded in the register.Yes
CPC Issue CountryIssuing country of the CPC in ISO 3166-1 alpha 2 format as recorded in the register.Yes
Total Managed UndertakingsThe number of transport undertakings with which the transport manager is associated.Yes
Total Managed VehiclesThe total number of vehicles with which the transport manager is associated.Yes
FitnessDeclaration of either ‘Fit’ or ‘Unfit’.Yes
End Date of UnfitnessEnd date of unfitness of the transport manager in ISO 8601 format (YYYY-MM-DD). Applicable if the Fitness is unfit.No
Search MethodThe 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 NameThe name of the transport undertaking (name and legal form) as recorded in the register.Yes
Transport Undertaking AddressThe 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 StatusThe status of the community licence of the transport undertaking as recorded in the register.Yes
Managed VehiclesThe number of vehicles managed as recorded in the register.Yes

Infringement Notification

Infringement Notification RequestMandatory
Business Case IdentifierA serial or reference number identifying each individual request.Yes
Notifying AuthorityThe competent authority that issues the infringement notification.Yes
Transport Undertaking Yes
Transport Undertaking NameThe name of the transport undertaking against which the infringement is being recorded.Yes
Community Licence Number The serial number of the certified true copy or of the Community licence of the transport undertaking (free text alphanumeric field with length 1 to 20). Yes
Vehicle Registration NumberThe Vehicle registration number of the offending vehicle.Yes
Vehicle Registration CountryThe country in which the vehicle is registered.Yes
Serious Infringement Yes
Date of InfringementDate 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 TypeIn accordance with the classification provided in Annex IV to Regulation (EC) No 1071/2009 and Annex I to Regulation (EU) 2016/403Yes
Date of CheckThe date of the check at which infringement has been ascertained in ISO 8601 format (YYYY-MM-DD).Yes
Penalty Imposed (for each Serious Infringement) Yes
Penalty Imposed IdentifierThe serial number of the individual penalty imposed.Yes
Final Decision DateThe 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 DateThe start date of the penalty imposed in ISO 8601 format (YYYY-MM-DD)No
End DateThe end date of the penalty imposed in ISO 8601 format (YYYY-MM-DD)No
Is ExecutedYes/NoYes
Penalty Requested (for each Serious Infringement) No
Penalty Requested IdentifierThe 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
DurationThe duration of the requested penalty (calendar days).No
Infringement Notification ResponseMandatory
Business Case IdentifierA serial or reference number matching the business case identifier of the request.Yes
Originating AuthorityThe competent authority that issued the original infringement notification.Yes
Licensing AuthorityThe competent authority responding to the infringement notification.Yes
Status CodeThe status code of the infringement response (e.g. found, not found, error, etc.).Yes
Status MessageAn explanatory status description (if necessary).No
Transport Undertaking Yes
Transport Undertaking NameThe name of the transport undertaking as recorded in the register.Yes
F2Transport 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
Managed Vehicles The number of vehicles managed as recorded in the register. Yes
Penalty Imposed No
Penalty Imposed IdentifierThe serial number of the individual penalty imposed (given in the Penalty Requested Identifier of the Infringement Notification).Yes
Authority Imposing PenaltyThe name of the authority imposing penalty.Yes
Is ImposedYes/NoYes
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 DateThe start date of the penalty imposed in ISO 8601 format (YYYY-MM-DD).No
End DateThe end date of the penalty imposed in ISO 8601 format (YYYY-MM-DD).No
ReasonReason if penalty is not imposed.No
Infringement Notification AcknowledgementMandatory
Business Case IdentifierA serial or reference number matching the business case identifier of the notification or the response.Yes
Status CodeStatus code of the acknowledgement.Yes
Status MessageStatus Message StringNo
Originating Authority

For an IN_Ack: in the legislation this field is represented as ‘Destination Competent Authority Identifier’.

For an IR_Ack: in the legislation this field is represented as ‘Acknowledging Competent Authority Identifier’.

Yes
Licensing Authority

For an IN_Ack: in the legislation this field is represented as ‘Acknowledging Competent Authority Identifier’.

For an IR_Ack: in the legislation this field is represented as ‘Destination Competent Authority Identifier’.

Yes
Acknowledgement Type

Defining Acknowledgement Type

Possible Values:

  • ‘IN_Ack’

  • ‘IR_Ack’

Yes

Check Community Licence

Check Community Licence RequestMandatory
Business Case IdentifierA serial or reference number identifying each individual request.Yes
Originating AuthorityThe authority issuing the search request.No
Transport Undertaking Yes
Transport Undertaking NameThe name of the transport undertaking for which the community licence details are requested.Yes
Community Licence Number The serial number of the certified true copy or of the community licence for which the details are requested (free text alphanumeric field with length 1 to 20). Yes
Vehicle Registration NumberThe vehicle registration number for which the certified true copy of the community licence is issued.No
Check Community Licence ResponseMandatory
Business Case IdentifierA serial or reference number identifying each individual request.Yes
Originating AuthorityThe authority that issued the search request.No
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
Transport Undertaking Yes if status code is Found
Transport Undertaking NameThe name of the transport undertaking (name and legal form) as recorded in the register.Yes
Transport Undertaking AddressThe address of the transport undertaking (address, postal code, city, country) as recorded in the register.Yes
Community Licence Details Yes, if status code is Found
Licencing Authority The authority that issued the community licence to the transport undertaking. Yes
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’

  • ‘National licence for goods transport’

Yes
Start DateThe start date of the community licence.Yes
Expiry DateThe expiry date of the community licence.Yes
Withdrawal DateThe withdrawal date of the community licence.No
Suspension DateThe suspension date of the community licence.No
Suspension Expiry DateThe date on which the community licence suspension expires.No
Managed VehiclesThe number of vehicles managed as recorded in the register.Yes
Certified True Copy Details No
Certified True Copy Number The serial number of the 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
F3
Expiry DateThe expiry date of the certified true copy of the community licence.Yes
Withdrawal DateThe withdrawal date of the certified true copy of the community licence.No
Withdrawal Expiry Date The date on which the certified true copy of the community licence withdrawal expires. No

Annotations

Textual amendments

F1

Substituted by Commission Implementing Regulation (EU) 2017/1440 of 8 August 2017 amending Implementing Regulation (EU) 2016/480 establishing common rules concerning the interconnection of national electronic registers on road transport undertakings (Text with EEA relevance).

F2

Inserted by Commission Implementing Regulation (EU) 2017/1440 of 8 August 2017 amending Implementing Regulation (EU) 2016/480 establishing common rules concerning the interconnection of national electronic registers on road transport undertakings (Text with EEA relevance).

F3

Deleted by Commission Implementing Regulation (EU) 2017/1440 of 8 August 2017 amending Implementing Regulation (EU) 2016/480 establishing common rules concerning the interconnection of national electronic registers on road transport undertakings (Text with EEA relevance).