1. Loan Management System
  2. Features
  3. Application intake
Feature · Application intake

Application intake

Prepare an owned loan request with principal, borrower and supporting records.

OverviewMy applications
Loan Management System · Application intake

My applications

Loan applications

New
Record numberSubjectStatusRequested principal USDCounterpartyRevision
LA-55305Draft la-947Draft830BRR-3871600
LA-23427Under review la-921Under review860BRR-1766700
LA-19788Approved la-192Approved110BRR-2228220
LA-82961Submitted la-622Submitted900BRR-8224630
LA-68342Pending la-105Pending920BRR-3030100
6 of 6 records
Draft la-947Loan applications · LA-55305
Draft
Requested principal USD830
CounterpartyBRR-3871
Revision600
Example screen with sample data

What you can do

Prepare the request

A Credit Officer opens a loan application for a particular organization and borrower. The record number identifies the case, while the subject describes the request. Requested principal and submission date place the financial request in time. The owner points to the team member responsible for preparation. The application revision matters because the Independent Credit Approver’s later decision is tied to the version actually reviewed. If the officer changes the case after submission, the earlier decision must remain attributable to its original revision.

Supporting material stays on the case. Record attachments have a title, file, upload time, visibility and evidence type, with an uploader linked to a team member. Application evidence can identify a statement, confirmation, settlement or correction, along with provider event ID, received time, amount and verification value. These are distinct records: an attachment is a document the team can inspect; an application evidence row describes a source event or supporting assertion. Use both links to make a decision traceable without treating an uploaded file as proof of a provider effect.

How the work is organized

  • Case ownership. Each request has one team member responsible for preparing and following it.
  • Supporting trail. Attachments and application evidence stay connected to the parent case.
  • Revision control. The submitted revision identifies precisely what the reviewer considered.

What to agree during setup

Decide how record numbers are assigned and what a useful subject contains. Agree which documents are shared and which remain internal. The visibility setting should be checked on an actual case with people in different roles, since a copied link must still respect case access. Decide who checks evidence verification and what source event IDs must be retained. Align organization and borrower ownership before Credit Officers begin preparing requests.

For the first cycle, use a request with a principal amount, borrower, officer and one supporting attachment. Add a statement evidence row with its received date. Submit the case for review and ask the Independent Credit Approver to find the exact materials associated with that revision. Repeat after changing the application so the prior decision is not mistaken for a new decision. The officer should be able to locate returned cases and add the requested material without overwriting the review record.

Check the handoff on an actual case

A borrower submits a request for a stated principal. The Credit Officer records the amount and subject, adds an internal attachment, and associates a statement with the case. Before review, the officer checks that the borrower belongs to the selected organization and that the attachment is visible to the intended reviewer. The officer submits the current revision. If the reviewer returns the case for a corrected document, the officer updates the application and submits the new revision. The decision trail shows both what was considered and why the work came back.

The Operations Overview helps the team begin the day with recorded exceptions. The application views keep ordinary intake work close to its next decision. Credit Officer ownership remains visible even after the status changes, so a provider confirmation or repayment question can be routed back to a real person.

What your team sees

  • My applications — Requests assigned to the signed-in officer, with current status and principal.
  • Applications in review — Applications awaiting a credit decision on the submitted revision.
  • Application status board — Cases grouped by their current application status.

Follow the work through

See application review and credit decisions to follow the case into approval.

What it keeps track of

Data model
Loan applications
Loan applications moving through underwriting, approval, disbursement and repayment.
Record attachments
Supporting documents attached to a loan application.
Application evidence
Statements, confirmations, settlement notices and corrections supporting a loan application.
Borrowers
Borrowers eligible for loan applications.
Team members
Preparers, approvers, auditors and administrators working in the organization.

Who uses it

Permissions
Credit Officer
Prepares the application and supporting records.
Independent Credit Approver
Reads the submitted revision and evidence.
Auditor
Examines authorized case history.
App Administrator
Maintains the organization and membership context.

Set up Loan Management System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started