Lending
Loan origination, decisioning, booking, servicing, and variation journeys.
remoteEaze lending begins with a Loan Application and progresses through a product-defined workflow. That workflow can evaluate eligibility, generate pricing, approve final terms, prepare collateral, and book the approved application into a Loan Contract and Account.
This chapter covers the Dashboard journey under Loans. For offline field capture, see Workbench loan applications.
The lending journey
- Start a loan application and either save it as a Draft or submit it for record authorization.
- Assign, review, and progress the application through the stages configured for its Loan Product.
- Evaluate eligibility, generate pricing, and approve terms.
- Maintain collateral and guarantees when the configured journey requires them.
- Authorize and book the loan into a contract and customer Account.
- Continue with contracts, disbursement, and schedules, then use loan variations for controlled post-booking changes.
Complete Before originating the first loan before beginning an operational application.
Access is permission-based
Loan Application access depends on the user's permission, data-access scope, record state, current workflow stage, and accepted stage assignment.
| Permission | What it allows |
|---|---|
| Read Loan Application | Open the list and application details within scope. |
| Create Loan Application | Capture an application for an eligible borrower and Loan Product. |
| Update Loan Application | Edit an eligible application and capture current-stage requirements. |
| Delete Loan Application | Delete an eligible application. |
| Export Loan Application | Download the application PDF. |
| Assign Loan Application | Assign, self-assign, or accept current-stage work. |
| Process Workflow | Record ordinary decisions and run permitted workflow operations, including advancing a stage. |
| Waive Loan Application | Record a waiver where the configured control permits it; a reason is required. |
| Level 1, 2, or 3 Approver | Perform the corresponding maker-checker authorization step when the record requires it. |
Having a permission does not guarantee that its action is available. The record must also be in scope and in an eligible state, and runtime actions must be configured on the current stage. Stage work requires an accepted assignment.
For users below organization scope, a Loan Application can be in scope through its borrower, Group, selected member, or requested customer Accounts. The maker can also see a record they created or last changed. An active workflow assignment also places the application in an eligible assignee's normal work scope. Assignment never expands maker-checker authorization scope.
See Roles and permissions, Data-access scope, and Maker-checker authorization.
Three statuses describe different things
The detail header and Workflow tab expose separate layers of state:
| Layer | Meaning |
|---|---|
| Record status | The maker-checker state of the Loan Application record, such as Captured, Awaiting L3/L2/L1, or Authorized. |
| Application status | The lending outcome, such as Draft, In Review, Approved, Offered, Rejected, or Closed. |
| Workflow status and stage | Whether the product-defined workflow is active and which operational stage currently owns the work. |
An Authorized record is therefore not the same as an Approved loan. Authorization allows the operational workflow to proceed; the configured workflow actions and transitions determine the lending outcome.