How Much Is the U-ETDS Penalty? Warning Points [2026]

The answer people expect when they ask what a U-ETDS penalty costs is a sum of money. The system does not work that way. U-ETDS — the Ministry of Transport and Infrastructure's electronic tracking and inspection system — is enforced primarily through warning points (ihtar puanı) recorded against your authorisation certificate (yetki belgesi). An administrative fine exists alongside it, but that is not where the real exposure sits.

The distinction matters: a fine is paid and closed, while a warning point is a balance that sits on your certificate and keeps accumulating.

A second widespread misconception is that the duty follows the vehicle. It follows the authorisation certificate — the K1, K3, C2 or L2 document under which the carriage is performed. Whether the load moves on your own fleet or on a subcontracted vehicle, if the trip runs under your certificate the record is your responsibility.

What happens if a trip is not notified to U-ETDS?

A warning point is recorded against the certificate holder for every trip that goes unreported, and the sanction separates by type of breach: failing to notify and deliberately notifying something false are not in the same basket.

Taking the rows one at a time: a trip that is never notified is written against the certificate holder as a warning point, recorded separately for each breach, so several skipped trips in one week are not consolidated into a single item. A deliberately false or misleading notification attracts a markedly heavier point — the rules draw a line between leaving something out and showing something incorrectly.

Incomplete or incorrect data entry is a different heading, where an administrative fine may be assessed per unit — the one place where money rather than points is the immediate consequence. The last row is the only one working in your favour: closing a three-month period completely, on time and error-free removes part of the balance.

The fourth row is the one most often missed: a rejected record counts as not notified at all — it was sent, but as far as the system is concerned the trip has no record. We looked at where rejections cluster in our article on what to do when your U-ETDS record is rejected.

Why is a warning point heavier than a fine?

Because a fine is the cost of one trip while a warning point is a risk to your certificate. Points accumulate against the certificate, and once certain thresholds are passed it can be temporarily restricted. What speaks then is not the sum you paid but the vehicles standing still in the yard.

The same breach lands differently in two companies: a carrier running few trips that is late with one filing a month grows its balance slowly, while one running a heavy daily schedule with the same lateness accumulates far faster. That is why "everyone else works the way we do" is not a measure of risk: what counts is the total that frequency produces once multiplied by trip volume.

How do I find out my warning point balance?

The balance is held against your authorisation certificate, so you cannot estimate it from your own trip list. That is the mechanism's most uncomfortable feature: the breach happens on your side, while its consequence accumulates where you do not see it. Most companies learn their balance for the first time after an inspection.

The practical answer is not to chase the balance but to cut off the input that feeds it. Two numbers you can hold on your own side: trips run during the month, and records accepted in the system. If they do not match, the difference is a preview of what you will later see on the certificate.

How are accumulated warning points removed?

A company that closes a three-month period completely, on time and error-free has a portion of its previous warning balance removed automatically. The mechanism does not only punish; it rewards a settled routine, which makes being behind a temporary condition rather than a permanent one.

Removal works per period, not per trip. Correcting a single record does not rescue the period; all three conditions have to hold together, which changes the target of remediation: instead of chasing individual records, you build a flow that will not break next period.

What can be done about points already accumulated?

You cannot retroactively turn an unreported trip into a reported one: the notification has to be made before the carriage begins. Cut the input first, then talk about the balance — every month before the flow is fixed keeps adding to it.

The second step is to find where the breakage comes from. Missing notifications and rejections rarely fall at random; they cluster around a particular vehicle, customer or trip type. Fixing the source stops the error repeating, whereas trip-by-trip fixes mean the same work every month.

Why do most penalties come from disconnection rather than forgetfulness?

Because notification is a separate job from the operation, and separate jobs are the ones that fall behind. Nobody skips filings on purpose. There are three typical points of disconnection.

• Time drift. The trip closes in the evening, the filing is entered the next morning. If an inspection falls in between, there is no record.
• The subcontractor gap. The duty follows the authorisation certificate, not who owns the vehicle. A routine built for the own fleet breaks as soon as a subcontracted truck is used.
• Silent rejection. A record that was sent but rejected stays unreported, because nobody looks at the response.

The third is the most insidious: the company believes the filing was made, and the problem only appears at an inspection. Which fields are required, and in what order the filing is made, we set out step by step in our guide on how to make a U-ETDS load notification.

The subcontractor gap is the most expensive of the three, because it grows with volume. With a subcontracted truck the plate arrives at the last minute, the trip is recorded after the vehicle has left and the notification is late — and the consequence is still written against your certificate.

What is checked at an inspection?

At an inspection the documents in the vehicle are compared with the trip record held in the system. But you do not have to be stopped on the road for a gap to surface: missing notifications are equally found in periodic reviews run through the system, and the two routes differ in the period they cover.

Putting the table into sentences: a roadside inspection covers only the trip on the road at that moment; the document on board is compared with the record in the system, any gap is established immediately in a report, and the consequence falls on that single trip. If a valid record exists when the trip is opened, the check passes.

A system-based periodic review covers an entire past period instead. What is examined is not one vehicle on one day but the completeness and timing of the trip records as a whole, so gaps surface later and in bulk — and because the record discipline of a past period cannot be changed afterwards, there is no way to prepare.

