Loan Deferment workflow

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Loan Deferment Workflow

    The Loan Deferment workflow allows bank agents to manage loan service requests for temporarily postponing scheduled loan repayments, applicable to both business and personal loans. During the deferment period, customers may not be required to make payments, and banks might waive interest, although forbearance is also an option where interest is accrued but paid later.

    Show full answer Show less

    Key Features

    • Service Request Submission: Loan deferment requests can be submitted by loan contributors or customers directly through various portals, including the Customer Service Portal, provided the necessary plugins are activated.
    • Automated Workflow: Upon case initiation, an automated workflow triggers, routing tasks to the appropriate back-office teams based on assignment rules.
    • Document Verification: A document processor service identifies required documents, creating a verification task for document agents.
    • Credit Assessment: A credit agent reviews customer credit and approves the deferment request.
    • Loan Authorization: A loan authorizer reviews and approves the case before updating the loan account, potentially integrating with core banking systems for automatic updates.

    Key Outcomes

    Once the process is complete, the case is marked as Closed Complete, and work notes are updated. Customers can track the status of their deferment request via the Customer or Consumer Service Portal or other self-service portals, ensuring transparency and effective communication throughout the workflow. This streamlined process enhances customer service efficiency and satisfaction.

    Learn how bank agents, using the Loan Deferment workflow, resolve a loan service request for a temporary postponement of a scheduled loan repayment. The workflow applies to both business and personal loan service requests.

    With loan deferment, the customer is not expected to pay any amount for an agreed duration. In addition, the bank may consider waiving the interest during the deferment period.

    Forbearance is also a temporary postponement of scheduled loan repayments where the customer is not expected to pay any amount for an agreed duration. In this case, the bank accrues the interest on the outstanding amount and collects it when the regular repayments start on the loan.

    Note:
    Banks use Deferment and Forbearance interchangeably on a case-to-case basis.
    The following diagram shows how the application helps bank agents resolve a Loan Deferment service request.
    Figure 1. Loan Deferment workflow
    Workflow that shows how a loan service request for deferment is resolved using the Loan Operations application.

    The following workflow routes the case and tasks for a Loan Deferment service request to agents in different departments. The agents log in to Workspace to work on the tasks in their queue. For Loan Deferment workflow for personal loan operations, agents can also use the case playbook that guides them through the steps that are needed to resolve the case.

    As a loan contributor, requester, or customer
    A loan contributor or a requester submits a Loan Deferment loan service request on behalf of a customer.
    A customer (consumer or contact) can directly submit a request from the Customer Service Portal, Consumer Service Portal, or another self-service portal.
    Note:
    For consumers to submit a request using the Consumer Service Portal, you must have the Consumer Service Portal plugin (com.glide.service-portal.consumer-portal) activated.

    A case is initiated based on the request type.

    As back-office agents
    After the case is initiated and an agent updates the case details, a workflow is triggered automatically. The assignment rules route the associated tasks to the appropriate back-office teams.
    1. A loan agent reviews the case details and adds additional details, such as the fee.

      The document processor service determines the documents that must be verified for the request. The workflow generates an inbound document verification task for the document agent.

    2. A document agent works on the inbound document verification task to verify each document that is listed in the task. If required, they can request a deferment of a specific document.

      The workflow generates a credit assessment task for the credit agent.

    3. A credit agent works on the credit task to review the credit for the customer and approve the request.

      The workflow generates a loan authorization task for the loan agent.

    4. A loan authorizer (loan agent) reviews the case details and approves it.
    5. A loan agent works on the loan update task and updates the loan account in the banking system.

      If the bank has enabled an integration, the loan account could also get automatically updated in the core system.

    After the case is complete, its state and the stage are set to Closed Complete and the work notes are updated. A customer can view the status of the case from the Customer or Consumer Service Portal or another self-service portal.