Field Complaint Log That Survives a BSP Spot Check

Educational only — not legal or regulatory advice. Confirm current BSP and local requirements with your compliance counsel before changing policy.

When a borrower disputes a fee, a missed receipt, or a rude collection visit, most one-desk Philippine lenders still park the story in a group chat or a notebook. That works until someone asks for a closed trail: who complained, what was promised, who fixed it, and when. A lightweight field complaint log BSP PH lenders can run closes that gap without hiring a compliance team or inventing a ticketing product.

This guide is for owners and branch managers running microfinance or small lending desks who need a repeatable log before the next spot check. You will keep a nine-field sheet, a 15-minute intake ritual, a worked Quezon City example, and a weekly aging review you can finish before Friday float close. Soft note: tools like PesoLend already hold borrowers, loans, repayments, case notes, and branch-scoped roles — use those as the ledger home for the complaint ID. This article is an ops playbook, not a product module name.

What “good enough” looks like on day one

You do not need a CRM or a dedicated complaints suite. You need one shared sheet or LMS note type that every officer can fill in under five minutes, and that a manager can filter by status. Aim for four outcomes:

1. Every complaint has a unique ID and a recorded intake time.
2. The borrower’s claim is separated from the officer’s version of events.
3. A named owner has a due date to respond.
4. Closure notes show what changed (waiver, apology visit, corrected ledger) and who approved it.

If your LMS already supports case notes on the borrower or loan file, use that. If not, a locked Google Sheet or Excel file in the branch shared drive is fine until volume grows. The point of a field complaint log is reconstructability — not software theater.

Minimum fields for a PH field complaint log

Keep columns short so officers actually fill them after a market visit. Nine fields is the bar used in this playbook:

Field	Why it matters	Example
Complaint ID	Audit trail and handoffs	CPL-2026-09-25-03
Borrower / loan ID	Ties dispute to the schedule	LN-88421
Channel	Shows intake pattern	Walk-in / SMS / field visit
Category	Lets you spot systemic issues	Fee dispute / receipt / conduct / data
Claim summary (borrower words)	Preserves the allegation	“Charged late fee though paid Sep 20”
Evidence attached	Speeds investigation	Photo of receipt; SMS screenshot
Owner + due date	Prevents orphan tickets	Ana — respond by Sep 27
Status	Open / Investigating / Resolved / Escalated	Investigating
Resolution + approver	Shows control	Fee reversed; manager signed

Skip free-text essays. One or two sentences per field is enough for a spot check to follow the story. Put the complaint ID in the loan note so collections does not chase while the case is open (unless your policy says otherwise). Related cash-to-ledger habits belong in collection receipt discipline — this log covers disputes, not every routine repayment.

A 15-minute intake ritual after every complaint

Rituals beat memory. Run these five steps before the officer leaves for the next barangay stop:

1. Acknowledge in writing. Text or print a short note: you received the complaint, the ID, and when they should hear back (for example, within two business days). Do not promise a fee waiver in that first message unless policy already allows it.
2. Log before the next collection stop. Do not wait until end-of-day; details fade after three more visits. Capture borrower words first, then the officer’s note in a separate sentence.
3. Park evidence in one folder named by complaint ID — receipts, chat screenshots, call notes. One folder beats ten chat threads.
4. Assign an owner who did not cause the dispute when the complaint is about conduct. Same officer investigating themselves is a red flag in any calm desk review.
5. Update the loan note with the complaint ID so the schedule and the dispute stay linked. Use live LMS case notes / repayment records when you have them — not a second shadow ledger.

Fifteen minutes is the budget for a clean intake, not for solving the case. Investigation can wait for the named owner; intake cannot wait for “after lunch.”

Worked example: three complaints in one Quezon City week

Illustrative desk (not a claim about your book or any regulator finding). A two-desk money lender in Quezon City runs fifteen field visits a day and usually sees two to four complaints a week by SMS or walk-in. Week of 22–26 Sep 2026, three cases hit the log:

ID	Channel	Category	Claim (borrower)	Owner / due	Resolution
CPL-2026-09-22-01	SMS	Fee dispute	“Late fee though paid Sep 20 at market”	Ana / Sep 24	Receipt photo matched; fee reversed; manager approved Sep 23
CPL-2026-09-23-02	Walk-in	Receipt	“Collector took ₱1,200, no stub”	Ben / Sep 25	Late numbered receipt + LMS post under maker-checker; coach logged
CPL-2026-09-25-03	Field visit	Conduct	“Officer shouted in front of neighbors”	Carla (not the officer) / Sep 27	Apology visit scheduled; HR note separate from borrower log

What a spot check can reconstruct in under ten minutes: who complained, which loan, what evidence, who owned the reply, and how the ledger or conduct path closed. What fails without the log: CPL-02 becomes a group-chat rumor, CPL-01 has no fee-reversal proof, and CPL-03 mixes staff discipline into the borrower file until nobody can find either story.

Desk math you can adapt (illustrative): if three fee-dispute complaints a week each take forty minutes of rework when undocumented, that is roughly two hours of manager time — before counting borrower trust loss. The nine-field log does not remove judgment; it stops you from rebuilding the story from memory.