The two routes running in parallel is what takes "we have never been stopped" out of the category of reassurance. Inspections also ask for documents beyond the filing; a missing transport waybill arises from different legislation and produces a separate sanction, which we covered in our article on the transport waybill penalty.

How high is your penalty risk?

Risk depends far less on your trip count than on the structure of your notification routine. The matrix below shows which profile sits at which level, and what to fix first.

Reading the rows one by one: a single vehicle running a few trips a week, filed by hand at the moment of the trip, carries low risk and needs no intervention. An own fleet running daily trips with filings entered in bulk at day end is medium risk, and the fix is to tie the filing to trip opening. Where the share of subcontracted vehicles is high, the risk rises even with the own fleet integrated, because the subcontracted side stays manual; bring subcontractors into the same flow.

With seasonal peaks, manual filings build a backlog exactly when volume rises, so the risk is high again and the durable fix is integration. A company working under more than one authorisation certificate sits at the top of the scale: keeping the certificates separate by hand generates errors on its own, and only integration holds.

The distinction underlying the matrix is this: manual notification does not break as trip counts grow, it breaks as volume fluctuates. A routine that holds through a quiet week builds a backlog during a peak — exactly when inspections become more frequent.

How does the risk change as the fleet grows?

Risk grows faster than the fleet, because errors stop being isolated incidents and become categorical. A plate written in a format the system does not expect affects one vehicle in a single-truck company and is corrected once; the same habit in a large fleet breaks the notification for every trip run with that vehicle, and one error produces enough missing records to disqualify the whole period.

The second factor is that the field of view of the person checking does not grow with the fleet. In a company running a handful of vehicles, which trips were filed can be held in someone's head; above that, a missing record becomes visible only when two lists are compared.

The third factor is the subcontractor share: extra capacity is met with vehicles outside your own record discipline, so the error rate there runs higher while the consequence still lands on your certificate.

Which three controls lower the risk?

1. Tie the notification to trip opening. As long as it is a separate task it gets forgotten; when it is part of the trip there is no step left to skip.
2. Make rejection responses visible. A flow in which a rejected record never lands on anyone's screen produces penalties silently.
3. Put subcontracted vehicles in the same flow. A routine that works for the own fleet is of little use if it breaks at the subcontractor.

The shared logic of the three is to move the control from the office to the moment the trip begins. A check made at day end notices a gap late; a check made at trip opening prevents it.

The same discipline applies when a new vehicle enters service: a trip run with a vehicle not yet within the scope of the authorisation certificate produces an out-of-scope record, and unless it is corrected it stays a missing filing.

You can see how these three controls are set up inside an operation on the how Seferi works page, and which module takes on which step on the features page.

A closing reminder: this article is general information, not legal advice. Because fine amounts and warning point thresholds are revalued annually, verify the current position with the Ministry of Transport and Infrastructure, and confirm your own certificate's position with the regional directorate you are registered with.

How much is the penalty for not filing a U-ETDS trip?

The sanction is applied primarily as a warning point rather than as a flat sum of money. A warning point is recorded against the holder of the authorisation certificate for every trip that was not notified, and a deliberately false or misleading notification attracts a markedly heavier warning than a simple omission. Incomplete or incorrect data entry may additionally attract an administrative fine per unit. We deliberately publish no figure here, because amounts are revalued annually and a decision based on a stale number is worse than no number at all. Verify the current position with the Ministry of Transport and Infrastructure before acting. The more useful question for an operator is not what one trip costs, but how quickly the balance on the certificate is growing.

Why does a warning point matter more than a fine?

Warning points accumulate on your authorisation certificate, and once certain thresholds are passed the certificate can be temporarily restricted. That is a far heavier outcome than paying for individual trips: if your certificate is restricted you cannot carry at all, and what speaks then is not the sum you paid but the vehicles standing still in the yard. A fine is a line item that is settled and closed; a warning point is a balance that stays and keeps growing. This is why the U-ETDS penalty should be assessed as a risk to the certificate rather than as a cost per trip, and why two companies with the same habit but very different trip volumes are not carrying the same exposure.

Can accumulated warning points be removed?

Yes. A company that closes a three-month period completely, on time and error-free has a portion of its previous warning balance removed automatically. The system does not only punish; it also rewards a settled notification routine. Being behind is therefore not a permanent condition: once the routine is in place the balance erodes over time. The removal works per period rather than per trip, so correcting a single record does not rescue the period, and all three conditions have to hold together. The first thing a company with a high balance should do is not to argue about the past but to close the next three-month period cleanly.

If the system rejects my record, does the trip count as notified?

No. A rejected record counts as not notified at all. This is the situation most often missed by companies filing by hand: the record is sent, the system rejects it because of one field, nobody checks the response, and the trip stays unreported. Because the company believes the filing was made, the gap only comes to light at an inspection. Any notification flow therefore needs a checkpoint where rejection responses are actually seen by a person or blocked by the system, otherwise the balance grows silently while the operation looks clean from the inside.

How is a missing notification detected at an inspection?

At a roadside check the documents in the vehicle are compared with the trip record held in the system, and a report is drawn up where no record exists or the record does not match the document on board. You do not have to be stopped on the road for a gap to be found, however: missing notifications can also be identified in periodic reviews carried out through the system itself. The difference between the two routes is the period they cover. A roadside check looks at the trip running at that moment, while a system-based review covers an entire past period, which means unreported trips can accumulate quietly and then arrive together.