Skip to content

ETLE · ETLE fines

ETLE is Indonesia's electronic traffic enforcement. A weekly job checks every ready or rented car's plate; a fine it finds is linked to the rental active at the time and can become a charge on the driver. Code ETLE.

R-ETLE-01 · An ETLE ticket number is unique within the organization

Section titled “R-ETLE-01 · An ETLE ticket number is unique within the organization”
  • Status: planned
  • Example: given a violation with ticket number T-123, when the next scan finds T-123 again, then a second row is refused.
  • Refusal: none: unique_violation (23505).
  • Who: every writer, the ETLE job included.
  • Source: [Ref] Data model V13: etle_violations.

R-ETLE-02 · A violation is linked to the rental that was active when it happened

Section titled “R-ETLE-02 · A violation is linked to the rental that was active when it happened”
  • Status: planned
  • Example: given a car rented to driver A until 2026-10-03 and to driver B from 2026-10-04, when a violation of 2026-10-02 is found on 2026-10-06, then it is linked to driver A's rental.
  • Refusal: none.
  • Who: the ETLE job (M5).
  • Source: [Ref] Database rules and conventions, Scheduled jobs; [Ref] Data model V13: etle_violations.rental_id.

R-ETLE-03 · The weekly ETLE check records one scan for each ready or rented car

Section titled “R-ETLE-03 · The weekly ETLE check records one scan for each ready or rented car”
  • Status: planned
  • Example: given 40 cars ready or rented and 6 in maintenance, when the weekly check runs, then 40 etle_scans rows are written, one per car, including the cars whose check failed (result error).
  • Refusal: none.
  • Who: the ETLE job (M5).
  • Source: [Ref] Database rules and conventions, Scheduled jobs.

R-ETLE-04 · Reading ETLE scans and violations needs vehicle:read at the car's pool

Section titled “R-ETLE-04 · Reading ETLE scans and violations needs vehicle:read at the car's pool”
  • Status: planned
  • Example: given a finance user, who doesn't hold vehicle:read, when she reads etle_violations, then nothing comes back; an admin_fleet at the car's pool sees them.
  • Refusal: none: hidden.
  • Who: super_admin, admin, admin_driver, admin_fleet, maintenance, asuransi, checker and viewer hold vehicle:read.
  • Source: [Ref] Roles, policy matrix.

R-ETLE-05 · Recording ETLE scans and violations needs vehicle:write at the car's pool

Section titled “R-ETLE-05 · Recording ETLE scans and violations needs vehicle:write at the car's pool”
  • Status: planned
  • Example: given a checker at PML, when he records a violation for a PML car, then it is refused; an admin_fleet at PML may.
  • Refusal: none: insufficient_privilege (42501) on insert; no effect on update.
  • Who: super_admin, admin and admin_fleet hold vehicle:write. The ETLE job runs as service_role and isn't limited by this.
  • Source: [Ref] Roles, policy matrix.