A borrower who paid clean for ten weeks and then went quiet is not the same problem as a week-one no-show. Mid-term stalls need a different fork: restructure the schedule, or rewrite the loan. Loan restructure vs rewrite Philippines desks get wrong usually softens the book into a polite default.
This piece is for small lenders and MFIs who want policy gates, yield math you can explain in Tagalog or Cebuano, and an LMS loan-lifecycle habit — amend schedule or rewrite as ops practice with maker-checker on any new disburse — not a mythical restructuring engine. Keep amended terms next to the original history in PesoLend features so officers stop inventing parallel notebooks.
Define mid-term stall before you invent mercy
Call it mid-term when at least 40% of scheduled installments were paid on time, the account is not yet a hard write-off candidate, and the borrower still has a reachable number. A Divisoria vendor on week 12 of 20 who missed two dues after a supplier shock fits. A borrower who never intended to pay does not.
If your only playbook is the week-one delinquency script, you will either harass a salvageable account or bless a soft default with a “restructure” sticker. Mid-term loan restructure small lender policy exists to separate temporary cash pain from character risk.
Write the definition on one page and train it in a Monday huddle in Makati, Cebu, or Cagayan de Oro. If officers cannot recite the definition, they will improvise — and improvisation is how yield dies politely.
Restructure: keep the loan ID, change the path
Restructure means the same loan continues. You amend dates, installment size, or temporary handling per written policy. Principal truth stays visible. Officers in Bulacan and Batangas should open the file and see original terms, amendment date, who approved, and why.
Good restructure triggers include a documented income interruption with a return date, partial pays still arriving, a cooperative guarantor, and yield after amendment that still clears your floor. Bad triggers include “para hindi mukhang delinquent,” officer bonus protection, or hiding PAR from a visiting partner. Those are soft defaults with paperwork.
Operationally, mid-term restructure should feel slower than a chat promise and faster than a full underwrite. Collect proof, run the gate, amend the schedule, tell the borrower the new dates in plain words, and log the SMS or visit note.
Rewrite: close clean, open deliberate
Rewrite means you close or settle the old loan under policy and book a new loan with new terms. Use it when the old schedule is fiction — tenure no longer matches cash cycle, product type was wrong, or concentration risk needs a hard reset.
Rewrite policy yield protection starts with one rule: no silent principal forgiveness inside a “new” loan without a manager-coded loss. If you forgive ₱3,000 of a ₱20,000 balance to “help,” your yield math must show that gift as cost, not as marketing. Maker-checker on the new disburse is non-negotiable when any concession exists.
Yield math on a phone calculator
Example: ₱15,000 book, 16 weeks, expected finance charge ₱3,600. At week 10 the borrower has paid ₱9,000 total, with roughly ₱6,200 still outstanding under your waterfall. They propose skipping two weeks then stretching the rest.
- Restructure A: pause two weeks, extend two weeks at end, keep installment size. Extra days of capital outstanding cost float — price that against retention.
- Restructure B: cut installment 20% and add four weeks. More interest days, higher completion odds, longer officer attention.
- Rewrite: settle remaining into a new 12-week note at current product rate, with a documented fee if policy allows. Cleaner reporting; higher process cost.
Pick the path where expected collected cash minus extra ops cost beats a probable charge-off. If both paths lose, collect hard or exit — do not decorate the loss with kindness language.
Policy gates before any LMS click
Write gates on one page and refuse exceptions by chat:
- Minimum clean weeks before restructure eligibility (for example, eight on-time pays).
- Maximum restructures per loan (often one).
- Manager approval above a peso threshold or tenure stretch.
- No restructure if contact data is rotten or the last three reminders failed.
- Rewrite requires dual control if any principal concession exists.
- No restructure solely to protect an officer’s disbursement score.
LMS restructure workflow PH shops can run today: status note, amended schedule fields, approval role, audit trail. That is loan lifecycle discipline — not an AI judge and not a branded engine you do not have live.
Conversation script that protects dignity and yield
In a Cebu or Quezon City visit, say the fork out loud: “We can keep this loan and change the dates, or we close this one and open a new one with clearer terms. Both need proof and an approval. What changed in your cash this month?”
Borrowers respect clarity. Officers who mumble “ayosín natin” without a gate create folklore. Folklore becomes the real policy, and folklore never shows up correctly in PAR reports.
Bring the guarantor into the same conversation when the stall is material. A co-maker who hears the new dates is less likely to claim surprise later. Store the consent note in the borrower file — SMS acknowledgment is enough; you do not need full e-sign theater on day twenty.
How this differs from collections theater
Collections that protect cashflow without killing retention still apply for broken promises. Mid-term restructure is for salvageable books with a new cash story. Do not use late-fee waivers as a fake restructure. Do not use restructure to bury fees you were afraid to explain at booking.
If the borrower is simply avoiding you, stay in collections mode. If the borrower is reachable, paying partials, and showing a temporary shock, open the policy fork. Mixing the two modes confuses officers and teaches borrowers that silence earns softer terms.
See also: collections that protect cashflow, repayment discipline, late fees and penalties, and features.
Worked desk example: market vendor in Sta. Mesa
Rosa took ₱12,000 over 12 weeks for inventory. Weeks 1–7 clean. Weeks 8–9 partial. Week 10 missed after a supplier delayed goods. Officer proposes cutting dues by 25% and adding three weeks. Manager checks gates: clean history exists, phone works, guarantor confirms, yield still above floor. Restructure approved same day. LMS shows amendment; collections calendar updates; no rewrite needed. Two months later Rosa finishes. Compare that to a silent “sige bayaran mo when you can” that would have aged into PAR without a date.
30-day policy install
- Week 1: Draft the one-page gates. Train officers on definitions with two sample files.
- Week 2: Tag five historical stalls — which should have been restructure vs rewrite?
- Week 3: Enforce maker-checker on any rewrite with concession. Kill chat-only approvals.
- Week 4: Review yield on amended accounts versus charge-offs avoided. Adjust gates if officers game the minimum clean weeks.
Success looks like fewer “special cases” in group chat and more coded amendments in the loan file. Managers in Ortigas and Davao should be able to sample ten files on Friday and see consistent language.
Field notes from desks that got this right
Officers in provincial and Metro desks who sustain the habit share the same unglamorous traits: they write codes the same way every night, they refuse chat-only payments, and they treat a balanced drawer as a result worth logging — not as an excuse to skip the sheet. Copy the discipline before you copy anyone’s spreadsheet template.
If your team is new, shadow the close for three nights with a printed checklist. On night four, the cashier leads and the owner only signs. By night seven, the ritual should feel as automatic as locking the shutter. That is how end-of-day and policy habits survive staff turnover in Quezon City, Cebu, and Davao alike.
Documentation pack for a mid-term decision
Before a manager signs, the file should hold: latest payment history print or screen, borrower explanation in one paragraph, supporting note (medical, supplier delay, job pause), guarantor acknowledgment, proposed new schedule, and yield check initials. SMS threads can be pasted into the loan note. You are building an audit story, not a novel. Officers in Pampanga who skip the pack create “he said” fights when the borrower stalls again.
Store the pack in the borrower CRM fields and loan notes you already use. No full e-sign required for day-twenty discipline — clear consent text and a dated officer attestation beat a fake digital ceremony.
SEA-adjacent note without pretending packs are live
Indonesian or Malaysian group networks sometimes use committee mercy differently than a Philippine one-desk shop. If you operate across borders later, keep local policy packs separate. For this article’s PH/SEA readers, the universal rule is the same: define stall, pick restructure or rewrite, show yield, dual-control concessions. Do not import another country’s product marketing as if it were your live module list.
Closing
Restructure vs rewrite when Philippine borrowers stall mid-term is a policy fork with yield math, not a kindness contest. Keep the loan ID when the story is temporary. Rewrite when the contract is fiction. Record who approved. Protect the book without soft defaults dressed as empathy.
Run that lifecycle with clear approvals inside the LMS at https://pesolend.com/app/login.