Sell or deregister a vehicle

When to use

A company vehicle is sold to a buyer, scrapped, or exported. Not for a vehicle the company keeps — renew its inspection and OCTA via vehicles.technical-inspection and vehicles.octa-renewal. Not for adding a replacement to the fleet — use vehicles.add-vehicle. If the vehicle was in an accident before the sale, close that first with vehicles.accident.

Before you start

• The owner has said whether the vehicle may be sold at all (owned outright — not leased; a leased vehicle
• Registration document, service book and both keys are on hand, or their absence is noted.
• Known defects, damage history and current odometer are written down before any buyer sees the vehicle.

What a run requires3

The trail8 steps

1. S1

   Assemble the vehicle fileagent

   From the vehicles module: registration number, VIN, make, model, year, odometer, inspection and OCTA expiry, known defects, photos (all sides, interior, odometer).

   Done when one vehicle record lists every fact a buyer would ask about, with photos attached.

2. S2

   Check encumbrances and finesagent

   In e-CSDD check the vehicle's status, registered owner and any restrictions (pledge, lease, seizure); check for unpaid traffic fines (vehicles.traffic-fine handles them separately).

   Done when the result is written in the vehicle record: "clean" or the exact encumbrance found, with the date of the check.

   ⛔ An undisclosed pledge blocks the transfer at CSDD — resolve it before advertising, not after a buyer is found.

3. S3

   Set price and channelownerneeds approval · owner

   Approval · S3 · owner — the run stops until a named person records the decision

   Present the vehicle file with a market-price range from recent ads for the same model and year, and the options (private sale, dealer buy-back, scrap/export).

   Done when the owner has named a minimum acceptable price and the channel.

4. S4

   Prepare the ad and the sale contractagent

   Draft the ad from the vehicle file (defects included — hiding them creates claims later) and prepare the Latvian purchase contract: parties with personal codes / registration numbers, vehicle and VIN, price, odometer reading, handover date.

   Done when ad text and contract draft are ready for review.

   ⛔ Never sign over the registration document before payment — hand it over at S7 together with the keys.

5. S5

   Advertise and screen buyersagent

   Publish on the chosen channel, answer enquiries, arrange viewings and test drives.

   Done when a buyer is named with agreed price and handover date, or the owner is asked to revisit S3 after 3 weeks without a buyer.

6. S6

   Sign and get paidownerneeds approval · ownerirreversible

   Approval · S6 · owner — the run stops until a named person records the decision

   Irreversible · S6 — an agent never closes it alone

   At handover: buyer signs the contract, pays the agreed price into the company account, receives the keys and the registration document; both parties sign the odometer reading.

   Done when the contract is signed by both parties and the payment is visible in the bank feed.

7. S7

   Notify CSDD of the transferagent

   Submit the ownership transfer notice through e-CSDD on the day of handover (LV — ⚠ verify the seller's notice obligation and the buyer's registration deadline in the Road Traffic Law, likumi.lv / csdd.lv). If the vehicle is scrapped or exported instead, follow the CSDD deregistration path for that case.

   Done when the e-CSDD confirmation is saved, or CSDD data shows the buyer as owner.

8. S8

   Cancel OCTA and close the fleet recordagent

   Cancel the OCTA policy effective from the transfer date (insurer or via the vehicles module; ⚠ verify the insurer's notice channel and any refund rules). Remove the vehicle from the fleet list, cancel its inspection and OCTA renewal reminders, book the sale price in the money module.

   Done when the fleet list no longer shows the vehicle and the payment is matched to the sale.

Checks — how we know it worked

• CSDD data (checked from e-CSDD, not from the contract) shows the buyer as owner, or a deregistration entry.
• Contract states the odometer reading and both signatures are present.
• Payment received equals the contract price; matched in the money module.
• OCTA policy shows cancelled from the transfer date; no further charges on the bank feed.
• The next traffic fine for that registration number, if any, can be answered with "sold on <date>, see contract".

If it goes wrong

What each step leaves behind

1. S1one vehicle record lists every fact a buyer would ask about, with photos attached.
2. S2the result is written in the vehicle record: "clean" or the exact encumbrance found, with the date of the check.
3. S3the owner has named a minimum acceptable price and the channel.
4. S4ad text and contract draft are ready for review.
5. S5a buyer is named with agreed price and handover date, or the owner is asked to revisit S3 after 3 weeks without a buyer.
6. S6the contract is signed by both parties and the payment is visible in the bank feed.
7. S7the e-CSDD confirmation is saved, or CSDD data shows the buyer as owner.
8. S8the fleet list no longer shows the vehicle and the payment is matched to the sale.

Evidence to keep

Vehicle file with photos and odometer at handover · signed sale contract (scan) · payment reference · e-CSDD transfer/deregistration confirmation · OCTA cancellation confirmation · the owner's price decision in S3 (who, when, what minimum).

How this playbook improves

After every 5 runs ask: how many days from ask to signed contract, and did any encumbrance surface after S2? Did any buyer fail to register, and did the CSDD notice close it? Did any OCTA charge land after the transfer date? A new version changes the step that caused the wait or the miss, and says so in its change note.