Skip to content
NexusBook a demo

Financial services use case · Salesforce + ServiceNow + OpenAI + Snowflake

Commercial customer onboarding

Application details, ownership evidence and screening results are reviewed across separate systems without one record linking the assessment to account provisioning. Compliance receives a documented commercial onboarding case before approved provisioning reaches the core system and CRM.

Discuss this use case Financial services overview

Systems involved

What each system contributes

Salesforce

73 actions

  • Accounts10
  • Contacts10
  • Cases12

Trigger source: Salesforce (SOQL polling)

ServiceNow

55 actions

  • Tickets10
  • Users10

Trigger source: ServiceNow

OpenAI

25 actions

  • Chat Completions8
  • Files4
Snowflake

35 actions

  • Tables6
  • Views6

Core banking, lending, policy administration, claims, identity verification, KYC and sanctions screening have no pre-built Nexus connector. They are reached through the institution's approved APIs, database access or vendor interfaces, or as Rules + Code, inside the same workflow and with the same approvals and audit.

Architecture

One governed run

Trigger: Salesforce applicationInterface: identity, ownership and screeningRules + CodeAI step: model of your choiceHuman ApprovalInterface: core bankingAudit

How it starts: A commercial application in Salesforce is released for the institution's onboarding review.

Step by step

How the process runs

  1. 01

    Establish the application

    Read the Salesforce application context, check required business identifiers and open the linked ServiceNow review case.

  2. 02

    Gather verification results

    Call the institution's authorized identity-verification, beneficial-ownership and screening interfaces, retaining result references and the permitted Snowflake context.

  3. 03

    Apply risk-tier rules

    Evaluate the verified application against the institution's versioned risk-tiering and referral rules, recording the inputs and required decision authority.

  4. 04

    Review the business description

    The selected model, hosted inside the boundary where required, compares the submitted narrative with the stated activity and industry code and presents source-linked differences for the analyst.

  5. 05

    Obtain the compliance decision

    The named compliance analyst reviews the screening, ownership results, rule-based tier and model observations before deciding whether onboarding may proceed.

  6. 06

    Provision the approved scope

    A separate core-banking interface call performs the authorized provisioning, then the workflow updates the Salesforce record and ServiceNow case with the resulting references.

Control

Human decision and exception path

Human decision

The named compliance analyst approves onboarding within the institution's authority rules before any core-system provisioning occurs. Changes to material ownership, screening or activity information return the affected assessment for review.

Exception path

  • Incomplete ownership evidence or unavailable screening results hold the application in the review case.
  • A business-description discrepancy routes to the analyst with the relevant source passages rather than changing the risk tier through a model decision.
  • Partial or uncertain provisioning is reconciled against core-system references before another account-creation request.

Evidence

What gets audited

  • Application version, ownership evidence and screening-result references.
  • Risk-rule version, tiering inputs and model comparison.
  • Analyst decision, approved scope and timestamp.
  • Core-interface response and linked Salesforce and ServiceNow updates.

Nexus runs on premises, in private or sovereign cloud, or air-gapped. Credentials stay in the vault, roles decide who can approve, and the execution record stays inside your deployment boundary.

Sovereignty and deployment

Related

Patterns, connectors and next steps

FAQ

Questions about this use case

Does Nexus replace any of these systems?
No. Each system keeps its own records. Nexus runs the process between them and records each decision.
How does the run start?
A commercial application in Salesforce is released for the institution's onboarding review.
What if a step is not covered by a pre-built action?
Core banking, lending, policy administration, claims, identity verification, KYC and sanctions screening have no pre-built Nexus connector. They are reached through the institution's approved APIs, database access or vendor interfaces, or as Rules + Code, inside the same workflow and with the same approvals and audit.
Does the model decide whether to onboard the business?
No; it compares the business description with the submitted activity context, and the named compliance analyst makes the onboarding decision.

Use case review

Discuss this use case

Bring your version of the process. We will map the systems, approvals and evidence it needs.

Discuss this use case Book a demo