A repair you have to order a part for, a device somebody is holding for a customer, a bill split across two visits. Taking part of the money is a normal sale with a balance attached — and the balance is only real if Lunix knows about it.
- 1
Ring the sale as normal
Build the order with everything on it, at the full price. Do not reduce the total to match what the customer is handing you — the order says what was sold; the payment says what was paid.
- 2
Choose Deposit at payment
On the payment screen pick Deposit, which has to be enabled in your payment methods. Then choose the deposit option and enter the deposit amount — what the customer is paying right now.
- 3
Or mark a payment as partial
Where you are taking part of the money on a method you already use, mark it as a partial payment instead. Either way the result is the same: money in, and a balance recorded against the order.
- 4
Set the due date
The due date is required, and that is deliberate. "He'll come back" is not a date, and a balance with no date is a balance nobody chases. Put the day you actually expect the rest.
- 5
Read the due amount back to the customer
The order shows the due amount. Say it out loud and put it on the receipt — the argument you are preventing is the one in three weeks about how much was left.
- 6
Collect the rest later
When the customer comes back, take the balance against the order. Outstanding balances live in accounts receivable, which is where you look to see who owes you what and which dates have passed.
Proffs tips
- For a repair you have not started, a quote or a draft order may fit better than a deposit — nothing is committed and no balance exists until the customer agrees.
- Filter accounts receivable by due date once a week. A deposit taken with a date and never followed up is worse than no system at all, because everybody assumes it is handled.
Var detta till hjälp?