Loan Operations workflows

  • Release version: Yokohama
  • Updated January 30, 2025
  • 1 minute to read
  • The Financial Services Loan Operations application installs automated workflows for loan servicing. These workflows enable routing of cases and tasks to different departments, including the loan, document, and credit agents.

    Workflows available with the application

    The following predefined workflows for business and personal loans are available with the application:
    Personal loans Business loans
    Partial Prepayment Partial Prepayment
    Loan Forgiveness Loan Forgiveness
    Loan Deferment Loan Deferment
    Loan Write-Off Loan Write-Off
    Missed Repayment Missed Repayment
    Covenant Breach Covenant Breach
    Note:
    This workflow is initiated from the Financial Services Credit Operations application.
    Loan Restructuring Loan Restructuring
    Note:
    This workflow is initiated from the Financial Services Credit Operations application. From there, a loan case is automatically created to take the request to completion.
    Loan Drawdown
    Loan Rollover

    These workflows are built using Flow Designer. The loan admin can review and customize these predefined flows that are based on the business needs of an organization.

    General workflow for Loan Operations

    When a customer requests a loan service, a loan service case is created and assigned to a loan agent. After the agent updates the case details, a workflow is triggered. The flow triggers various tasks from the case and the assignment rules route these tasks to the appropriate back-office teams such as loan, credit, or document service. A new task is automatically created when an agent closes the previous task.

    The following is a typical loan workflow in the Financial Services Loan Operations application.
    Note:
    Depending on the request type, individual workflows might have additional or fewer tasks.
    1. A loan contributor, requester, or a customer submits a loan service request.
    2. The loan contributor collects the required customer documents and updates the case.
    3. A loan agent receives the case and adds additional information, such as the fee.
    4. The document processor service determines the documents that are required. If any documents must be verified, a task is generated for the document agent.
    5. A credit task is generated for the credit agent.
    6. An authorization task is generated to review and approve the loan request.
    7. After the authorization, a loan update task is generated. If the bank has enabled an integration, the loan account could get automatically updated in the core system.