---
title: Financial Services Payment Operations workflow example
description: The workflows available with Financial Services Payment Operations connect people, departments, and institutions to quickly initiate, research, and resolve the payment errors and missing payments.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/financial-services-operations/financial-services-payment-operations/payment-ops-workflow-example.html
release: australia
product: Financial Services Payment Operations
classification: financial-services-payment-operations
topic_type: concept
last_updated: "2026-03-12"
reading_time_minutes: 1
breadcrumb: [Use, Payment Operations, Banking applications, Financial Services Operations \(FSO\)]
---

# Financial Services Payment Operations workflow example

The workflows available with Financial Services Payment Operations connect people, departments, and institutions to quickly initiate, research, and resolve the payment errors and missing payments.

The following workflow example shows how the application facilitates payment inquiries, research, and claims resolution, as well as communications with other financial institutions for external payments.

<table id="table_s5m_w22_tnb"><tbody><tr><td>

-   **1. Initiate a case**

A customer can report a payment error or missing payment by logging into their account or via email, phone, or chat to initiate a case. This case provides a digitized, single system of engagement for all contacts \(mobile, web, and phone\), tasks, and actions taken, from issue initiation to resolution.

-   **2. Intake and assign**

Once the case is initiated, a workflow is triggered automatically or by an agent that validates the information about the transaction and the customer. The workflow routes the inquiry to the appropriate middle and back office payment teams.

-   **3. Investigate**

An inquiry agent can review customer details or payment details within the system of engagement without needing to research across systems. The agent can take action if the claim is eligible for reversal. A claim agent can manage all interactions with the payment recipient and external financial institutions. Tasks and status are tracked in the case. Notifications are sent automatically to recover funds and take corrective action.

-   **4. Resolve**

A communication to the customer lets them know that the issue is resolved, and prompts a satisfaction survey.

-   **5. Provide audit trail**

All the data and timelines are captured in the case, eliminating the need to manually pull that information when needed for reports or audits to support compliance requirements.


</td><td>

\[Omitted image "payment-ops-workflow-example.png"\] Alt text: Infographic showing how the application facilitates payment inquiries, research, claims resolution, and communications with other financial institutions for external payments.

</td></tr></tbody>
</table>For more information on each task in the workflow, see:

-   [Managing payment inquiries](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/financial-services-payment-operations/managing-payment-inquiries.md)
-   [Managing payment claims and debit approvals](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/financial-services-payment-operations/managing-payment-claims.md)