This guide is part of a phased educational application. Behaviour is labelled as planned, demonstrated or verified. Examples use synthetic data and simulated money; a real-money launch would require separate commercial, legal, security and operational decisions.
A funding reservation is only the beginning of servicing. The application needs a dated repayment schedule, an explainable loan position and a way to handle missed, partial, unknown, corrected and early-settlement events.
The schedule describes what is expected. Confirmed receipts describe what actually arrived. Arrears are calculated from explicit due-date, calendar, rounding and grace-period rules. A payment plan, waiver, settlement quote or hardship arrangement is a recorded change with authority and an effective date.
Keep closure precise
Paid closure, accounting write-off, debt release and a borrower stopping payments are different outcomes. The user experience should explain which one occurred and why. Statements must identify their source and date so a later correction can be understood.
Practise, then reflect
Your turn to make the decision
Design a repayment timeline with one confirmed payment, one unknown payment and one missed instalment. Identify what the borrower, operator and funding partner can each see.
Compare your reasoning with mine
The schedule remains an expectation, confirmed receipts update the authoritative position, unknown payments remain under investigation and arrears are calculated from defined due dates. A write-off or closure decision is recorded separately from borrower repayment.
Take it one step further
Which correction should create a linked new record rather than changing the original financial event?