Matching fines and accidents to drivers

A traffic fine on a plate, or an accident report, means little until you know who was behind the wheel at that hour — and if the objection window is missed, the fine becomes final. Fine and accident tracking matches an incoming fine or accident record to the driver on the shift roster automatically, and turns the deadline into a tracked task. Here’s how that match works, and where a contracted corporate customer fits into this picture.

The fine is written to the plate, responsibility falls to the driver

A traffic fine is issued against the vehicle’s plate, but who it lands on inside the business — a payroll driver or a plate lessee — depends on who was actually driving at that hour. Done by hand, remembering who drove which plate on which shift falls on the stand manager; without a shift record, that match isn’t reliable.

The objection window is a task, not a reminder

Under Turkey’s Kabahatler Kanunu (Law on Misdemeanors), an administrative fine can be objected to before the local misdemeanor court (sulh ceza mahkemesi) within fifteen days of notification, after which it becomes final (Kabahatler Kanunu, Article 27). That’s why a fine record needs to be tracked as a task carrying a deadline and a status — open, objected, final — not a spreadsheet row.

HGS toll violations: the penalty grows with time

Toll (HGS) passage violations run on the same kind of clock: if payment isn’t made within the days following the violation date, an administrative penalty is added on top of the toll fee, and that penalty structure grows the longer payment is delayed (Karayolları Genel Müdürlüğü, HGS). With many plates in a fleet, tracking these against a threshold counter beats trying to remember where each one stands.

Accident files: the same match, a different pace

An accident raises the same question — who was driving — but the answer needs to turn into a file fast, alongside the insurance notification and that trip’s passenger and route details. The shift record supplies the driver and vehicle instantly; the trip or call record fills in who was on board.

Where corporate customer accounts fit in

A fine or accident that happens during a contracted corporate customer’s ride — a factory shuttle, a corporate call agreement — is charged to the driver or the stand, not to that customer’s account, unless the contract says otherwise. The corporate customer’s running account and monthly invoice run on a separate track, tied to the ride itself.

Why the audit trail matters

Fine and accident records keep who entered them, when, and when their status changed. In an objection process or an insurance claim, when the record was created and what it was backed by needs to be visible retroactively.

How the driver takes part in the objection

The driver a fine is matched to can see the record and add an objection note if needed; that note stays on the task without the stand manager having to chase the process by hand. Once the objection outcome comes back, the status is updated and the record closes.

Example: a fine at midnight

A speeding fine is issued late one night against one of a stand’s plates. Once the notification date is entered, the shift record automatically surfaces the night driver who had that plate at that hour; the fine gets linked to that driver and listed as an open task with its objection window. A few days before the deadline, the task reminds both the stand manager and the driver. If a second fine opens for that same driver within the same month, the counter flags it too, raising a separate alert for the stand manager.

How this works in Rotenta

1. A fine record is entered with the plate and date-time; the staff module’s shift record automatically suggests the driver on shift at that hour.
2. The record is listed as an open task with its objection deadline, tracked through open, objected and final status.
3. Repeat fines or accidents per driver show up on a counter, flagged once they cross a threshold.
4. For an accident, the vehicle record in the fleet module and that trip’s passenger/route details come together in one file (vehicle and driver management).
5. A contracted corporate customer’s ride is tracked separately in the accounting module’s running account and invoice flow (accounting).

Frequently asked questions

Is a fine record entered automatically or by hand?

Today a fine record is entered by hand; the system matches it to the shift record and tracks the objection deadline as a task.

What happens if we miss the objection window?

Under Kabahatler Kanunu Article 27, the fine becomes final once the fifteen-day window passes, which is why it’s tracked as a task with a deadline.

Are HGS violations tracked on the same screen?

Yes, an HGS violation opens as a fine record too, and its time-based penalty growth is made visible in task tracking.

Does a fine on a corporate customer’s ride land on their invoice?

No, it’s charged to the driver or the stand; the corporate account only reflects the ride itself, unless the contract states otherwise.

Can a fine or accident record be deleted?

No; once closed, a fine or accident record stays in the history, and only its status (objected, final, and so on) gets updated.

See the shift record this depends on in shifts, drivers and documents, or how a deduction feeds settlement in plate rental and driver settlement. To talk through your own setup, reach out; for the overview, see taxi dispatch software.