Progress a loan application

A Loan Application follows two controls before and during operational review: the record is first authorized through maker-checker, then permitted users work the product-defined Loan workflow one stage at a time.

Authorize the application record

A saved Draft has record status Captured. Submit it from the application form, then complete the required L3 → L2 → L1 authorization sequence. The levels actually used depend on the submitter's Create Loan Application permission configuration.

Each approver needs the matching Loan Application approval permission, sufficient authorization authority, and authorization scope over the application. Maker-checker separation prevents the maker from approving their own record.

When the final level approves the record, its record status becomes Authorized. This does not approve the loan; it enables the configured Loan workflow to continue. See Maker-checker authorization and Authorization levels.

If an approver selects Reject, the record returns for correction with record status Rejected and Application status Draft. Its Loan workflow remains at the same stage but cannot be operated until the corrected record is submitted and Authorized again. Deny remains the terminal maker-checker outcome.

Find the current work

Open Loans → Loan Applications, select the application, then use:

Overview for the borrower, requested terms, Group context, and requested Accounts;
Workflow for the current stage, requirements, assignments, reviews, history, and available transitions;
Decisioning for eligibility, pricing, and approved-term results;
Admin for record ownership, authorization, and audit metadata.

The detail header shows both Application and Record status. Confirm both before deciding what action is due.

Assign and accept the current stage

Stage work requires an accepted current-stage assignment. A user with Assign Loan Application can open Actions and:

select Self Assign when the current stage has no active assignment;
select Accept Assignment when an open assignment targets their user, role, department, or branch;
select Assign Stage to route an unassigned stage to one or more of those target types;
when handing over active work, select that assignment under Reassign From and choose the replacement target.

An assignment is not accepted automatically. Until an eligible user accepts it, requirement, review, decisioning, and stage-advance operations remain blocked. Leaving a stage completes its open assignments, so the next stage must be claimed or routed separately.

The assignee must also have Read Loan Application. An active assignment can place the application in the assignee's normal work scope, but it does not grant missing entity/action permissions or maker-checker authorization scope. When role, department, and branch targets are combined, the assignee must match all configured targets.

Complete stage requirements

Open the Workflow tab and review the current stage's requirements. A requirement's configured severity and verification mode determine what is needed:

capture requires Update Loan Application and an accepted assignment;
ordinary verification requires Process Workflow;
a waiver requires Waive Loan Application, an accepted assignment, and a reason;
a blocking requirement configured with no separate verification is satisfied once its evidence is captured;
other blocking requirements must be Verified or validly Waived before the stage can advance.

The capture dialog follows the requirement's configured data type, so the value may be text, a number, a date, a yes/no answer, or supporting evidence. The Workflow tab records who captured, verified, or waived the result.

Review the current stage

With an accepted assignment, open Actions → Review Stage. Ordinary decisions require Process Workflow; Waived requires Waive Loan Application and comments.

The available decisions are Approved, Rejected, Returned, and Waived. A review records the current-stage decision; it does not move the application by itself.

A stage with a Required review gate needs a current review before it can advance.
With Independent Actor Required, the same user cannot both record the review and advance the stage, except at platform scope.
After a non-waiver review, remoteEaze offers only transitions whose Review Outcome matches the latest decision.
Recording another review supersedes that reviewer's earlier current-stage decision.

Advance the stage

You need Process Workflow, an accepted assignment, no unresolved blocking requirements, and an Authorized outgoing transition.

Resolve every blocking requirement shown on Workflow.
Record the required stage review, if any.
Select Advance Stage. It appears as the primary action when the stage is ready, or under Actions where another primary operation takes precedence.
Select the Next Stage, review the transition and outcome, add optional comments, then confirm the advance.

Advancing records the stage history, completes current-stage assignments, and moves the workflow to the selected stage. A backward transition is allowed only when its configuration permits Return.

The actions configured on the destination stage can also change the Application status. For example, they can expose an offer, mark the application Approved for booking, or close it. The status change is therefore determined by the configured journey, not by the stage name alone.

Edit or amend the application

Update Loan Application allows eligible Captured or Rejected record details to be corrected directly. Editing an Authorized application creates a controlled amendment containing only supported application fields; the amendment must complete its own configured authorization path before the changes apply.

Closed applications cannot be amended from this page. Use the Loan Contract or Loan Variation journey for post-booking changes.

Continue with Eligibility, pricing, and approved terms.