Lending Event Catalog

Governed lifecycle events for the Lending Operating System, used to synchronize decisions, servicing, recovery, and legal workflows across enterprise environments.

Shared event contracts reduce ambiguity across systems

Architecture, delivery, and operations teams move faster when lifecycle events are named consistently, published intentionally, and understood in the same way by every consuming system.

For architecture, operations, and transformation teams

This catalog is the reference view for how lifecycle change is emitted, consumed, and traced across the operating model. Use it to align implementation discussions, operational evidence, and downstream automation expectations.

Review the API platform

Lifecycle events referenced across the operating model

The catalog should answer three questions clearly: what changed, where it originated, and why downstream teams should care.

Event Domain Operational meaning
LoanApplicationCreated LOS Application intake has been registered and is available for downstream workflow and audit traceability.
UnderwritingCompleted LOS A governed credit decision has been completed and the outcome is ready for approval or next-step routing.
PaymentReceived LMS A borrower payment has been captured and can now feed allocation, reconciliation, and financial posting workflows.
DelinquencyDetected Collections Repayment behaviour has crossed a recovery threshold and strategy execution can begin under policy control.
LegalCaseOpened Litigation The case has moved into legal enforcement and should now be visible to litigation, evidence, and cost-tracking workflows.

What teams should review before publishing a new event

Event design is not only an integration concern. It affects operating evidence, implementation risk, and the stability of downstream workflows.

Operational meaning
Define the business state change clearly so servicing, recovery, finance, and legal teams interpret the signal the same way.
Consumer impact
List which systems, queues, alerts, and dashboards depend on the event so release planning and testing are grounded in real usage.
Governance evidence
Document versioning, replay implications, and audit expectations before the event becomes part of the operating baseline.