New: the Kontor regulatory map, with UK, EU and US obligations mapped to controls and evidence. Read it

[ Blog / Platform ]

Loan servicing: what has to happen after drawdown

The Kontor team·7 October 2026·4 min read

A borrower draws down on a Monday. From that moment, the lender owns a cash flow that has to be tracked, billed, collected, reported and, when things go wrong, remediated, across the full life of the loan. Most of the operational and regulatory risk in consumer credit sits here, not in the credit decision.

Loan servicing is the set of processes and systems that manage that obligation: calculating what is owed and when, communicating it correctly, applying payments in the right order, handling changes mid-term and producing a ledger that a regulator or auditor can reconstruct. Get any one of those wrong and the consequences range from a mis-stated APR to a Consumer Duty breach to an upheld FOS complaint.

What a servicing layer actually contains

Servicing is not a single function. It is a stack of interdependent jobs, each of which has to be correct before the next one can run. What a loan management system actually has to do covers the broader platform picture; here is what lives specifically in the servicing layer.

  • Interest accrual and billing. The ledger must calculate interest daily, apply the contractual rate, and produce a statement that matches what the consumer credit agreement promised. Under CONC 6 and the Consumer Credit Act, the figures on the statement must be reconcilable to the original agreement.
  • Payment processing and allocation. When a payment arrives, the order in which it clears principal, interest, fees and charges is not arbitrary. The Consumer Credit Directive and most UK regulated agreements specify allocation order. Applying a late payment to principal before interest understates the cost of credit on the account.
  • Rate and term changes. A variable-rate mortgage or revolving facility requires the ledger to reproject the schedule every time the rate moves. That reprojection must be stored as a versioned event, not an overwrite, so the history of what was charged and why is recoverable. Why your loan ledger needs two clocks explains why transaction time and business time have to be kept separate for this to work.
  • Arrears and past-due handling. When a payment is missed, servicing has to recognise the arrears, apply any contractual default interest correctly, trigger the right CONC 7 forbearance assessment and communicate with the borrower within the required timeframes. Past-due credit: how a ledger should handle it goes into the mechanics of that sequence.
  • Account closure and redemption. A loan that ends early, whether by full prepayment or sale, needs a final settlement figure that is accurate to the day, with any rebate of charges calculated under the Consumer Credit Act rule 78 or the actuarial method as the agreement specifies.

How servicing holds up under scrutiny

A regulator or complaints handler will reconstruct a disputed account from the ledger. That means every servicing action has to leave a complete, ordered record. The sequence that makes an account auditable is as follows.

  1. Event sourcing the ledger. Every charge, payment, rate change and status transition is written as an immutable event with a timestamp. Nothing is updated in place. The current balance is derived by replaying the event log, not by reading a field that has been overwritten.
  2. Jurisdiction rules applied at execution time. The allocation order, the arrears communication timeline, the rebate method: these differ by market. A servicing layer that hard-codes UK rules cannot be extended to the EU without a rebuild. Jurisdiction packs: one lending platform, many regulators describes how Kontor separates the rule set from the ledger engine so that the same core system can serve multiple markets.
  3. Automated agent actions with auditable procedures. Servicing agents, whether human or automated, should operate from defined procedures that are themselves versioned and logged. When an agent sends a CONC 7 arrears notice or applies a payment holiday, the procedure it followed and the version of that procedure in force at that moment should appear in the audit trail. Agent Operating Procedures: how we make servicing agents auditable covers why this matters under Consumer Duty.
  4. Statement and notice generation tied to the ledger state. The statement a borrower receives must match the ledger at the point it was generated. Reconciliation failures, where the statement figure and the ledger balance disagree, are a common source of upheld complaints and regulatory findings.
  5. Reconciliation and reporting outputs. At month end, the servicing layer must produce a trial balance, an arrears report and, where applicable, regulatory returns. These have to agree with the underlying event log without manual adjustment.

A lender that can replay any account from its event log, show which rule was applied and why, and demonstrate that every borrower communication matched the ledger state at the time, has the foundation for both Consumer Duty fair outcomes evidence and a credible FOS response.

Why a spreadsheet or a simple database is not enough

Many lenders start with a database table that stores the current balance and updates it on each transaction. That works at low volume until someone disputes a charge from eight months ago, a rate change needs to be unwound retroactively, or the business needs to migrate the book to a new system. Without an event log, the historical state of any account is unrecoverable. Migrating a live credit book without a big bang shows how the absence of event sourcing makes migrations brittle and often impossible to do without a service window.

The same limitation applies to rules. A lender that embeds allocation order, rebate calculations and arrears timelines as application code rather than configurable, versioned rules cannot adapt when a jurisdiction changes its requirements, when a product changes its terms, or when an audit reveals that the wrong rule was applied to a cohort of accounts.

Loan servicing is where a lender's obligations to its borrowers and its regulators are discharged, one payment at a time, and the ledger either supports that or it does not.

[ More from the blog ]

Run your receivables on Kontor.

Bring a product spec or a portfolio extract. We'll show you how the ledger, decisions and agents would run it, and what your regulator would see.