Lending & AI Glossary
Definitions with architecture context.
Open Glossary →Articles, practices, comparisons and definitions connecting Lending, Banking Technology and Enterprise AI to real implementation questions.

Use the Glossary, Comparisons and Knowledge Map to connect related topics.
Insights is designed for people, search engines and AI search with direct answers, clear structure and useful internal links.
A practical explanation of how a Loan Origination System (LOS) differs from a Loan Management System (LMS) and where they connect.
Read article →Understand how an LMS manages loan accounts, schedules, interest, fees, payments and lifecycle events after approval.
Read article →A practical capability map from product design, LOS and LMS to collateral, collections, litigation, integration and reporting.
Read article →From delinquency events to strategy, work queues, customer contact, payment, restructuring and legal escalation.
Read article →Private AI explained for enterprise use: customer-controlled environment, shared AI services, private model runtime, governance and operations.
Read article →A progressive governance approach starting with use case ownership, risk, data boundary, identity, registry, evaluation, approval and audit.
Read article →A delivery model for turning financial-services problems into AI use cases from discovery and prototype to evaluation, integration and production.
Read article →Document AI should go beyond text recognition to classification, extraction, cross-document checks, confidence handling and human review.
Read article →Payment allocation defines how an incoming payment is applied to fees, interest, principal or other components. The order must reflect product rules, institutional policy and accounting treatment.
Read article →An interest engine should separate formula, day-count, rate source, rounding, calendars and calculation-triggering events from workflow so calculations remain auditable and reusable across products.
Read article →Lending-to-core integration should begin by defining system-of-record and ownership for customer, account, transaction, balance and accounting events before choosing APIs, events, batch or files.
Read article →In lending, an operational ledger records account-level events and balances, while the General Ledger is the enterprise accounting book receiving postings under the chart of accounts and accounting rules.
Read article →RAG should start with governed source content, access rights, metadata and target questions before choosing a vector database or embedding model. Citation, access filtering and evaluation are essential.
Read article →An AI Gateway sits between applications and model services to manage authentication, policy, routing, logging, quotas and model changes without binding applications to a single endpoint.
Read article →AI evaluation should reflect the real task and risk, measuring answer quality, coverage, error types, latency, review effort and failure scenarios rather than relying on one benchmark for every use case.
Read article →The key difference is not only where the model runs, but also data boundaries, identity and policy controls, model approval, audit, operating ownership and integration with enterprise systems.
Read article →