Your Spreadsheet Loan Book Is Leaking Money. Quietly.

Your spreadsheet never crashes and never shows an error. It just hands you numbers that are slightly wrong, on a few borrowers, every month, until a borrower proves you wrong to your face.

Why do spreadsheet loan books fail quietly?

A lending spreadsheet does not fail loudly. There is no error message when a penalty goes uncharged or a payment lands on the wrong row. The file opens, the totals add up to something, and everyone moves on. The failure shows up months later as margin you cannot explain and borrowers you cannot convince.

If you run a lending business in the Philippines on Excel or Google Sheets, you are not lazy or careless. You started with ten borrowers and a sheet was the right tool. The problem is that the sheet did not grow with the book. At 150 accounts, the same file that served you well is now costing you money in three specific ways.

Failure mode 1: hand computed interest

Most small Philippine lenders price with flat add-on rates. Say 3 percent per month add-on: a ₱50,000 loan over 6 months carries ₱9,000 of interest, so the borrower pays ₱9,833.33 monthly. Simple. Until someone restructures a loan mid-term, or a borrower prepays two installments, or you onboard a co-maker loan with a different rate.

Now a person is typing formulas by hand. One cell copied down one row too far, one rate typed as 0.3 instead of 0.03, and that account is wrong until someone happens to check it. Nobody checks it, because checking means recomputing by hand, which is exactly the work everyone is avoiding.

Failure mode 2: penalties that never get charged

Your loan agreement probably carries a penalty rule like 5 percent on any amount past due, per 30 days or fraction thereof. That rule requires someone to notice the due date passed, count the days, apply the rate, and add a row. Every day, for every late account.

In practice, penalties get applied when someone remembers. Work through the math on a modest book:

  • 200 active accounts, 30 of them late in a given month
  • Average past due installment of ₱4,000, penalty of 5 percent per 30 days
  • If penalties are only caught half the time, that is 15 accounts times ₱200, or ₱3,000 leaked that month
  • Across a year, ₱36,000 of contractual revenue simply never billed, and the number grows with the book

Worse than the leaked pesos: the borrowers who do get charged notice that others do not. Inconsistent penalties train borrowers that late payment is negotiable.

Failure mode 3: mis-posted payments

A borrower sends ₱3,500 over GCash. The screenshot goes to a staff Messenger thread. Someone types it into the sheet that evening, or the next morning, or after the weekend. Two borrowers named Reyes, two loans for the same borrower, one wrong row, and now one account shows paid while another shows past due.

The borrower who paid gets a collection text. The borrower who did not pay gets silence. One of them is now angry and the other one just learned your records cannot catch them.

The fix for all three modes is the same and it is not a better spreadsheet. It is a ledger that does the computing: interest generated from the schedule, penalties applied by rule on the day they accrue, payments posted against a specific installment in a fixed order, with a timestamp and a reference. When arithmetic is enforced by software, being right stops depending on who typed carefully that day.

What do these small errors really cost you?

When a borrower disputes a balance and your evidence is a spreadsheet only your staff can edit, you have a weak hand even when you are right. You will settle arguments by waiving amounts, because waiving is faster than reconstructing six months of history cell by cell. Each waiver is small. The habit is expensive.

It cuts the other way too. You cannot fully trust your own numbers. Is your portfolio at risk 8 percent or 13 percent? Depends which version of the file you believe.

You do not need a bank core to escape this. You need a loan ledger that knows your products, your penalty rules, and your payment channels, including GCash, and refuses to drift. The spreadsheet was the right tool for ten borrowers. Your book outgrew it, quietly, the same way it fails.

Your book deserves a ledger that cannot drift

We build loan management systems for Philippine lenders: schedules, penalties, and payment posting enforced by the software, not by memory.

See the Lending System We BuiltTell Us About Your Lending Book