Not every peso past due deserves another motorcycle trip. Cost to collect by DPD bucket Philippines small lenders should know where chasing stops paying — before pride spends the margin. This is collections economics, not a week-one delinquency narrative and not a claim that you run a full cost-curve analytics suite.
Use basic PAR, arrears, and work practices on reports. Soft path: queues and arrears visibility help officers spend effort where return still exists.
Name your effort costs
Collections cost curve small lender math starts with honest unit costs: SMS batch, officer call-minute, branch visit, and field ride across barangays. Example sketch only: SMS is cheap, calls cost time, visits can run ₱150–₱400 depending on traffic. Your numbers will differ; the habit of naming them should not.
When to stop chasing DPD
Compare expected recovery in a bucket with cost of the next action. If a small balance at deep aging needs two field visits plus manager time, and historical recovery in that bucket is thin, expected value may not clear the effort. LMS collections effort ROI is that comparison done weekly — on a sheet if you must — not a fantasy analytics suite.
Channel mix by bucket
- Pre-due to DPD-3: reminders and polite calls.
- DPD-4 to 14: calls, guarantor notify, early visit if ticket mid or high.
- DPD-15 to 30: structured visits, manager review, restructure fork if fit.
- DPD-31+: selective field, settlement policy, or exit path — stop daily chase theater.
Work queues should sort by expected value and promise freshness, not only by aging macho points.
On-site companions
Read collections and retention, P&L reading, late fees, and pricing.
21-day practice
- Estimate unit costs with your team.
- Tag last month’s actions by bucket.
- Build a stop-chase rule for low expected-value tails.
- Rework queues toward expected value and fresh promises-to-pay.
Success: fewer empty rides, steadier margin, collectors less burned out in Manila heat.
(1) Worked example from a Metro Manila desk
Imagine a cashier in Quezon City closing a busy Tuesday: the numbers on the screen and the drawer only match when every repayment was posted before the count. The same discipline applies to this topic — write the rule, name the owner, and refuse chat-only exceptions. When a new hire arrives in week three, they should inherit a ritual, not a mystery. That is how Philippine one-desk and small-branch shops keep margin without theatrical software claims.
(2) Provincial desk notes (Cebu, Iloilo, Davao)
Outside Metro Manila, courier delays and thinner staff benches make written cadence even more important. A Cebu side desk cannot assume HQ will answer a float shout at 9 p.m. An Iloilo branch cannot assume the guarantor will walk in twice. A Davao collector cannot burn a full tank chasing zero-EV accounts. Localize the clocks and buffers; keep the principles identical: visible loans, visible repayments, named approvals, coded exceptions.
(3) What “good” looks like after two weeks
You will know the habit stuck when Friday sampling finds consistent language in loan notes, when officers can recompute the same KPIs from the same reports, and when borrowers hear one policy story instead of three. If group chat still hosts the real policy, you are not done. Move decisions into the LMS file and the signed one-pagers. Thin ops beat folklore.
(4) Common objections — and calm answers
“Too slow.” Faster than reconstructing a weekend of missing posts or a month of soft defaults. “Borrowers will leave.” Clear clocks and gates retain the borrowers you want. “We need AI.” You need arrears truth and human follow-up first. “We need a new module name.” You need roles, reports, and maker-checker on the Must list you already have.
(5) Worked example from a Metro Manila desk
Imagine a cashier in Quezon City closing a busy Tuesday: the numbers on the screen and the drawer only match when every repayment was posted before the count. The same discipline applies to this topic — write the rule, name the owner, and refuse chat-only exceptions. When a new hire arrives in week three, they should inherit a ritual, not a mystery. That is how Philippine one-desk and small-branch shops keep margin without theatrical software claims.
(6) Provincial desk notes (Cebu, Iloilo, Davao)
Outside Metro Manila, courier delays and thinner staff benches make written cadence even more important. A Cebu side desk cannot assume HQ will answer a float shout at 9 p.m. An Iloilo branch cannot assume the guarantor will walk in twice. A Davao collector cannot burn a full tank chasing zero-EV accounts. Localize the clocks and buffers; keep the principles identical: visible loans, visible repayments, named approvals, coded exceptions.
(7) What “good” looks like after two weeks
You will know the habit stuck when Friday sampling finds consistent language in loan notes, when officers can recompute the same KPIs from the same reports, and when borrowers hear one policy story instead of three. If group chat still hosts the real policy, you are not done. Move decisions into the LMS file and the signed one-pagers. Thin ops beat folklore.
(8) Common objections — and calm answers
“Too slow.” Faster than reconstructing a weekend of missing posts or a month of soft defaults. “Borrowers will leave.” Clear clocks and gates retain the borrowers you want. “We need AI.” You need arrears truth and human follow-up first. “We need a new module name.” You need roles, reports, and maker-checker on the Must list you already have.
Building a simple expected-value sort
For each arrears account, sketch expected recovery percent by bucket from your last quarter, multiply by balance, subtract the peso cost of the next best action. Sort the queue by that residual. It will feel wrong the first week because the oldest balance is not always on top. That discomfort is the point. Ego sorts by age. Margin sorts by expected value.
Re-estimate bucket recovery rates quarterly. Typhoon months and school-opening months change curves. Do not freeze a January curve through September without looking.
Talking to collectors about stop-chase rules
Collectors fear looking lazy. Show them the math and reassign saved hours to amber pre-DPD7 work where recovery is cheaper. Pride moves upstream. Celebrate prevented DPD-7 as loudly as you once celebrated dramatic late recoveries.
Implementation checkpoint 1
Checkpoint 1 for this playbook: confirm the written one-pager exists, confirm one named owner in the branch, confirm last week’s sample audit happened, and confirm exceptions carried reason codes. Philippine desks in Manila, Cebu, and Davao that skip checkpoints recreate folklore inside two pay cycles. Keep the checkpoint boring and weekly.
If the checkpoint fails, pause new process complexity. Fix the broken step before adding another form field. Thin ops means fewer steps done every time — not more steps done rarely. Log the checkpoint result in a shared branch note dated in Asia/Manila local time so remote owners can see it.
Implementation checkpoint 2
Checkpoint 2 for this playbook: confirm the written one-pager exists, confirm one named owner in the branch, confirm last week’s sample audit happened, and confirm exceptions carried reason codes. Philippine desks in Manila, Cebu, and Davao that skip checkpoints recreate folklore inside two pay cycles. Keep the checkpoint boring and weekly.
If the checkpoint fails, pause new process complexity. Fix the broken step before adding another form field. Thin ops means fewer steps done every time — not more steps done rarely. Log the checkpoint result in a shared branch note dated in Asia/Manila local time so remote owners can see it.
Implementation checkpoint 3
Checkpoint 3 for this playbook: confirm the written one-pager exists, confirm one named owner in the branch, confirm last week’s sample audit happened, and confirm exceptions carried reason codes. Philippine desks in Manila, Cebu, and Davao that skip checkpoints recreate folklore inside two pay cycles. Keep the checkpoint boring and weekly.
If the checkpoint fails, pause new process complexity. Fix the broken step before adding another form field. Thin ops means fewer steps done every time — not more steps done rarely. Log the checkpoint result in a shared branch note dated in Asia/Manila local time so remote owners can see it.
Implementation checkpoint 4
Checkpoint 4 for this playbook: confirm the written one-pager exists, confirm one named owner in the branch, confirm last week’s sample audit happened, and confirm exceptions carried reason codes. Philippine desks in Manila, Cebu, and Davao that skip checkpoints recreate folklore inside two pay cycles. Keep the checkpoint boring and weekly.
If the checkpoint fails, pause new process complexity. Fix the broken step before adding another form field. Thin ops means fewer steps done every time — not more steps done rarely. Log the checkpoint result in a shared branch note dated in Asia/Manila local time so remote owners can see it.
Implementation checkpoint 5
Checkpoint 5 for this playbook: confirm the written one-pager exists, confirm one named owner in the branch, confirm last week’s sample audit happened, and confirm exceptions carried reason codes. Philippine desks in Manila, Cebu, and Davao that skip checkpoints recreate folklore inside two pay cycles. Keep the checkpoint boring and weekly.
If the checkpoint fails, pause new process complexity. Fix the broken step before adding another form field. Thin ops means fewer steps done every time — not more steps done rarely. Log the checkpoint result in a shared branch note dated in Asia/Manila local time so remote owners can see it.
Closing
Cost-to-collect by DPD bucket tells PH small lenders where chasing stops paying. Use basic reports and honest effort math. Protect margin without performing toughness.
Prioritize queues from https://pesolend.com/app/login.