Servicing is the second half of the story. This page walks the first half: where the money comes from, how a loan application becomes a funded loan, and how every record links together.
Training only. LOR (Loan Application Register) is used here as an organization-specific term and data structure, not a universal industry standard. LOC structure and accounting treatment also vary by lender, program, funding arrangement and servicing platform — confirm the model used in your environment.
Where is the lending/funding capacity coming from, and how much is left?
What loan is being requested, approved, certified and funded, and for whom?
What does the borrower now owe, and how is that obligation serviced?
What financial activity changed the balances, when, and with what effective date?
Select a stage to see what data is created and what money moves.
A new loan is approved on LOR-24587 for Jane Smith. Before you press the button: what happens when the $25,000.00 is funded?
Warehouse facility — sample funding entity
Loan Application Register record (internal term)
Forward: Borrower → Application/LOR → Loan → LOC → Disbursement → Servicing → Transaction. Reverse troubleshooting walks the same chain upward from the transaction. Click any record.
Organization-specific record. Authoritative for approved and certified amounts and for the link between application and servicing.
Operations proves what the borrower should owe. Finance proves the funding and the ledger agree. IT proves the data moved between systems. Product decides which control or interface has to change so it does not happen again. All four use the same chain — the first hop where the records disagree is where the problem started.