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

[ Blog / Platform ]

Past-due credit: how a ledger should handle it

The Kontor team·6 October 2026·5 min read

A payment arrives two days late. The question is not whether to charge a fee or send a letter. The question is whether every downstream system, the ledger, the arrears register, the customer communication, the regulatory reporting, all see the same state at the same moment, and whether every action taken from that point is recoverable and auditable. Most servicing stacks answer that question poorly, because past-due logic is scattered across a loan management system, a collections tool and a CRM that were never designed to agree with each other.

The answer is to treat past-due status as a ledger event, not a workflow flag. Once a missed payment is recorded as an immutable fact on the loan account, every subsequent action, fee accrual, arrears staging, forbearance offer, default notice, follows from that single source of truth.

What a past-due event actually contains

A missed payment is not a boolean. It carries state that determines everything a lender is permitted to do next. A well-designed past-due event on an event-sourced ledger holds at least the following fields, each of which is immutable once written.

  • Due date and settlement date, the two clocks a loan account needs: the contractual clock that governs what is owed, and the calendar clock that governs when regulatory obligations and fee permissions are triggered. Conflating them is a common source of mis-stated arrears balances. For more on this distinction, see why your loan ledger needs two clocks.
  • Shortfall amount, the exact gap between what was scheduled and what settled, expressed in the account currency. This figure drives arrears staging and must survive any subsequent partial payment or fee capitalisation without being overwritten.
  • Arrears stage, an enumerated value, not a free-text field, that maps to the lender's defined buckets: current, one to thirty days, thirty-one to sixty, sixty-one to ninety, and so on. Stage transitions are themselves events, not updates to a status column.
  • Regulatory context, the jurisdiction pack in force at the moment of the event. Under CONC 7, for example, a firm must treat a customer in arrears fairly and consider their circumstances before adding charges. Under the Consumer Duty the same firm must assess whether a charge is in the customer's interest. The event record must show which rules applied.
  • Forbearance eligibility flag, a signal computed at the time of the event from income, arrears history and vulnerability indicators, used by servicing agents to route the account correctly without re-running the same logic on every interaction.

How past-due accounts move through the system correctly

Getting past-due logic right is a sequencing problem. Each step must produce a durable record before the next step begins, so that if anything fails mid-process the account can be reconstructed without ambiguity.

  1. Detect and record the shortfall. At the close of the payment window, compare the scheduled instalment against settled receipts. Write the shortfall as an immutable ledger event. Do not update a status field; append a new fact. This is the moment arrears begin for regulatory purposes.
  2. Stage the account. Apply the lender's arrears staging rules to produce an arrears stage event. If the account is already in arrears and this payment widens the shortfall, write a stage-change event with the previous and new stage both recorded. The audit trail must show every transition, not just the current state.
  3. Apply fee logic under the applicable rules. CONC 7.6 requires that charges not make it harder for a customer to repay. The Consumer Credit Directive (Article 27 in its UK retained form) constrains default charges to reasonable compensation for the lender's actual costs. Fee accrual should be computed from the event, not from a nightly batch that may run in a different time zone or miss a bank holiday.
  4. Route to the correct servicing path. Use the forbearance eligibility flag and arrears stage to select the next action: an automated payment reminder, an outbound agent call, a hardship assessment, or a formal arrears notice. Each routing decision is itself an event, so that if a complaint is later raised the firm can show exactly why a particular path was chosen at that moment. The Agent Operating Procedures pattern makes each of those decisions auditable by design.
  5. Report to credit reference agencies and regulators. Arrears data reported to a CRA must reflect the account state at the reporting date, not the current state. Event sourcing makes point-in-time reconstruction straightforward. A lender running across more than one jurisdiction can apply the correct reporting format from the relevant jurisdiction pack without maintaining separate pipelines.

What this gives a lender is a single, ordered, time-stamped record of every past-due event that a compliance officer, an auditor or an FCA supervisor can read without needing to reconcile three systems. It also means that a forbearance arrangement agreed on day fourteen can be unwound, extended or varied without corrupting the original arrears record.

Why a collections workflow tool is not enough on its own

Collections platforms are good at routing work: queues, call scheduling, promise-to-pay tracking. They are not designed to be the system of record for what happened to a loan account. When the collections tool holds arrears state that differs from the loan management system, neither is wrong in its own terms, but the discrepancy means that any report produced from either system is unreliable, and any complaint investigation requires manual reconciliation across both. That is the root cause of most past-due compliance failures, not bad intent, but two systems each believing they are the ledger.

Firms that have migrated a live credit book to an event-sourced ledger consistently find that the arrears reconciliation problem disappears, because there is only one place where past-due events are written. Kontor's ledger applies this pattern directly: a past-due event is appended once, and every downstream process, fee engine, servicing agent, CRA report, reads from the same immutable record. The collections layer becomes a consumer of ledger events, not a parallel source of truth.

Past-due credit management is, at its core, a data integrity problem: the moment a payment is missed, every system that touches that account must agree on what happened, when it happened, and what the rules were at the time, or the firm is building its compliance position on ground that can shift under an audit.

[ 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.