{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":15579,"path":"financial-services-operations/dispute-management/dispute-management-workflows.md","title":"Overview of the Dispute Management workflow","bundle":null,"doc_type":null,"release":"australia","body":"\n# Overview of the Dispute Management workflow\n\nServiceNow® Dispute Management enables efficient card and non-card transaction dispute resolution, enhanced compliance, and streamlined customer experiences.\n\nWhen a dispute service case is initiated, the dispute transaction flow triggers. This flow includes various tasks specific to the case details.\n\nFor card or non-card dispute management cases, tasks are generated for each transaction that has a dispute request. The Dispute Workspace guides you through each task in the dispute. With input or decisions from each party, you as a dispute agent work through the Initiate, Review,Processing, and Closure stages of a dispute case.\n\n## Initiate\n\nWhen a dispute is initiated, the case begins in the Initiate stage.\n\nDispute cases can be initiated from the Dispute Workspace by contributors on behalf of the customer, by customers through the portal, or through virtual agent disputes with ServiceNow Otto for Financial Services Operations \\(FSO\\) with the Virtual Agent  skill. Dispute agents can also create cases when needed.\n\nDuring this phase, the system identifies the initial transaction. You’re then guided through the \"Select dispute reason\" activity, which involves a tiered questioning process \\(Level 1, Level 2, and optionally Level 3\\) to accurately determine the dispute category and its corresponding reason code.\n\nYou can then add more transactions \\(if the dispute category is Fraud\\),  and select associated transactions \\(if Visa network\\). You also complete the dispute questionnaire and upload any supporting documentation.  Dispute cases created using  disputes intake via Virtual Agent  are populated with information from the customer's responses in the Virtual Agent chat.\n\nWhen a transaction is selected for a card dispute, you can obtain additional information about the transaction with an integration, such as Order Insight Digital Management.\n\n**Note:** Additional integrations such as Ethoca Consumer Clarity are available to retrieve additional information on a transaction.\n\nThe system evaluates decision rules and determines policy rules for each transaction in the case. For example, determining which transaction qualifies for a provisional credit, as opposed to a final credit. However, if the dispute is initiated by a contributor or customer, the evaluation of decision rules occurs only after the Review task has been submitted. For more information on these rules, see [Dispute decision tables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/dispute-decision-tables.md).\n\nThe system generates tasks based on the policy rules that are evaluated when a case is submitted. For instance, when a case has a dispute category of Fraud, the system creates a task to block and reissue the card.\n\nChargeback eligibility rules depend on the dispute category \\(for card disputes\\). In cases of fraud, these rules are evaluated during the Investigate stage, specifically after the Fraud Report task is submitted. For non-fraud categories, the evaluation happens at the Submit action, whether from Initiate or Review. For ACH disputes, the eligibility for chargeback is evaluated during investigation and can be assisted by ServiceNow Otto agents.\n\nFor information about configuring business rules, see [Exploring decision tables](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/decision-designer-overview.md).\n\n## Review\n\nIf a dispute case was submitted by a customer via a service portal or a user with a contributor persona via Dispute Workspace, the case progresses to the Review stage. If the case was initiated by an agent, this stage is skipped.\n\nThe dispute agent reviews the dispute intake, including the disputed transactions, the dispute amount, and the reasons for the dispute.\n\nThe agent provides answers to any additional questions not answered by the customer as required. If the dispute category changes, the system produces a questionnaire for the newly selected category, which is then filled out by the agent. For ACH disputes, the agent then must review the previously attached and signed Written Statement of Unauthorized Debit \\(WSUD\\) document, which they can either verify or reject.\n\nAfter review, the agent submits the case and continues with the subsequent lanes and activities in the case.\n\nThe system generates tasks based on the policy rules that are evaluated when a case is submitted. For instance, when a case has a dispute category of Fraud, the system creates a task to block and reissue the card.\n\n**Note:** If the Dispute Rules Content Pack for Visa, Mastercard, or Nacha are installed, the system automatically provides both the dispute category and reason code. Without these content packs, only the dispute category is determined. For networks other than Visa, Mastercard, or ACH, customers must manually map their network-specific reason codes to the system's decision tables.\n\n## Processing\n\nAfter a card dispute case is submitted, an agent can monitor and progress the disputed transactions in the Processing stage. This stage presents an overview of the overall case and tracks the status of each transaction and its related tasks.\n\nEach disputed transaction in the case is displayed in this view as a separate card. Each card contains the following information:\n\n-   Card disputes transaction number\n-   Stage of processing \\(Investigate, Chargeback, or Complete\\)\n-   Card present or card not present indicator\n-   Dispute amount\n-   Transaction date\n-   Merchant type\n-   Transaction state\n-   Current activity\n-   Activity service level agreement \\(SLA\\)\n\n## Investigate\n\nThis stage applies for each disputed transaction in a case. You can access this stage by opening a disputed transaction in the Processing stage of the playbook.\n\nEach transaction is opened in the **Dispute Workspace**, represented as a process-based layout. This layout visually represents the distinct stages of the investigation workflow for that specific transaction: Investigate, Chargeback, and Closure.\n\nDuring this stage, the card network, card issuing bank, merchant bank or acquirer, and merchant engage in review processes to make final determinations for each transaction. In this stage, the merchant gets alerted of a card dispute transaction. If a merchant declines a disputed transaction, then a task to [Investigate transactions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/dispute-management/manually-investigate-disputed-transaction.md) is created.\n\n**Note:** Issuer banks don’t contact merchants directly about disputed transactions. However, merchants enrolled in Ethoca Alerts or Verifi CDRN receive notifications of potential disputes, enabling them to work with cardholders to resolve issues and help prevent chargebacks.\n\nIn this stage, agents can also work on transactions identified as friendly fraud. For more information, see [Resolve friendly fraud disputes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/dispute-management/resolve-friendly-fraud.md).\n\n## Chargeback\n\nThis stage applies for each disputed transaction in a case. You can access this stage by opening a disputed transaction in the Processing stage of the playbook.\n\nDuring the chargeback stage, the agent submits the card dispute and the chargeback workflow begins between the involved parties. For non-card disputes, the agent files the ACH return.\n\nFor card fraud disputes, the block card or reissue card flows run in parallel with the rest of the dispute management flow for the disputed transactions.\n\nChargeback workflows differ between card and non-card disputes, as well as between card networks. See [Managing Disputes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/dispute-management/managing-disputes.md) for more information.\n\n## Closure\n\nAfter a case is processed according to the final determinations for all dispute transactions associated with the case, the case progresses to Closure.\n\nIf there are more than one disputed transactions associated with a case, the case remains open until the workflows for each transaction are completed and closed.\n\nIf the evaluated policy rules deny the transaction, it moves directly to Closure.\n\nAgents can enter the Resolution code and any Resolution notes before the case is moved to Closed Complete state.\n\n**Parent Topic:**[Managing dispute service requests](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/dispute-management/managing-card-disputes.md)\n\n**Related topics**  \n\n\n[Card Disputes data model](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/dispute-data-model.md)\n\n[Set up Dispute Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/dispute-management/setting-up-disputes-management.md)\n\n[About dispute intake](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/dispute-management/dispute-intake-overview.md)\n\n[Review a dispute from portal or workspace intake](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/dispute-management/review-a-dispute-from-cardholder-intake.md)\n\n[Managing Disputes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/financial-services-operations/dispute-management/managing-disputes.md)\n\n"}}