The table full of files
Walk into the back office of most recond showrooms and you will see the same thing. Files on the table. A file for each car, sometimes two. A drawer of bank documents. A clipboard of payment slips waiting for someone to check them. A WhatsApp group where sales keep asking, "Boss, the loan for the Alphard already approved or not?"
None of this is because people are lazy. Recond car sales really are document heavy. A single unit can pass through import and customs, duty payment, Puspakom inspection, JPJ registration, a bank or hire purchase (HP) loan, the LOU, insurance cover note, the VSO and the final handover. Each step has its own paper and often its own person.
The trouble starts when the information about one car is spread across many places. To answer a simple question about one unit, you need the sales file, the accounts book, the admin checklist and somebody's memory.
A recond deal is really a sales workflow
It helps to see a recond deal for what it is: a sales workflow with many hand-offs. Sales books the car. Accounts confirms the booking fee and later payments. Admin prepares the loan documents, insurance and registration. The owner decides when to pay duty and release the car.
Each person depends on the one before. When the hand-off happens by phone call, chat message or a sticky note on the file, things wait. That waiting is where deals slow down, customers get anxious and staff spend their day chasing instead of closing.
This is why a dealer system works best when it behaves like a sales workflow system, similar to the SFA (sales force automation) tools used by distributors, but built around the car. RecondOS, one of Our Products, is designed this way.
The idea: one record per car, found by chassis number
The simple shift is this. Make the car the base unit of your business, and use the chassis number as its key.
Every car gets one record from the day it is bought or imported until well after it is sold. Everything about that car is attached to it:
- Purchase and import: AP details, supplier, landing cost and import documents.
- Duty: amount, status and the date it was paid.
- Inspection and registration: Puspakom result, JPJ registration status and plate number.
- The deal: customer, salesperson, booking date, selling price and the signed VSO.
- Loan: bank or HP company, submission date, approval, LOU and disbursement.
- Payments: booking fee, down payment, balance, each one marked as verified or not.
- Insurance and handover: cover note, delivery date and who released the car.
- Refunds and adjustments: what was refunded, why, and who approved it.
Once this exists, nobody needs to ask "where is the file". The file is the record, and everyone looks at the same one.
What each person sees and does
| Role | What they see | What they do |
|---|---|---|
| Sales | Each of their deals with status: booked, loan submitted, loan approved, payment received, ready for delivery | Create the booking, upload customer documents, follow up with the customer |
| Accounts | Payments waiting to be verified, by car and by customer | Check the bank-in against the statement and mark it verified in the system |
| Admin | A queue of cars ready for the next step, sorted by what has been paid | Prepare loan documents, insurance, Puspakom and JPJ registration in the right order |
| Owner | Which sold or paid cars still need duty, what cash is coming in and what is going out | Decide which duty to pay first and keep an eye on cash and stock |
Sales stop chasing. A salesperson can open the deal and see whether the loan is approved and whether the customer's payment has been verified. There is no need to message admin or accounts and wait for a reply. They can give the customer a clear answer straight away.
Accounts update once. When accounts confirms a payment, they mark it in the system. That single update tells sales, admin and the owner at the same time. Nobody has to forward screenshots or repeat the same message three times.
Admin works from a queue. As soon as a payment is verified, the case moves into admin's queue. Admin can see which cars are fully paid and ready for registration, which are waiting on loan documents and which are still missing something. They work on the right case first instead of the loudest one.
The owner sees duty priority and cash. Duty is one of the biggest cash outflows for a recond dealer. When every car shows its sold and payment status, the owner can pay duty first on cars that are already sold and paid, and hold back on units still sitting in the yard. It also gives a clearer picture of cash position without waiting for a month-end report.
A day in the life: before and after
Before. At 9am a customer calls asking when he can collect his Vellfire. The salesperson does not know, so she messages admin. Admin says the loan is approved but she is not sure if the balance was paid, so she asks accounts. Accounts is busy with the bank reconciliation and replies after lunch. Meanwhile the owner is deciding which duty to pay this week, flipping through files to work out which cars are sold. In the afternoon an auditor emails asking for the full history of a car sold last year. Someone spends two hours pulling papers from the storeroom.
After. The customer calls. The salesperson opens the car by chassis number and sees the loan approved, the balance verified by accounts yesterday and the registration in progress. She tells the customer the realistic collection date on the spot. Admin starts the day with a queue already sorted by paid cases. The owner opens a list of sold and paid cars still waiting for duty and decides in a few minutes. When the auditor asks about last year's car, accounts searches the chassis number and exports the deal, payments, duty and refund records together.
Nothing magic happened. The same people did the same work. They simply stopped working from separate piles.
Faster closing comes from fewer hand-off gaps
Dealers often think of speed as a sales problem. In practice a lot of time is lost between people: the hours between a payment arriving and someone confirming it, between confirmation and admin starting the paperwork, between paperwork ready and the owner releasing duty.
When status is visible to everyone and each update moves the case forward automatically, those gaps shrink. The car gets registered and delivered sooner, the customer is happier and the next sale can start.
Customer history and audits in one search
Months or years after a sale, questions come back. A customer wants a copy of the VSO. A bank asks about a disbursement. Your auditor or tax agent asks for supporting documents for a list of cars for bookkeeping.
With one record per car, the answer is one search. Type the chassis number and you see the whole story: who bought it, for how much, every payment received, the loan and disbursement, duty paid, registration details and any refund. You can show the auditor exactly what happened without rebuilding it from memory and box files.
Refunds without the headache
Refunds are where paper systems hurt the most. A loan is rejected, a customer cancels, or a booking needs to move to another unit. To refund correctly you need to know exactly what was paid, when, by whom and what was already spent on that car.
When all payments and costs sit on the car's record, the refund is straightforward. Accounts can see the verified payments, the owner can approve the amount, and the refund is recorded on the same car so the history stays complete. No more digging through stacks of files on the table.
Quick checklist: how is your process today?
Answer yes or no for your showroom:
- Can a salesperson see a deal's loan and payment status without asking anyone?
- Does accounts update a verified payment in one place that everyone can see?
- Does admin have a clear list of which paid cases to process first?
- Can you list all sold cars that still need duty paid, in under five minutes?
- Can you find the full history of a car sold last year by chassis number?
- Can you process a refund without pulling physical files?
- If a key admin staff resigned tomorrow, would the status of every car still be clear?
If you answered "no" to three or more, the paper pile is probably costing you time and sales. Start by picking one rule: every new car gets one record from day one, keyed by chassis number, and every update goes there first.
Frequently asked questions
Why use the chassis number instead of the plate number?
A recond car may not have a Malaysian plate until JPJ registration is done, and plates can change. The chassis number stays with the car from import to sale and beyond, so it is the most reliable key.
Does this replace the JPJ, customs or bank portals?
No. You still use the official portals and bank systems. The car record keeps your internal status, documents and dates in one place so your team knows where each step stands.
Is this only for big multi-branch dealers?
No. A small showroom with a few staff benefits early, because one person often covers several roles and needs to see everything quickly. The benefit grows as you add cars, staff and branches.
Can we keep using WhatsApp with customers?
Yes. Customers will still message you. The difference is that payment slips, documents and decisions end up on the car's record, so they are not lost in a chat.
See how RecondOS works
If the table full of files sounds familiar, take a look at the RecondOS product page to see how one record per car fits a recond showroom. You can also contact Xameon on +60 16-679 1186 to talk through how your sales, accounts and admin hand off today.
