The Penalty Clause You Wrote but Never Enforce

The sentence in the contract

Most Philippine lending contracts carry a penalty rule like this: a penalty of 5 percent shall be charged on any installment or portion thereof not paid when due, for every 30 days of delay or fraction thereof. Some add a grace period of 3 or 5 days. One sentence, unambiguous on paper.

Now watch it meet reality. An installment of ₱6,800 falls due on the 10th. The borrower pays ₱4,000 on the 18th and the rest on the 45th day. Quick: what penalty is owed, and on what base? If your answer starts with let me check how we usually do it, the contract is not your penalty policy. Habit is.

What does or fraction thereof actually mean?

Work the clause literally. Fraction thereof means day 1 of delay already triggers a full 5 percent charge, and day 31 triggers the second one. On the example above, assuming no grace period and the penalty base is the unpaid portion:

• Days 1 to 8: the full ₱6,800 is late, so one penalty of ₱340 accrues on day 1
• Day 8: ₱4,000 posts, leaving ₱2,800 unpaid
• Day 31: a second 30 day period begins on the remaining ₱2,800, adding ₱140
• Total penalty by day 45: ₱480, each charge tied to a date and a base

Reasonable people can define the base differently: full installment versus unpaid portion, penalty on principal only versus principal plus interest. How a partial payment is applied against those charges is its own rule worth fixing. Every variant is defensible. What is not defensible is computing it a different way each month, which is exactly what hand computation produces.

Why do hand computed penalties always drift?

Penalty math is not hard. It is relentless. It must run every single day, for every late account, with the day count and the base exactly right. Humans are bad at relentless, which is the same reason spreadsheet loan books leak quietly. The drift shows up in four predictable ways:

Timing drift. Penalties get computed when someone reviews the book, so a borrower who cures quickly is often never charged at all, while one who lingers gets hit with a lump that looks punitive.

Base drift. One staff member charges on the full installment, another on the shortfall. Both are following the rule as they remember it.

Grace drift. The 5 day grace becomes 7 for pleasant borrowers and 3 for difficult ones, applied by mood.

Waiver drift. With no computed figure on record, waiving the penalty is the path of least resistance in any dispute. You cannot hold a line you never drew.

Grace periods deserve a precise definition too

Decide, once: does the grace period waive the penalty entirely if payment arrives within it, or merely delay the start of the penalty clock? Does a payment on grace day 5 sent at 11 pm through GCash count as within grace if it is confirmed the next morning? These sound like fine print, and they are exactly the fine print borrowers argue about. Pick your answers and encode them.

What enforcement by the ledger looks like

A proper lending system treats the penalty clause as configuration, not as a memo. You set the rate, the period, the base definition, and the grace behavior per loan product. Then, every night, the system checks every account: installments past grace get their penalty rows created automatically, dated, with the base and computation stored. The next 30 day boundary schedules itself.

Waivers still happen, and should. The difference is that a waiver becomes a recorded decision with an author and a reason, applied against a computed charge, instead of a silent gap where a charge never existed. Your borrowers get consistency they can verify on a printed statement of account, which reads as fairness. Your book gets the revenue the contract already earned. And your staff stop being the penalty calculator, which was never a job they could do every day without missing.