<\/span><\/p>\n<\/p>\n
Translated into less legal language: this is not a dramatic shift in the regulation, but it is an important clarification, especially with inspections, incidents, and possible penalties in mind.<\/p>\n[\/vc_column_text][vc_column_text css=”” text_direction=”default”]\n
How responsibility for the DCA is now allocated<\/h3>\n <\/p>\n
The current wording of Article 7 sets out the allocation as follows:<\/p>\n
1. The contractual shipper is responsible for the shipment data<\/h4>\n <\/p>\n
The contractual shipper is responsible for inaccuracies or missing data in sections a), b), c) and d)<\/b><\/span> of Article 6 of the order. In other words, it is responsible for: its own identification, the identification of the actual carrier, the origin and destination of the shipment, and the nature and weight of the goods. It is also responsible for any observations or notes it includes in relation to section h). <\/span><\/p>\n2. The actual carrier is responsible for the execution of the transport<\/h4>\n <\/p>\n
The actual carrier is responsible for inaccuracies or missing data in sections e), f) and g)<\/b><\/span> of Article 6. This includes any special transport authorization where applicable, the date the transport is carried out, and the registration number of the vehicle used. Likewise, it is responsible for any observations or notes it includes in relation to section h). <\/span><\/p>\n3. There is also a basic shared responsibility<\/h4>\n <\/p>\n
The regulation also maintains one key point: both the contractual shipper and the actual carrier are responsible if the control document is not formalized<\/b><\/span>. They will also be responsible if the document is not carried on board the vehicle, unless the contractual shipper can prove that the document was issued, in which case it will be exempt. <\/span><\/p>\n<\/p>\n
Put simply: one thing is who is responsible for each specific piece of data, and another is who is responsible for ensuring that the document exists and accompanies the transport. On that latter point, responsibility remains shared.<\/p>\n[\/vc_column_text][image_with_animation image_url=”2456″ image_size=”full” max_width=”100%” max_width_mobile=”default” animation_type=”entrance” animation=”None” animation_movement_type=”transform_y” hover_animation=”none” alignment=”center” border_radius=”none” box_shadow=”none” image_loading=”default”][vc_column_text css=”” text_direction=”default”]\n
So, if there are errors, who is actually exposed?<\/h3>\n <\/p>\n
It depends on the error.<\/p>\n
<\/p>\n
If an inspection detects a problem in data such as the origin, destination, nature of the goods, or their weight, the focus will fall on the contractual shipper<\/b><\/span>, because those are data points expressly assigned to it by the regulation. If the issue affects the date of transport, the vehicle registration number, or the special transport authorization, responsibility will fall on the actual carrier<\/b><\/span>. And if the problem is that there is no DCA at all or that it is not carried on board, responsibility may extend to both parties. <\/span><\/p>\n<\/p>\n
This nuance is what truly changes the conversation. It is no longer enough to think, \u201clet the driver carry it and that\u2019s it.\u201d Now, traceability regarding who provided which data and at what point becomes much more relevant. <\/span><\/p>\nAnd what about penalties?<\/h3>\n <\/p>\n
Here it is important not to mix things up. The March 2026 order clarifies how responsibility is allocated, but it does not by itself create a new specific penalty framework for each piece of DCA data<\/b><\/span>. The risk of penalties must be read together with the LOTT<\/b><\/span> and the rest of the control and inspection framework. <\/span><\/p>\n<\/p>\n
The Land Transport Regulation Act<\/b><\/span> classifies as a serious infringement the absence, lack of formal completion, or lack of essential data in the mandatory control documentation. In addition, the same law establishes that administrative control documents must be carried on board the vehicle while the service is being performed. <\/span><\/p>\n<\/p>\n
As for the financial range, Article 143 of the LOTT sets out penalties of \u20ac801 to \u20ac1,000<\/b><\/span> for certain serious infringements under Article 141, and among them are points 27 and 28 of that article. <\/span><\/p>\n<\/p>\n
That said, there is an important detail here: that specific reference to Article 141.28 is linked to the failure to formalize the consignment note or the ongoing contract in writing<\/b><\/span> when mandatory, not to every possible DCA error. That is why the prudent approach is not to promise a fixed amount for every scenario, but to understand that the risk of penalties does exist and will depend on the type of breach and how exactly it fits into the applicable penalty regime. <\/span><\/p>\n<\/p>\n
The practical conclusion is far less legalistic and much more useful: if it is unclear who was supposed to provide a piece of data, if there is no evidence of when it was added, or if the document is not properly available during an inspection, then the problem is no longer just operational. It may also be sanctionable.<\/p>\n[\/vc_column_text][vc_column_text css=”” text_direction=”default”]\n
Why this matters even more now<\/h3>\n <\/p>\n
Because the timeline is getting tight.<\/p>\n
<\/p>\n
Law 9\/2025<\/b><\/span> establishes that the administrative control document for public road freight transport must be necessarily digital<\/b><\/span> ten months after the law enters into force. That places the change in October 2026<\/b><\/span>. <\/span><\/p>\n<\/p>\n
And when an obligation moves from paper to a digital environment, one old excuse in the sector disappears: \u201cwe\u2019ll fill it in later,\u201d \u201csomeone else had it,\u201d or \u201cthe other party was dealing with that.\u201d In digital form, either the data is there, or it isn\u2019t. Either it is recorded who provided it, or it isn\u2019t. And at that point, responsibility<\/b><\/span> stops being a theoretical discussion and becomes something quite tangible. <\/span><\/p>\nWhat shippers and carriers should already be reviewing<\/h3>\n <\/p>\n
At this point, continuing to treat the DCA as if it were an isolated task of the carrier is basically buying yourself a ticket to problems later on.<\/p>\n
<\/p>\n
The sensible thing is to review three issues from now on:<\/p>\n
<\/p>\n
First<\/b><\/span>, which data must be provided by each party and who validates each field before transport begins. The regulation already separates this quite clearly. <\/span><\/p>\n<\/p>\n
Second<\/b><\/span>, how to prove that the document has been issued and that it accompanies the transport. Because on that point, responsibility may extend to both parties. <\/span><\/p>\n<\/p>\n
Third<\/b><\/span>, how to leave a trace of contributions, corrections, and validations. Not only to work better, but also to be in a better position to defend yourself if there is an inspection or a later dispute. This is no longer just about \u201chaving a document\u201d; it is about being able to prove the documentary process. That is the part that is often forgotten until the problem arrives. The takeaway here is operational, but it fits with the legal allocation of responsibilities established by the regulation itself.<\/p>\n[\/vc_column_text][vc_column_text css=”” text_direction=”default”]\nWhat Orus Logistics can contribute in this new scenario<\/h2>\n <\/p>\n
At Orus Logistics, we are working so that both the contractual shipper<\/b><\/span> and the actual carrier<\/b><\/span> can comply simply and quickly with the part that corresponds to them within the DCA documentary process.<\/p>\n <\/p>\n
The idea is clear: that each party provides its information, that the process is documented, and that there is traceability as to who added each piece of data and when they did so. Not to fill operations with digital bureaucracy, but quite the opposite: to reduce friction, avoid errors, and arrive better prepared for an environment in which the control document will be mandatorily electronic. This last part is an Orus value proposition, not a literal requirement of the BOE. The regulatory framework does require the digital DCA in October 2026 and defines the responsibilities of each actor. <\/span><\/p>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row type=”in_container” full_screen_row_position=”middle” column_margin=”default” column_direction=”default” column_direction_tablet=”default” column_direction_phone=”default” bg_color=”#EAEAEA” scene_position=”center” top_padding=”4%” bottom_padding=”4%” left_padding_desktop=”4%” right_padding_desktop=”4%” top_padding_phone=”15%” bottom_padding_phone=”15%” text_color=”dark” text_align=”left” row_border_radius=”20px” row_border_radius_applies=”bg” row_position_desktop=”default” row_position_tablet=”inherit” row_position_phone=”inherit” overflow=”visible” overlay_strength=”0.3″ gradient_direction=”left_to_right” shape_divider_position=”bottom” bg_image_animation=”none” gradient_type=”default” shape_type=””][vc_column column_padding=”no-extra-padding” column_padding_tablet=”inherit” column_padding_phone=”inherit” column_padding_position=”all” flex_gap_desktop=”10px” column_element_direction_desktop=”default” column_element_spacing=”default” centered_text=”true” desktop_text_alignment=”default” tablet_text_alignment=”default” phone_text_alignment=”default” background_color_opacity=”1″ background_hover_color_opacity=”1″ column_backdrop_filter=”none” column_shadow=”none” column_border_radius=”none” column_link_target=”_self” column_position=”default” gradient_direction=”left_to_right” overlay_strength=”0.3″ width=”1\/1″ tablet_width_inherit=”default” animation_type=”default” bg_image_animation=”none” border_type=”simple” column_border_width=”none” column_border_style=”solid” column_padding_type=”default” gradient_type=”default”][vc_column_text css=”” text_direction=”default”]\nDo you want to try creating the digital DCA?<\/h3>\n <\/p>\n
Request your exclusive access to the trial.<\/p>\n
<\/p>\n
\n\tNotice: JavaScript is required for this content.<\/noscript>\n