A borrower walks in with ₱5,000 when only ₱3,200 is due. The cashier posts the full amount, the schedule looks clean, and nobody asks what to do with the ₱1,800 excess. Two weeks later the borrower wants it back in cash, the officer already treated it as an early principal cut, and the branch manager has three different stories. That is what a missing loan overpayment desk looks like: not a software bug, but a decision nobody owned.
The short answer: treat excess payment as a controlled desk event. Confirm the amount that was actually due, log the excess, choose one written disposition (apply to next due, refund, or offset another loan of the same borrower), get the second signature your policy requires, then post the LMS repayment so the receipt, schedule, and cash drawer all match. Soft language only: this is operational guidance for PH lending desks, not legal advice.
What counts as an overpayment (and what does not)
For desk purposes, an overpayment is cash or transfer received against a specific loan that is more than the amount due on that loan under your posted schedule and fees on that day. Three common traps:
- Partial payments are not overpayments. If ₱2,000 of a ₱3,200 due arrives, you have a shortfall. Allocation rules for that case belong in your waterfall policy, not here — see partial repayment waterfall mistakes and how waterfall allocation protects lender policies.
- Full pre-termination is not a casual excess. If the borrower is closing the loan, you need a payoff quote (principal, accrued interest, fees your contract allows), not a next-due credit. Use your pre-termination payoff quote process.
- Unidentified float is not an overpayment. Money in the drawer with no loan ID is a cash-control problem first. Tie it to a borrower and loan before you choose refund vs credit.
Once you know the loan, the due amount, and the cash received, the excess is a desk decision with a paper trail — even if your LMS has no dedicated “overpayment module.”
Decision table: apply to next due vs refund vs offset
Write the rule before the queue gets busy. The table below is a starting policy for small PH money lenders and MFI ops desks. Adjust thresholds to your license, float, and maker-checker limits.
| Situation | Preferred disposition | Why | Who signs |
|---|---|---|---|
| Excess ≤ next scheduled installment; borrower still active; no refund request | Apply to next due (credit on schedule) | Keeps cash in the book, cuts next visit friction, easy to explain on the statement | Cashier posts; officer confirms borrower consent on receipt note |
| Borrower asks for cash back the same day; excess within cashier float limit | Refund same day from drawer | Clears the quasi-contract risk early; borrower leaves satisfied | Cashier + second staff (teller or BM) on refund slip |
| Excess above cashier float limit or refund after the cash already remitted | Refund via next-day float / cheque / transfer per policy | Protects overnight float and dual-control cash rules | Branch manager; finance if above BM limit |
| Borrower has a second loan in arrears under the same CIF | Offset other loan (after written consent) | Protects PAR without inventing a new product | Officer + BM; consent note on both loan files |
| Borrower disputes the “due” figure or claims wrong loan ID | Hold excess in desk log; do not auto-apply | Wrong allocation creates statement fights and support tickets | BM owns hold until schedule vs receipt is reconciled |
| Loan already paid off / zero balance before this cash | Refund (or written credit to another open loan) | No due left to apply; holding cash without basis invites complaints | BM + finance as needed |
Default for most weekly collectors: apply to next due when the borrower does not ask for a refund and the loan is still open. Default when they do ask: refund, with dual control. Offset only with consent — silent cross-loan application is how trust breaks.
Why PH desks care: solutio indebiti in plain language
Under the Civil Code of the Philippines, payment of something not due can create an obligation to return it. Article 2154 states that if something is received when there is no right to demand it, and it was unduly delivered through mistake, the obligation to return it arises. Article 2155 brings certain mistakes of law into that scope; Article 2156 allows recovery when the payer was in doubt whether the debt was due and later proves it was not. The full quasi-contract text is published in Title XVII of Book IV (see a clear rendering of Articles 2154–2156).
For a branch desk, the practical takeaway is simple: if you keep money you had no right to demand under the loan schedule, you should expect the borrower to ask for it back — and your own policy should make refunds routine, documented, and dual-controlled. This paragraph is educational only. How Articles 2154–2156 apply to a specific case depends on facts and your counsel; SEC / BSP rules for your license still govern how you handle customer funds. This is not legal advice.
7-step overpayment desk checklist (with roles)
- Identify the loan and the due amount (Cashier + Officer). Pull the LMS schedule for that loan ID. Note principal due, interest due, fees due, and penalties due for today. If the borrower has multiple loans, confirm which one they intend to pay.
- Count and receipt the full cash received (Cashier). Issue a collection receipt for the full amount received — never for “due only” while pocketing the rest. Receipt discipline is the same problem as field collections; see collection receipt discipline.
- Compute excess = received − amount due today (Cashier). Write the three figures on the receipt stub or desk log: due, received, excess. If received < due, stop — that is a partial, not an overpayment.
- Ask the borrower which disposition they want (Officer). Offer the three options your policy allows: apply to next due, refund, or offset another open loan. Note the answer on the receipt or a short consent slip. If they are unsure, default per your written table (usually next-due credit).
- Get the second signature when policy requires it (Maker-checker). Same-day refunds above the cashier limit, any offset, and any hold need a second staff member. Use the same dual-control mindset you already use for disburse and large repayments.
- Post the LMS repayment so the schedule matches reality (Cashier / Teller). Post the portion that clears today’s due under your waterfall. For a next-due credit, post the excess in the way your LMS and desk log agree (often a second repayment line or a memo plus schedule note). PesoLend posts repayments, receipts, and schedules; it does not ship a separate overpayment module today — a desk log plus correct repayment posting is the honest setup.
- Close the cash and the ticket (Cashier + BM). Refunds leave the drawer; credits stay in the book. Either way, the end-of-day float must explain the movement — same discipline as end-of-day float reconciliation. File the consent note on the loan; if the borrower later asks for a statement, the excess line should be obvious (see borrower statements that reduce support tickets).
Worked peso example (illustrative)
All figures below are illustrative for training a desk — not a real borrower.
| Line | Amount (₱) |
|---|---|
| Scheduled due today (interest + principal installment) | 3,200 |
| Cash received at counter | 5,000 |
| Excess | 1,800 |
| Next installment on schedule | 3,200 |
Path A — apply to next due. Post ₱3,200 against today’s due. Record ₱1,800 as credit toward the next installment. After posting, next due shows ₱1,400 remaining (3,200 − 1,800). Receipt shows ₱5,000 received. Borrower leaves with a note: “₱1,800 applied to next due.” No cash leaves the drawer for the excess.
Path B — same-day refund. Post ₱3,200 against today’s due. Refund ₱1,800 from the cashier float with a dual-signed refund slip. Receipt shows ₱5,000 in and ₱1,800 out. Drawer net for this ticket: +₱3,200, which matches the LMS repayment.
Path C — offset another loan. Borrower has Loan B with ₱1,500 past due. With written consent, apply ₱1,500 of the excess to Loan B’s arrears and ₱300 as next-due credit on Loan A (or refund the ₱300). Two LMS posts, one consent slip, one receipt for the ₱5,000 intake.
Training tip: run all three paths on the same ticket in a dry run so cashiers see how the drawer and the schedule diverge when step 6 is skipped.
Mistakes that create disputes
- Posting the full ₱5,000 as “principal only” without a policy. That silently shortens tenure and surprises the borrower at the next visit.
- Writing the receipt for ₱3,200 while keeping ₱1,800 “for later.” That breaks cash–LMS integrity and fails any serious audit.
- Auto-offsetting another loan without consent. Even if it helps PAR, it feels like a seizure to the borrower.
- Mixing overpayment with pre-termination. Closing a loan needs a payoff quote, not a next-due credit.
- No desk log. When the only record is a chat message, the Monday argue starts from zero.
Who this is for, and who can skip it
This is for PH money lenders, financing companies, and MFI branches where cash or over-the-counter transfers regularly exceed the posted due — weekly collectors, market-day pay points, and one-desk branches especially. If every payment is exact (salary deduction or fixed auto-debit with no walk-ins), you still need a rare-case refund path, but you can keep a one-page policy instead of a daily board.
This article is general operational guidance for lending desks. It is not legal, tax, or financial advice. Civil Code Articles 2154–2156, SEC rules for lending/financing companies, and BSP rules where they apply to your license can all matter; confirm with your compliance officer or counsel before you change customer-fund handling.
Where PesoLend fits today
In PesoLend, staff can post repayments against loan schedules, issue receipted collection records, review borrower statements, and use branch-scoped roles with maker-checker on sensitive money movements. There is no dedicated overpayment module today — and you should not wait for one. Keep a simple desk log (loan ID, due, received, excess, disposition, two signatures), post the repayment so the schedule matches, and use statements when the borrower asks what happened to the excess. Existing teams can log in to PesoLend to pull today’s due before the cashier accepts the cash.
Frequently asked questions
Should we always refund excess payments?
No. Many active borrowers prefer a next-due credit. Refund when they ask, when the loan is already closed, or when your policy forbids holding unidentified credit. Always document the choice.
Can we keep a small excess as a fee?
Only if your contract and regulator-facing disclosures already allow that fee and the borrower agreed. Silent conversion of excess into a fee is how complaints start. When in doubt, refund or credit next due.
What if the borrower overpays by transfer after hours?
Same three dispositions, but the refund path usually waits for the next banking window. Log the excess when the transfer is matched to the loan; do not leave it as unmatched float overnight without an owner.
Does the LMS need an overpayment button?
Helpful, not required. Correct repayment posting plus a desk log and dual-signed refund slips already close most gaps for small PH lenders.
Next step: print the decision table, add your peso thresholds and signers, and run one dry-run ticket this week so every cashier can compute due / received / excess without calling the branch manager.