Customer payments

Record a customer receipt and spread it across the customer’s open invoices. Villva enforces strict guards so receivables can never go wrong, and posts the payment immutably.

Record a payment and allocate it

1. Open Finance → Customer payments and click New payment.
2. Enter the receipt details:
   • Mode: cash, cheque, NEFT, RTGS or UPI
   • Amount
   • Deposit account
   • Reference and date
3. Allocate the amount across one or more of that customer’s open invoices.
4. Save.

📷 Image placeholder

Add a short recording here: entering a new receipt (mode, amount, deposit account, reference, date), then splitting the amount across two open invoices and saving, with the balances updating.

Each allocated invoice’s balance reduces by exactly its allocation, and the customer’s total outstanding reduces by the total allocated.

📷 Image placeholder

Add a screenshot here: the New payment form with the allocation table listing the customer’s open invoices and the amount allocated to each.

Example

For a customer with open invoices INV-1 (30,000) and INV-2 (50,000), record a 70,000 NEFT payment and allocate 30,000 to INV-1 and 40,000 to INV-2. After posting, INV-1 is 0, INV-2 is 10,000, and the customer’s outstanding has dropped by exactly 70,000.

Allocation guards

• The total of your allocations cannot exceed the payment amount.
• An allocation to a single invoice cannot exceed that invoice’s balance. If you try to over-allocate, the save is blocked and a clear message tells you which allocation is too high, a balance can never go negative.
• If two payments try to allocate to the same invoice at once, only one succeeds; the other is rejected. There is no double-allocation.

Unallocated remainder

Any amount you do not allocate can be retained as an advance against the customer. If your organisation requires payments to be fully allocated, the save is blocked until the whole amount is allocated.

The payment is final

Once posted, a payment is immutable and written to the audit trail. To change its effect, use a reversing entry rather than editing it.