Recond Deal Checklist Malaysia: Booking VSO LOU/COS Insurance Duty JPJ Handover

Originally published at xameon.com.

Malaysian recond deals stall less often because the car is wrong, and more often because one admin step was “almost done.” This article is a printable process SOP / checklist—not another narrative tour of the journey. Use it on the wall, in a shared drive, or as the skeleton for your dealer system’s stage flags.

It complements the longer story in From Booking to Disbursement. That guide explains why stages fragment. This one is the what to tick list from booking through LOU/COS, insurance, import duty, JPJ e-daftar, handover, and disbursement readiness.

Soft map only: where a Malaysia-shaped system helps, RecondOS covers digital VSO/e-sign, multi-branch stock, LOU/COS related tracking, JPJ registration tracking, import duty, insurance, and payments/disbursements on one vehicle timeline. Official JPJ, customs, bank, and insurance portals stay official—software is the internal control tower.

How to use this checklist

• Copy per unit (chassis number on every page)
• Assign an owner per stage (sales / admin / accounts / owner)
• Tick only when evidence is on the same car record—not “someone said so in WhatsApp”
• Block handover until the minimum readiness set at the bottom is green

Stage 0 — Before anyone promises the car

• [ ] Chassis number confirmed on yard / branch stock (not plate-only)
• [ ] Stock status is Available (not reserved/sold elsewhere)
• [ ] Branch / yard location matches where the customer will view the unit
• [ ] Known blockers noted (duty unpaid, docs incomplete, mechanical hold)
• [ ] Asking price and any package rules known to the salesperson on shift

Why this stage exists: multi-branch double booking starts here. Pair with multi-branch stock discipline once that article is live, and the chassis one-record guide already on site.

Owner: sales + stock controller

Evidence: stock screen or signed yard sheet with chassis

Stage 1 — Booking / deposit

• [ ] Customer identity captured (name, NRIC/passport, contacts)
• [ ] Unit linked by chassis on the booking
• [ ] Booking fee amount, method, and date recorded
• [ ] Accounts verified the bank-in (or marked pending with a chase date)
• [ ] Stock status moved to Reserved / Booked at the correct branch
• [ ] Expiry or follow-up date set if loan path is uncertain
• [ ] Customer given a clear “what happens next” (VSO timing, docs to bring)

Owner: sales; accounts verifies money

Evidence: booking slip + payment proof on the car record

Stage 2 — Vehicle Sales Order (VSO)

• [ ] VSO generated from vehicle + customer data (no retyped chassis errors)
• [ ] Selling price, deposit, balance, gifts, trade-in (if any) match the deal
• [ ] Cash vs HP path stated; bank/HP name filled when known
• [ ] Special conditions written (subject to loan / duty / registration as applicable)
• [ ] Buyer and authorised dealer signatory signed (wet ink or e-sign per policy)
• [ ] Signed PDF stored on the same chassis record as the final version
• [ ] Amendment / version logged if price or packages changed after first draft

Educational detail on fields: What is a VSO in Malaysia?

Owner: sales prepares; manager approves exceptions

Evidence: signed VSO (version ID visible)

Stage 3 — LOU / COS related track

Exact forms depend on your bank/HP partners and ownership path. Treat this as an ops checklist, not legal advice.

• [ ] Financing application submitted (or cash path confirmed in writing)
• [ ] Supporting buyer docs complete per lender checklist
• [ ] LOU / COS related items requested, submitted, or cleared—each with date and owner
• [ ] Blocks recorded (missing docs, valuation issues, guarantor pending)
• [ ] Sales told not to promise handover dates while this track is red
• [ ] Approval / decline outcome filed on the car record

Owner: admin (sales supports customer chase)

Evidence: submission refs + clearance notes on the timeline

Stage 4 — Insurance

• [ ] Insurer / cover path chosen per company process
• [ ] Cover note or confirmation requested with effective date target
• [ ] NCD / existing policy issues noted if trade-in or transfer applies
• [ ] Insurance milestone marked on the same vehicle timeline as VSO
• [ ] Handover rule clear: can keys leave without cover note? (company policy)

Owner: admin

Evidence: cover note / confirmation file on the car record

