Customers rarely pay the exact amount on the invoice. They pay part now and part later, pay in several transfers, or sometimes send more than they owe. Reyuko handles partial payments well. It rejects an amount above the balance, and it does not keep unapplied cash or a customer credit. This lesson shows how to work with each case.
Key takeaways
- Partial payments are fully supported: any amount above zero, up to the remaining balance.
- Each partial payment is a separate RCV- entry, and the status becomes Partial.
- An amount above the outstanding balance is rejected by the dialog and by the system.
- Reyuko does not currently keep a customer credit or unapplied cash from an overpayment.
- Do not assume a sales return lowers a receivable. Test it in your version first.
Partial payments
A partial payment is recorded like any other payment, from Payment > Receivable. Click Record Payment, enter the amount received, and save. The Balance falls by that amount, and the status changes to Partial. The invoice stays on the Receivable page until its Balance reaches zero.
Illustration: Harbor Wholesale is a fictional business; numbers are examples. A retail customer owes Harbor 8,000,000 on one invoice and pays in three transfers.
| Transfer | Amount | Balance after | Status |
|---|---|---|---|
| Invoice posted | - | 8,000,000 | Unpaid |
| First transfer | 3,000,000 | 5,000,000 | Partial |
| Second transfer | 2,000,000 | 3,000,000 | Partial |
| Third transfer | 3,000,000 | 0 | Paid |
Each transfer appears in Payment History with its own RCV- number. On an Installment invoice, a payment is applied to the installment rows of that same invoice. A partly paid invoice past its due date stays Overdue, and Aging AR/AP counts only the remaining balance.
Overpayments are rejected
If a customer sends more than the Balance, the Record Payment dialog marks the amount in red with the message "Amount exceeds the outstanding balance". The system also rejects the save.
Example. An invoice has a Balance of 3,000,000. The customer sends 3,500,000. You cannot record 3,500,000 against this invoice. Record 3,000,000, and handle the extra 500,000 as described below.
Do not change the amount to force the dialog to accept it. The cash record would then no longer match the invoice.
Unapplied cash: the gap
Reyuko does not currently hold unapplied cash. Once you record the balance, the extra money has no place in the Receivable list, and the app does not show a customer credit. Your bank statement may show more money than Reyuko records, and the Cash & Bank balance will be lower than the bank by the same amount until you handle the excess.
A practical workaround: record only what the invoice owes, write the excess down outside Reyuko with the customer name, date and amount, and confirm with the customer whether it is for a future invoice. When that invoice is posted, record the amount against it, dated as your accountant advises.
Returns do not lower the balance (check first)
A Sales Return posts its own journal. In the current code, posting a return does not change the receivable row of the original invoice. The Receivable and Aging pages may therefore still show the full balance after a return. Test this in your version with a sample invoice and return before you tell a customer that the balance was reduced.
- Go to Payment > Receivable and select the invoice.
- Click Record Payment and enter only the amount received for that invoice.
- Repeat for each partial transfer.
- Check the Balance in the detail panel and each RCV- entry in Payment History.
- For an overpayment, record the amount up to the Balance and note the excess outside Reyuko.
A wrong amount distorts both the invoice and your cash records. Record only up to the Balance, and keep the excess in a separate note until it is applied.
Check yourself: how much can you record?
An invoice has a Balance of 1,000,000 after an earlier payment. The customer sends 1,500,000. You can record 1,000,000 against this invoice. The remaining 500,000 is handled outside Reyuko.
Reyuko