Who this is for — and who should skip

Use this log if you run one to three desks, officers take cash or payment screenshots in the field, complaints arrive by chat or walk-in, and you need a trail that survives a calm BSP-oriented desk review or an internal audit. It also fits multi-barangay money lenders who already struggle with receipt discipline and want disputes tied to the same loan IDs.

Skip a spreadsheet-only approach if you already process dozens of formal complaints a week — then you need workflow with permissions, not a shared file. Skip this playbook if every dispute is already logged in your LMS with maker-checker, aging reports, and a named compliance owner. Your problem is underwriting or product rules, not intake hygiene.

Field-heavy shops should pair this log with branch habits covered in field collections solutions and keep money-desk roles clear per money lender operations — complaint ownership is a role habit, not a new HR module.

Common traps that fail a spot check

• Group-chat only. Threads get deleted; examiners and owners cannot reconstruct timelines.
• Resolved with no ledger proof. “We explained it” without a corrected entry, signed waiver, or dated note looks unfinished.
• Mixing HR issues with borrower claims. Keep staff discipline in a separate file; the borrower log should stay about the customer.
• No aging. Anything open past your stated SLA (for example, five business days) needs a manager review note.
• Same officer investigates their own conduct case. Assign a second name. Neutrality is part of the trail.
• Promise language in the first SMS. Acknowledge receipt and timing; do not invent waivers mid-route.
• Shadow folders per officer. One shared log, branch-scoped view. Personal notebooks recreate the exact gap you are trying to close.

Cash and float mistakes often sit next to complaint spikes — if officers rush because overnight float is thin, fix the float habit with end-of-day float reconciliation instead of blaming “difficult borrowers.”

Weekly aging review (20 minutes every Friday)

Owners who only open the log when someone shouts will always look unprepared. Run this before Friday float close:

1. Filter status = Open / Investigating; chase anything past due. Write a one-line manager note on each overdue row.
2. Count complaints by category — three fee disputes in one week usually means a product or posting bug, not bad luck.
3. Confirm every Resolved row has an approver name and date. Empty approver = not closed.
4. Export a PDF or CSV snapshot into the month folder so you are not scrambling before a visit.
5. Spot-check two evidence folders: do files match the complaint ID naming rule?

Aging is where systemic issues surface. A rising “receipt” category often means collectors skip stubs under time pressure — train receipt discipline the same week, do not wait for next month’s PAR meeting. Cashier-side controls in money-handling controls for cashiers pair well when walk-in disputes involve till amounts.

Decision framework: log, escalate, or redesign the product

1. One-off fee or receipt dispute with clear evidence → Log, assign, reverse or explain with ledger proof. Close with approver.
2. Conduct complaint → Log in borrower file; open a separate HR note. Different owner for investigation.
3. Same category three or more times in a week → Treat as product or process defect. Pause blaming officers; change the fee rule, receipt booklet, or posting cut-off.
4. Borrower claims payment the LMS never shows → Cross-check receipt discipline and float recon before arguing. Fix the cash–LMS gap first.
5. Complaint volume exceeds what a sheet can age → Move fields into LMS case notes with roles and branch scope. Still do not invent a ticketing product name — use the notes and permissions you already have.

Use this framework in the weekly review, not only when a visitor is expected. Spot checks reward boring consistency.

How LMS case notes help without inventing a module

Public PesoLend framing stays on what Day-20 must already cover: borrowers, loans and schedules, repayments, branches, staff roles, and basic reports. A complaint ID living as a case note on the loan is enough for most one- to three-desk shops. Do not claim an offline field app, AI complaint scoring, native GCash/Maya rails, e-sign waivers, or a dedicated ticketing suite as live features. If you later wire the same nine fields into case notes, the habit above still applies — the fields do not change because the storage moves from Sheet to LMS.

When you are ready to keep notes next to the schedule, start at PesoLend login and brief officers that the complaint ID belongs on the loan, not in a private chat.

FAQs

Do we need a BSP-branded form?
No template in this article is an official BSP form. Use fields that let you reconstruct who, what, when, and how it closed, then confirm any regulator-specific format with counsel. [VERIFY: your license class and any circular that names complaint-handling timelines for your entity type.]

How fast should we respond?
Pick a written SLA you can keep — many small desks use two business days for first substantive reply and five business days for closure or escalation. Publish the SLA to officers; aging against a secret deadline helps nobody.

What if the borrower refuses to give a loan ID?
Take mobile number, full name, and approximate disbursement week; match against the borrower CRM before assigning an owner. Do not invent a loan ID to “close” the row.

Can collectors close their own cases?
Fee and receipt cases may be investigated by the collecting desk with manager approval on the resolution line. Conduct cases need a different owner. Approver ≠ investigator when trust is the issue.

What to do next

Create the nine-field log today, brief officers on the 15-minute intake ritual, and run the weekly aging review every Friday before float close. Once the habit sticks, wire the same fields into your LMS case notes so the complaint ID lives next to the loan — that is the version that survives both operations chaos and a calm desk review. For more field-ops reading, start at the PesoLend blog; to keep notes beside live schedules, use app login.