Stage 5 — Import duty (where applicable)

Not every used unit carries the same duty story; recond / import-heavy yards feel this hardest.

• [ ] Duty amount and status known for this chassis
• [ ] Payment priority decided by owner (sold+paid units usually first)
• [ ] Duty payment date and receipt filed on the car record
• [ ] Downstream steps that wait on duty are flagged (do not fake “ready”)
• [ ] Cash impact visible to owner without hunting email

Owner: owner / accounts; admin updates status

Evidence: duty receipt + status flag

Stage 6 — JPJ registration (e-daftar and related steps)

Dealers complete official actions through proper JPJ / partner channels. Internal software only tracks status.

• [ ] Registration path clear (who lodges, which partner, which queue)
• [ ] Required supporting docs assembled against the signed VSO identity
• [ ] Submission date and reference noted on the car record
• [ ] Pending / cleared / blocked status updated when anything changes
• [ ] Plate number captured when assigned
• [ ] Customer communication uses realistic dates from this status—not optimism

Owner: admin

Evidence: submission ref + status notes (portal work stays on official systems)

Stage 7 — Payments & disbursement readiness

• [ ] All customer payments listed (booking, DP, balance) with verified flags
• [ ] HP disbursement or cash settlement path clear
• [ ] Refunds / adjustments (if any) approved and recorded on the same chassis
• [ ] Finance checklist green before funds movement or final release
• [ ] No open “which VSO version?” question remains

Owner: accounts + owner

Evidence: payment ledger on the car record

Stage 8 — Handover

• [ ] Minimum readiness set below is complete
• [ ] Keys, spare, manuals, and agreed accessories prepared
• [ ] Customer signs handover acknowledgement per your template
• [ ] Stock status moved to Sold / Delivered
• [ ] After-sales contacts and warranty notes (if any) recorded
• [ ] Showroom photo / exit checklist done if your branch uses one

Owner: sales + admin

Evidence: handover form + final stock status

Minimum readiness set (print this box)

Do not hand over or treat disbursement as “done” until:

1. Signed final VSO on the chassis record
2. Stock status matches sold/reserved at the correct branch
3. LOU/COS related items cleared or explicitly waived per written process
4. Insurance pathway confirmed per company rule
5. Import duty at the agreed stage for this unit type
6. JPJ registration milestones at the agreed stage
7. Payments reconciled / verified on the same timeline

If any line is red, the honest customer update is “pending X,” not “tomorrow for sure.”

Role cheat-sheet

Turning the checklist into daily ops

Paper checklists help for a week; they fade when volume rises. The durable pattern is:

1. One record per chassis (guide)
2. Stage flags that match this SOP
3. Evidence files attached where the tick happens
4. Multi-branch stock that refuses silent double booking

Xameon’s RecondOS is built so those stages—digital VSO/e-sign, multi-branch stock, LOU/COS, JPJ registration tracking, import duty, insurance, payments/disbursements—sit on one vehicle thread. Use this checklist to brief a demo: walk one live chassis from booking to handover and see which ticks are still tribal knowledge.

FAQ

Is this checklist a substitute for bank or JPJ procedures?

No. It is an internal ops SOP. Banks, insurers, customs, and JPJ keep their official channels. Your checklist tracks whether your team has the evidence and status to hand over honestly.

How is this different from the booking-to-disbursement article?

That guide explains the journey and why stages fragment. This page is the printable tick-list / process SOP you can put on a wall or mirror as system stage flags.

Do we need software to use it?

No. Start on paper per chassis. Software such as RecondOS helps when volume and branches make paper ticks fade—by keeping digital VSO, stock, LOU/COS, JPJ tracking, duty, insurance, and payments on one timeline.

Soft next step

Print Stage 0–8 for your next five deals. Where ticks live only in chat, that is your digitisation backlog. Email Lwhee@xameon.com or use the contact page with branch count and which stage breaks most often—VSO versions, duty priority, or JPJ chase are the usual three.

Canonical: https://xameon.com/resources/recond-deal-checklist-lou-cos-jpj-malaysia/
Contact: Lwhee@xameon.com · https://xameon.com/contact/