Covenant Breach workflow

  • Release version: Washingtondc
  • Updated February 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 Covenant Breach Workflow

    The Covenant Breach workflow enables bank agents to proactively manage covenant breaches for both business and personal loans. This process helps identify potential loan default risks and facilitates the development of action plans with customers following a breach. Covenants are established at loan origination and require ongoing monitoring by the bank.

    Show full answer Show less

    Key Features

    • Covenant Definition: Covenants are promises made by borrowers to comply with specific conditions throughout the loan term, such as submitting financial statements or insurance receipts.
    • Workflow Initiation: A covenant breach triggers a credit service case via API or by a credit agent, which initiates the workflow.
    • Task Routing: The workflow automatically assigns tasks to various back-office teams based on defined assignment rules, ensuring efficient case management.
    • Document Verification: Document agents verify the necessary documents associated with the breach, with options to defer document requests if needed.
    • Credit Authorization: Credit agents review and approve the credit tasks associated with the case.
    • Case Closure: Once all tasks are completed, the case is marked as Closed Complete, and work notes are updated accordingly.

    Key Outcomes

    By utilizing the Covenant Breach workflow, bank agents can effectively manage covenant compliance, address breaches promptly, mitigate risks, and maintain clear communication with borrowers. This structured approach not only enhances operational efficiency but also supports better customer relationship management in the financial services sector.

    Learn how bank agents, using the Covenant Breach workflow, proactively contact a loan customer for a covenant breach and decide on an action plan for the future. The workflow applies to both business and personal loans.

    What are covenants

    A covenant is a promise by a borrower to a bank to abide by certain conditions through the life of the loan. Covenants are set up by the bank at the time of originating a loan. Monitoring covenants is an ongoing activity for the bank. A covenant helps a bank to identify and mitigate potential risks that are associated with a loan. When a covenant is breached, it is a signal of a potential default by the borrower.

    Examples of covenants for business loans could be:
    • Quarterly submissions of financial statements by the borrower
    • Monthly submissions of inventory and stock statement or unpaid invoices

    An example of a covenant for personal loans could be a periodic submission of home insurance premium receipts.

    The following diagram shows how the application helps bank agents work on a covenant breach for a loan.
    Figure 1. Covenant Breach workflow
    Workflow showing how a covenant breach is handled using the Loan Operations application. For the text description, refer to the workflow steps that follow.

    The following workflow routes the case and tasks for a covenant breach to agents in different departments. The agents log in to Workspace to work on the tasks in their queue.

    As a credit agent or via an API
    If a covenant breach is observed for a loan, an API in the backend triggers a Covenant Breach credit service case. A credit agent can also create this case.
    As back-office agents
    After the case is initiated and a credit 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 credit agent reviews the case details and adds additional details such as the covenant compliance status.

      The document processor service determines the documents that must be verified for the case. 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, this agent can request for a deferment of a specific document.

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

    3. A credit authorizer (credit agent) works on the credit task to review and approve it.

      The workflow generates a covenant update task for the credit agent.

    4. A credit agent works on this credit task and updates the covenant information in the banking system.

    After the case is complete, its state and the stage are set to Closed Complete and the work notes are updated.