Atjaunot OCTA obligāto civiltiesiskās atbildības apdrošināšanu

Kad izmantot

An OCTA policy on a company vehicle is approaching its end date. Not for a vehicle newly bought or brought into the company — use vehicles.add-vehicle, which registers it and starts its first policy. Not for casco, fleet or other voluntary insurance — this playbook covers only the compulsory third-party liability policy (OCTA) that Latvian law requires for every registered vehicle.

Pirms sāc

• The vehicle list shows the plate, current insurer, policy number and expiry date.
• The usage is known: who drives, private or business use, whether the vehicle goes abroad (green card is
• ⚠ jāpārbauda how many days before expiry a policy can be bought in advance, and whether the new policy can

Ko izpilde pieprasa3

Ceļš8 soļi

1. S1

   Read the renewal windowaģents

   For each vehicle due, read the expiry date from the vehicles module and confirm it against the current policy document.

   Izdarīts, kad each vehicle has a confirmed expiry date and a target start date (the day after expiry, or the same day if the policy allows same-day start).

2. S2

   Check the vehicle data is currentaģents

   Compare plate, registration state and usage against CSDD data and the vehicles module.

   Izdarīts, kad any mismatch (sold vehicle, changed usage, new driver) is written down before offers are requested.

   ⛔ Renewing a policy for a vehicle the company has already sold creates a paid policy for nothing.

3. S3

   Collect at least three offersaģents

   Request prices from at least three insurers (via the vehicles module integrations or the insurers' websites) for the same vehicle, usage and coverage period.

   Izdarīts, kad a comparison exists: insurer, price, period, what differs (instalments, claims handling notes), with the collection date.

4. S4

   Choose the insurerīpašnieksvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S4 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Present the comparison with a recommendation.

   Izdarīts, kad the owner has named the insurer and the price they approve.

5. S5

   Pay and issue the policyaģentsvajag apstiprinājumu · īpašnieksneatgriezenisks

   Apstiprinājums · S5 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Neatgriezenisks solis · S5 — aģents to nekad nenoslēdz viens

   Buy the approved policy in the company's name, pay from the agreed account, and confirm the policy document is issued — not merely ordered.

   Izdarīts, kad a policy document exists with a policy number, start and end dates, and the payment is recorded in the money module.

   ⛔ "I started the order" is not a policy. No issued document, no step done.

6. S6

   Verify the policy is registeredaģents

   Check the policy appears in the state OCTA database (via ltab.lv check by plate number) with the correct start date.

   Izdarīts, kad the database shows the new policy active from its start date.

   ⛔ A paper PDF without a database entry means the police see the vehicle as uninsured.

7. S7

   Update the vehicles moduleaģents

   Record policy number, insurer, price, start and end dates; set the next renewal deadline so this playbook fires again.

   Izdarīts, kad the vehicle row shows the new policy and the next deadline.

8. S8

   Record and hand backaģents

   Send the owner a three-line summary per vehicle: plate, policy number and dates, price paid vs the cheapest offer collected. File the policy document in the documents module.

   Izdarīts, kad the owner has the three-line summary per vehicle and the policy document is filed in the documents module.

Pārbaudes — kā zinām, ka izdevās

• The database check in S6 shows the new policy active — read back by plate number, not from the invoice.
• Start date = the day after (or the same day as) the old expiry — no gap, no overlap of more than a day.
• Policy holder is the company's legal name and registration number, not an employee.
• The vehicles module shows the new dates and the next renewal deadline.

Ja noiet greizi

Ko atstāj katrs solis

1. S1each vehicle has a confirmed expiry date and a target start date (the day after expiry, or the same day if the policy allows same-day start).
2. S2any mismatch (sold vehicle, changed usage, new driver) is written down before offers are requested.
3. S3a comparison exists: insurer, price, period, what differs (instalments, claims handling notes), with the collection date.
4. S4the owner has named the insurer and the price they approve.
5. S5a policy document exists with a policy number, start and end dates, and the payment is recorded in the money module.
6. S6the database shows the new policy active from its start date.
7. S7the vehicle row shows the new policy and the next deadline.
8. S8the owner has the three-line summary per vehicle and the policy document is filed in the documents module.

Ko saglabāt

Policy number and document · database check result with timestamp · payment record id · the offer comparison with collection date · the owner's choice in S4 (who, when) · the S7 vehicle row before/after.

Kā šī procedūra uzlabojas

After every 10 renewals ask: how many days before expiry did the run start, and did any vehicle end up renewed later than 5 days before? Was the paid price the cheapest collected offer, and if not, why did the owner choose otherwise? Did any run produce a gap, a wrong vehicle, or an unpaid order? A new version changes the step that caused the gap or the overpay, and says so in its change note.