Skip to content
NexusBook a demo

Enterprise use case · Salesforce + SAP + Stripe

Order to cash across CRM, ERP and billing

Deals are retyped into ERP, billing is set up separately and status never returns to sales. Won deals become orders and invoices without re-keying, with exceptions reviewed.

Systems involved

What each system contributes

Salesforce

73 actions

  • Opportunities10
  • CPQ Quote8

Trigger source: Salesforce (SOQL polling)

SAP

97 actions

  • Sales Orders14
  • Finance20
  • Invoice10
Stripe

43 actions

  • Billing19

Trigger source: Stripe

Architecture

One governed run

Trigger: Salesforce SOQL pollIntegration: Salesforce + SAPRules + CodeHuman ApprovalSystem Action: StripeAudit

How it starts: Salesforce SOQL polling starts the order leg. Stripe events start the billing leg.

Variant: Xero invoices and payments can replace Stripe and SAP finance for smaller entities.

Step by step

How the process runs

  1. 01

    Deal

    Closed opportunities and CPQ quotes are read.

  2. 02

    Order

    SAP sales orders are created.

  3. 03

    Invoice

    SAP invoice and finance records are updated.

  4. 04

    Billing

    Stripe billing is set up for subscriptions.

  5. 05

    Status

    Results return to the Salesforce opportunity.

Control

Human decision and exception path

Human decision

Orders outside pricing policy wait for a commercial or finance owner.

Exception path

  • SAP rejections return to Salesforce.
  • Billing failures open a finance task.
  • Duplicates are blocked.

Evidence

What gets audited

  • Deal data.
  • Approvals.
  • SAP and Stripe references.

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?
Salesforce SOQL polling starts the order leg. Stripe events start the billing leg.
What if a step is not covered by a pre-built action?
It runs through an API, protocol or database call, or as Rules + Code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the same approvals and audit.

Use case review

Discuss this use case

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