Servicing & collections
The part that runs for three years
Origination is a moment; servicing is the entire life of the loan. Getting the arithmetic exactly right and surfacing problems early is what determines whether a digital lending book performs.
Arithmetic
Money is an integer, never a float
Every amount in Khepee is an integer number of paisa. It sounds pedantic until you amortise across 36 instalments in floating point and find the schedule no longer sums to the principal.
- All amounts stored and transmitted as integer paisa
- A fractional amount is rejected at the API boundary, not silently rounded
- Rounding remainder assigned deliberately to the final instalment
- Formatted to NPR at the interface layer only
Schedules
One schedule, visible to everyone who needs it
The schedule is generated once at activation and becomes the reference for the borrower, your officers and your reporting. There is no second version in a spreadsheet.
- Generated at loan activation, from the terms actually approved
- The borrower sees the same schedule your officers see
- Each instalment tracked individually — paid, partial, overdue
- Early settlement handled explicitly rather than as an exception
Reminders
Contact before the due date, in the borrower’s language
Most missed instalments are forgotten, not refused. Reminders sent a few days ahead, in Nepali or English, recover a meaningful share of them without any collections effort at all.
- Configurable reminder schedule ahead of each due date
- SMS and push, behind a provider interface you choose
- Sent in the borrower’s selected language
- Every notification recorded, so a dispute about contact has an answer
Overdue handling
Escalation on policy, not on someone remembering
Day one
The instalment is flagged overdue by a job that runs daily, not by a month-end review.
Early contact
Automated reminders continue on your configured cadence.
Officer assignment
The account appears in a collections queue with its full history attached.
Escalation
Movement to defaulted requires a written reason, and is fully audited.
Cure
A defaulted loan that resumes payment can return to active — the state machine supports recovery, not just failure.
Conduct
Collections that will not embarrass your institution
Digital lending has a reputational problem in several markets precisely because collections practice was left undefined. Khepee constrains it, and the code of conduct is published rather than internal.
- No access to borrower contacts, photos or location — the app does not request those permissions
- Contact frequency and hours bounded by configuration
- No third-party disclosure of a borrower’s arrears
- Every contact logged, so conduct can be audited rather than argued about
Oversight
Ageing you can see before it becomes a problem
Your team sees the portfolio position and ageing continuously rather than in a monthly report assembled after the fact.
- Outstanding principal, disbursement volume and ageing buckets, live
- Overdue accounts ranked by exposure and days past due
- Cohort performance by product and by origination month
- The same underlying data that produces your NRB extract
Khepee provides the technology; your institution provides the credit
Khepee is a technology service provider operated by Lacspace Corporation Pvt. Ltd. It is not a bank or financial institution, does not lend, does not accept deposits and does not hold customer funds. All credit decisions, pricing and lending terms are set by the partner institution licensed by Nepal Rastra Bank. Khepee makes no claim of NRB licensing, approval or endorsement.
Coming soon
Stress-test the servicing model
Bring a real amortisation schedule and we will reconcile it against ours, to the paisa.