Loan outcomes and servicing
How to interpret loan status, arrears, schedules, classification, and provisioning results.
Loan servicing is largely driven by posted Transactions and COB processes. The Loan Contract page brings their operational results together; it is not a manual substitute for those processes.
Access required
You need Read Loan Contract and data-access scope over the contract. Related Transactions, Forward-Dated Transactions, Accounts, and Facilities retain their own Read permissions and scope rules when you follow their links.
Understand the contract status
Open Loans → Loan Contracts and select a contract. The header shows the stored Contract status and maker-checker record status. The Servicing & Variations tab can additionally show an effective status derived from the latest disbursement attempt.
Common outcomes include:
| Status | Meaning |
|---|---|
| Booked | Contract, Account, Facility linkage, and schedule exist, but disbursement has not completed. |
| Disbursement Pending | An immediate disbursement Transaction is awaiting posting. |
| Disbursement Failed | The latest disbursement posting attempt failed. |
| Disbursed / Active | Funds have been posted and the exposure is being serviced. |
| Matured | The scheduled contractual term has reached maturity; balances and arrears must still be reviewed. |
| Defaulted | Servicing classification identifies the contract as defaulted. |
| Closed | The lending exposure has completed its closure path. |
The effective Pending and Failed values are display outcomes; they do not replace the persisted Contract status.
Monitor repayments and arrears
Use Schedule for installment-level expected, paid, outstanding, and past-due amounts. Use Servicing & Variations for the summarized past-due principal, interest, charges, penalties, maximum days in arrears, and next due date.
Repayments are ordinary financial Transactions with loan-repayment intent. After successful posting, servicing allocates the payment against schedule components and updates the visible schedule progress. Do not infer successful repayment from a Captured or merely Authorized Transaction; confirm its posting status and the refreshed schedule.
Schedule versions
The Contract identifies its current schedule version. Booking creates the first Active version. An applied Reschedule, Restructure, Top Up, or qualifying Top Down can create a later version and make it current while preserving prior versions for traceability.
Classification and provisioning
COB evaluates eligible loans using the configured classification and provision rules. The Contract's servicing information records the classification business date and last serviced business date.
Open Provisioning to see each available result, including:
- the COB run and business date;
- classification and exposure used;
- required and previous provision amounts;
- the provision delta and configured rate;
- whether the result posted, skipped, or failed;
- linked posting references and technical identifiers.
Provision results are evidence, not editable Contract fields. Correct the underlying configuration or processing problem and use the governed COB path; do not attempt to edit a result on the Contract.
For processing failures, continue with COB, reports, and delivery troubleshooting.