If your incentive plan only pays for loans released, you are paying for tomorrow’s PAR. Loan officer incentive plan Philippines PAR design is the craft of growing disbursements without teaching officers to book hope. This guide stays commercial HR-and-ops — not a ₱10k product pricing lecture and not a claim that PesoLend ships a full HR performance module.
You will get collections-weighted formulas, clawbacks that survive a Friday argument, and scorecard practices officers cannot easily game. Use PAR reports, branch roles, and basic LMS reports as the evidence layer. The scorecard itself is your buyer practice.

What breaks when incentives chase volume alone
A desk in Marikina paid a flat kicker per booked loan above target. Disbursements jumped hard in six weeks. PAR 30 followed. Officers had learned to say yes to cousins, to stretch KYC, and to promise restructure later. The plan did exactly what it paid for.
MFI incentive design SEA shops repeat this pattern whenever head office shouts growth without a collections weight. Disbursement KPI without PAR spike is not a slogan — it is a formula with teeth and a published clawback window.
Design principles before the spreadsheet
- Pay for booked quality, not for ink on a form. A loan that hits DPD-7 in fortnight one should not fund a full bonus.
- Weight collections as heavily as release. Many PH desks land near 40/40/20: disbursement, on-time collection, file hygiene.
- Claw back on early default. Write the window (for example, first four dues) in the plan officers sign.
- Cap exceptions. Manager overrides that skip KYC should reduce, not increase, variable pay.
- Publish the math. If officers cannot recompute their bonus from LMS reports, they will invent side deals.
A collections-weighted incentive sketch
Example shape for a two-officer branch with average ticket around ₱10,000 (~$175): base variable pool tied to interest collected that month (not principal disbursed); a small flat kicker only for loans still current through first four dues; a PAR brake that cuts variable pay when personal book PAR 30 exceeds target; a hygiene gate that freezes kickers while incomplete files stay high.
This is not universal pricing advice — it is a shape. Your peso numbers must match your margin. The shape matters: cash-in and early performance fund the bonus, not vanity volume.

Scorecards officers cannot easily game
As a practice, officer scorecards should pull from PAR, arrears, disbursement counts, and repayment posting — not from a selfie of a signed form. Branch roles help: officers see their book; managers see overrides.
Anti-gaming rules worth writing: no credit for loans rewritten within 14 days to reset delinquency cosmetics; no credit for undeclared related parties; partial pays count only when posted; transfers between officers require acceptance so PAR dumping is visible. You do not need a shipped HR module to run this. You need honest reports and a one-page plan ops and people leads both sign.
Clawbacks that survive real arguments
Write clawbacks in the language your team actually uses. Put examples with pesos. Process: month-end report lists clawback candidates; manager confirms; variable pay adjusts next cycle. Keep evidence in the LMS loan file, not in a private sheet the auditor never sees.

Multi-branch twists
When profit leaks in approvals across branches, incentives must not reward the leak. Tie origination credit to the originating officer and approval exceptions to the approver’s quality score. See high-margin segments, approval leaks, repayment discipline, and pricing for plan fit — without inventing public price points here.
30-day rollout without freezing growth
- Week 1: Freeze the old volume-only plan. Publish new weights for comment.
- Week 2: Shadow-run new scores beside old pay.
- Week 3: Go live with clawbacks; sample ten loans for related-party and rewrite games.
- Week 4: Adjust caps, not principles, after structural shocks.
Communicate like adults: growth still matters; unpaid growth is expensive.
What not to claim on day twenty
Do not sell officers an AI-style scoring fantasy or a polished HR suite you do not run. Do use PAR, arrears, roles, and reports you actually have. Incentive design is policy plus evidence. The LMS is the evidence locker.
(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.
Weekly scoreboard columns that keep officers honest
Publish a Monday sheet every officer sees: loans released last week, loans still current through dues one to four, interest collected, PAR 7 and PAR 30 on the personal book, incomplete files count, overrides used, and clawback candidates. If your LMS reports can export these slices, stop retyping them into decorative slides. Managers in Cavite who review this board in fifteen minutes prevent the month-end surprise where the “top producer” is also the top early default.
Tie coaching notes to specific loan IDs. Ask what was known at booking, what was skipped, and what the incentive made attractive. Then recompute variable pay under clawback rules in front of the officer. Predictable math changes behavior faster than slogans about quality.
Segment-aware kickers without black-box scoring
If reports show market vendors in one barangay repay cleaner than certain salary-top-up patterns near a jeepney terminal, do not pay identical kickers for both. Segment-aware incentives are still human policy. You are reading repayment discipline by segment and paying accordingly so disbursement growth points at books that fund salaries next quarter. Owners who fear slower growth should see blended math: flashy volume with worse PAR often destroys more cash than modest growth with stable PAR.
Closing
Officer incentive plans that grow disbursements without inflating PAR pay for collected quality, brake on early default, and publish math officers can recompute. Collections-weighted design beats volume theater in every barangay book that wants to still be open next year.
Build the reports-backed scoreboard habit inside your LMS login at https://pesolend.com/app/login.