---
sourceDocument: Xanadu Financial Services Operations
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/financial-services-operations

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Financial Services Operations

ft:clusterId :

    - finso

bundleId :

    - finso

workflow :

    - Customer and Industry


---

# Failed standing order workflow

# Failed standing order workflow {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Learn how bank agents, using the Failed standing order workflow, proactively contact a
customer for a failed standing order for their deposit account and decide on an action plan. The
workflow applies to both business and personal deposit accounts.
The following diagram shows how the application helps bank agents handle a failed standing order for a deposit account.Figure 1. Failed standing order workflow example The deposit admin can review and customize this predefined flow based on the business needs of your organization.

The following workflow routes the case and tasks for a failed standing order to agents in
different departments. The agents log in to the Workspace to work on the
tasks in their queue. The case playbook guides agents through the steps that are needed to
fulfill the request.

As a deposit agent or via an API
:   If the system observes a failure in the execution of a standing order from a deposit
    account, an API in the backend triggers a Failed standing order deposit service case. A
    deposit agent can also create this case.

As back-office agents
:
    * A deposit agent works with the customer and finalizes the action plan.
    * In the case playbook, the deposit agent updates the failure reason, selects an appropriate corrective action in the Initiate and review stage, and submits the application for fulfillment.

    {#fso-failed-standing-order-workflow__ul_tzw_c2g_3sb}

    The workflow triggers next tasks or a case based on the selected corrective action
    and the assignment rules route the associated case or tasks to the appropriate
    back-office teams.

    Retry or waive a standing order occurrence
    :   If the corrective action based on the customer's request is to retry or waive
        off the standing order occurrence, the workflow automatically generates a deposit
        authorization task for the deposit agent.

        * A deposit authorizer (deposit agent) reviews the case details and approves the deposit task.
        * A deposit agent retries to execute the standing order for the deposit account in the core banking system and closes the retry deposit task in the playbook.  
          Note:  
          The Retry deposit task is generated only for the Retry corrective action.

        {#fso-failed-standing-order-workflow__ul_lwl_43w_3sb}

        The case is complete and the state and stage of the case are set to Closed
        Complete.

    Creating a corrective action service case
    :   If the corrective action is to modify or cancel the standing order, the workflow
        automatically creates one of the following child cases to resolve the case:

        * Modify standing order
        * Cancel standing order

        {#fso-failed-standing-order-workflow__ul_mwl_43w_3sb}

        The new child deposit case then handles this issue.

        After the child
        case is complete, the state and the stage of the parent case (failed standing
        order) are set to Closed Complete.