Solavel Docs
English

A customer paid a deposit. How do I handle the remaining balance?

Last updated

App: SolaCount. Outcome: use a deposit already received, then collect only what remains due.

#The situation

Bayside Café pays Palm Grove Furnishings LLC AED 300 on 5 October 2026 before a service invoice exists. On 8 October you invoice AED 750 and the customer later pays the remaining AED 450. This separate practice case uses one base currency and excludes tax and discounts. Funding an advance does not itself calculate VAT; get the correct tax-point treatment for your jurisdiction before using this method for real taxable deposits.

#Desired result

The AED 300 deposit is held as a liability until applied, the AED 750 invoice shows Balance Due 450 after the application, and the final bank receipt is only AED 450. Assumptions: currency AED, no tax, no discount.

#Before you start

Customer advances must be enabled and available in the workspace. You need Payments → View and Payments → Post, an active postable Customer Advances liability account, a bank account, the customer, and permission to create/post the final invoice. Layla Haddad (accountant) records it; Mona Fares (finance manager) approves where an approval policy applies. Check any advance approval policy and open accounting dates. Use the same customer, organization and currency for advance and invoice.

#Workflow overview

Record the incoming money as an advance liability. Post the final invoice separately. Apply the advance to that invoice without creating another cash receipt. Record only the remaining new money as a payment.

#Exact steps

  1. Open Payments → Customer Advances → New Payment. Select Bayside Café, the actual bank account, date 5 October 2026, currency AED and amount 300.
  2. Keep Payment purpose → Record as advance. Save and post through the available approval workflow. Open the resulting advance and verify Available Advance 300.
  3. Create and review the AED 750 service invoice dated 8 October in Sales → Documents → Invoices. Complete required approval and post it. Verify Balance Due 750 before applying anything.
  4. Return to Payments → Customer Advances, open the advance, and use Apply Advance. Select this posted invoice, enter amount 300 and the application date, then click Apply.
  5. Open the invoice. Check its Payments table and Balance Due 450. The application is a settlement, not another bank deposit.
  6. When the customer actually pays AED 450, click Record a payment on the invoice, choose the bank account/date/method, allocate 450 to this invoice and click Post, then confirm.

#App handoffs

Step Type What transfers Remaining review Effect timing How to verify
Fund advance Manual, SolaCount only Cash into Customer Advances liability Approval if required Bank and liability change at posting Available Advance 300
Apply Advance Manual, SolaCount only Advance linked to posted invoice None Receivable falls at application date; no cash moves Invoice Payments table, Balance Due 450
Goods order variant Not triggered by the advance Nothing to SolaStock Warehouse approval and dispatch Stock moves only at shipment See order-to-payment

There is no cross-app handoff in this service example. Within SolaCount, Apply links the existing funded advance to the selected invoice. It reduces Customer Advances and Accounts Receivable; it does not move cash or stock.

If this is a goods order connected to SolaStock, the final invoice uses the separately verified order-to-payment workflow. The advance itself creates no warehouse request. Dispatch still needs warehouse approval and actual shipment confirmation; applying the deposit cannot substitute for those steps.

#Check your result

Checkpoint Cash received so far Available advance Invoice balance
Advance funded 300 300 No invoice yet
Invoice posted 300 300 750
Advance applied 300 0 450
Final payment posted 750 0 0

The invoice is Paid and the advance is exhausted. Check the advance history, invoice Payments table, customer statement and Payments Received report. Total new cash is 300 + 450 = 750, not 1,050. Applying the advance is excluded from new cash receipts.

#Common variations

For a larger deposit, apply only the invoice's balance; leave the rest available or use Refund Advance for money actually returned. For a partial application of 200 in this example, available advance is 100 and the invoice still owes 550. A draft, fully paid, different-customer or different-currency invoice cannot receive this advance. Check those conditions if the invoice is missing from Apply Advance.

An application date must be in an open period. To correct an application, use Advance history → Reverse, provide a date and reason, and review the restored balances before applying again.

#Mistakes to avoid

Before retrying a step, check the advance history so the same deposit or application is not recorded twice. An application is refused if it exceeds the advance's available amount or the invoice's balance, or if the invoice is a draft, void, for another customer or in another currency; the application form also carries a submission key, so a repeated click returns the application already made. Check the advance list before re-entering the deposit itself; its own duplicate protection was not verified. Do not create a second AED 300 payment when applying the deposit. Do not fund advances as sales revenue. Do not assume receipt of a deposit meets every tax invoicing requirement: the application records settlement, not a jurisdiction-specific tax decision.

Customer order to payment, Customer return and refund, Customer advance payments, Payments, Invoices, Taxes and VAT, Business Solutions & Examples.