Skip to content

How is U-ETDS reporting done?

Updated

For a D2-licensed transfer company, U-ETDS reporting is not a separate task — it is a natural result of the trip record. In Rotenta, the passenger, route, vehicle and driver data already on the trip screen carries the fields the notification needs; the U-ETDS module transmits that data to Türkiye’s Ministry of Transport and Infrastructure and shows the send status live on the trip card.

Who uses it

Mandatory for transfer and shuttle companies operating irregular (charter, group, shuttle) passenger transport under a D2 licence. U-ETDS (Ulaştırma Elektronik Takip ve Denetim Sistemi, the Transport Electronic Tracking and Audit System) was established under Law No. 4925 on Road Transport and its related regulations to track, evaluate and audit transport activity electronically; it covers freight, hazardous-goods, cargo and passenger transport (see the official U-ETDS site).

How it works: timing, field matching, notification status

Irregular passenger carriers — transfers, staff shuttles, group and shuttle trips — must transmit trip, passenger, driver and vehicle information to U-ETDS no later than 1 hour before the journey begins; scheduled carriers must enter this information by the time the journey starts. Information about a passenger who cannot complete or make the trip must be entered within 30 minutes of that event (see the U-ETDS passenger transport page).

In Rotenta, this deadline is never something you race by hand: from the moment a trip record is created it already carries the fields notification needs — assigned staff identity, seat number, resolved pickup-point code and the transport fee — as part of the trip record itself, never filled in a second time for U-ETDS. The documents behind the notification — the operating licence, the driver’s licence — are read from document tracking.

Notification status — pending/sent/failed — shows on the trip card; no screen ever shows “sent” for a notification the ministry hasn’t confirmed. If a notification fails, the trip card shows it explicitly, and a resend can be started from the panel.

Example

Example: A D2-licensed transfer company runs 30 irregular trips a day. A trip record for an 08:00 airport transfer is entered the night before at 22:00; the system tracks the notification window (no later than 1 hour before departure) and sends it automatically on time. One passenger cancels at the last minute; the operator marks it on the trip record, and the system reports that change to U-ETDS within the 30-minute window from when it happened. The notification badge on the trip card stays “pending” until it actually turns “sent” — it never turns green early.

How it is done in Rotenta

  1. The operator creates the trip record as usual — passenger, seat, pickup point and vehicle/driver assignment happen on the same screen.
  2. Once the trip record is complete, the U-ETDS module matches these fields and tracks the notification window (for irregular transport, no later than 1 hour before departure).
  3. The notification transmits automatically; the badge on the trip card shows pending/sent/failed in real time.
  4. If a passenger cannot complete the trip, the operator marks it on the trip record; the system reports that change separately, within the 30-minute window.
  5. If the vehicle’s or driver’s operating document has expired, the assignment gate inside document tracking has already blocked creating that trip.
  6. Every trip a contract-bound recurring shuttle plan generates carries the same fields at generation time — notification needs no extra preparation.
  7. A failed notification shows on the trip card and can be resent from the panel; past notification status is kept for audit.

Frequently asked questions

Do I have to prepare the U-ETDS notification on a separate screen?

No. The trip record itself already carries the fields notification needs; the U-ETDS module transmits that data automatically once the trip is complete.

By when do I have to send the notification?

For irregular passenger transport (transfer, shuttle, group), no later than 1 hour before the journey starts; for scheduled transport, by the time the journey starts. Information about a passenger who couldn’t make the trip is reported within 30 minutes of that event (see the official U-ETDS site).

How do I know if a notification actually sent?

The badge on the trip card shows pending/sent/failed; the system only shows “sent” once the ministry side has confirmed it — never an optimistic green badge.

Can I create a trip with a driver whose document has expired?

No, the assignment gate inside document tracking already blocks assigning an expired document — which prevents an invalid U-ETDS notification before it would ever be built.

Which other modules does this connect to?

It reads trip data directly from trip and transfer operations, document validity from document tracking, and contract-bound generation from contracts and progress billing. See every connection in our module guide, or ask about the right coverage for your D2 licence through contact.

More in this category

Get a quote

Leave your details and we'll get back to you the same day.

By submitting you acknowledge the Privacy Notice.