Components installed with Financial Services Payment Operations

  • 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 Components Installed with Financial Services Payment Operations

    The Financial Services Payment Operations application installs various components essential for managing payment operations, including tables, user roles, plugins, and store applications. It is crucial for ServiceNow customers to understand these components to optimize their use of the application.

    Show full answer Show less

    Key Features

    • Plugins Installed: The application includes the Customer Service plugin, which allows for the extension of tables from the Customer Service Management application into Financial Services Operations applications.
    • Store Applications: The Financial Services Operations Core store application is installed, which is responsible for managing customer data needed for payment requests.
    • Roles Installed: A variety of roles are provided, including:
      • Payment Admin: System administrator role for managing payment operations.
      • Claim Agent: Role for managing claim cases and tasks.
      • Payment Contributor: Role for submitting payment inquiries and claims.
      • Inquiry Agent: Role for managing payment inquiry cases.
    • Tables Installed: Key tables include:
      • Payment Base: Extends tables for claims and payment inquiries.
      • Claim: Stores all payment claim cases.
      • Payment Inquiry Case: Stores all payment inquiry cases.

    Key Outcomes

    By understanding the components installed with Financial Services Payment Operations, ServiceNow customers can effectively manage payment operations, streamline processes, and ensure proper access control through defined roles. This setup enhances operational efficiency and supports better customer service through optimized case management.

    Several types of components are installed with the installation of the Financial Services Payment Operations application, including tables and user roles. The application also installs related plugins and store applications if they are not already installed.

    Note:
    The Application Files table lists the components that are installed with this application. For instructions on how to access this table, see Find components installed with an application.

    Demo data is available for this application.

    Plugins installed

    Table 1. Plugins installed with Financial Services Payment Operations
    Plugin Description
    Customer Service

    [com.sn_customerservice]

    		 Enables the extension of tables from the Customer Service Management application into the Financial Services Operations applications.

    Store applications installed

    Table 2. Store applications installed with Financial Services Payment Operations
    Store application Description
    Financial Services Operations Core Stores the customer data that is needed to make payment requests. For more information, see 110319b85caaf2e37e14ae65d0bf1e3cf4530756.dita.

    Roles installed

    Table 3. Roles installed with Financial Services Payment Operations
    Role title [name] Description Contains roles

    Payment admin [sn_bom_payment.admin]

    		 Application-specific system administrator role that can:
    • Grant payment operations roles
    • Delete payment cases and tasks
    Note:
    The sn_bom.admin role contains the sn_bom_payment.admin role when the Financial Services Payment Operations application is installed.
    • sn_bom_payment.inquiry_agent
    • sn_bom_payment.inquiry_viewer
    • sn_bom_payment.claim_agent
    • sn_bom_payment.claim_viewer
    Claim agent

    [sn_bom_payment.claim_agent]
    • View the overall status of claim cases
    • Create claim cases
    • Work on claim cases, debit approvals, and claim tasks
    • Record interactions
    • sn_bom.account_viewer
    • sn_bom.ref_data_viewer
    • sn_bom_payment.inquiry_viewer
    • sn_esm_agent
    • sn_bom_payment.claim_viewer
    Payment contributor

    [sn_bom_payment.contributor]
    • Submit payment inquiry requests
    • Submit payment claim requests for internal claims
    • View the status of payment inquiry and claim cases
    Important:
    For the contributor role to work, it must be combined with one of the CSM Contributor users roles. For more information, see Roles and Personas.
    • sn_sla_definition_read
    • sn_bom.b2c_contributor
    • sn_bom.account_data_viewer
    • sn_bom_payment.inquiry_viewer
    • sn_customerservice.csm_workspace_user
    • sn_bom.b2b_contributor
    • sn_bom.deposit_account_viewer
    • sn_bom_payment.claim_viewer
    Claim agent connector

    [sn_bom_payment.claim_agent_connector]
    • Create claim cases
    • Work on claim cases, debit approvals, and claim tasks for accounts managed by them
    Important:
    For the agent connector role to work, it must be combined with one of the CSM industry data model roles. For more information, see Roles and Personas.
    • sn_bom.ref_data_viewer
    • sn_sla_definition_read
    • sn_bom.viewer
    • sn_bom.account_data_viewer
    • sn_bom.agent
    • sn_bom_payment.inquiry_viewer
    • sn_bom.deposit_account_viewer
    • sn_bom_payment.claim_viewer
    Inquiry agent connector

    [sn_bom_payment.inquiry_agent_connector]
    • Create inquiry cases
    • Work on payment inquiry cases and inquiry tasks for accounts managed by them
    Important:
    For the agent connector role to work, it must be combined with one of the CSM industry data model roles. For more information, see Roles and Personas.
    • sn_bom.ref_data_viewer
    • sn_sla_definition_read
    • sn_bom.viewer
    • sn_bom.account_data_viewer
    • sn_bom.agent
    • sn_bom_payment.inquiry_viewer
    • sn_bom.deposit_account_viewer
    • sn_bom_payment.claim_viewer
    Claim viewer

    [sn_bom_payment.claim_viewer]

    		 View claim cases and related data
    • sn_bom.account_viewer
    • sn_bom.ref_data_viewer
    • sn_bom.customer_data_viewer
    Inquiry agent

    [sn_bom_payment.inquiry_agent]
    • View the overall status of payment inquiry cases
    • Work on payment inquiry cases and inquiry tasks
    • Record interactions
    • sn_bom.account_viewer
    • sn_bom.ref_data_viewer
    • sn_bom_payment.inquiry_viewer
    • sn_esm_agent
    • sn_bom_payment.claim_viewer
    Inquiry viewer

    [sn_bom_payment.inquiry_viewer]

    		 View inquiry cases and related data
    • sn_bom.account_viewer
    • sn_bom.ref_data_viewer
    • sn_bom.customer_data_viewer
    Payment manager

    [sn_bom_payment.manager]
    • View the Payment Operations dashboard
    • Use Process Mining for Payment Operations processes
    • sn_bom_payment.inquiry_agent
    • pa_viewer
    • sn_bom_payment.claim_agent

    Tables installed

    Table 4. Tables installed with Financial Services Payment Operations
    Table Description
    Payment Base

    [sn_bom_payment_base]

    		 Claim, Payment Inquiry Case, and Payment Service tables extend the Payment Base table.
    Claim

    [sn_bom_payment_claim]

    		 Stores all payment claim cases.
    Claim Task

    [sn_bom_payment_claim_task]

    		 Stores all claims tasks.
    Debit Instruction

    [sn_bom_payment_debit_instruction]

    		 Stores all debit instructions for all refunds.
    Payment Inquiry Case

    [sn_bom_payment_inquiry]

    		 Stores all payment inquiry cases.
    Inquiry Task

    [sn_bom_payment_inquiry_task]

    		 Stores all payment inquiry tasks.
    Receiving Transaction

    [sn_bom_payment_m2m_receiving_transaction]

    		 Stores all financial transactions that the receiving customers and accounts received.
    Sender Transaction

    [sn_bom_payment_m2m_sender_transaction]

    		 Stores all financial transactions (deposit) that sender customers sent.
    Payment Service

    [sn_bom_payment_service]

    		 Stores all payment service cases for debit approvals.