Does Nexus replace any of these systems?

No. Each system keeps its own records. Nexus runs the process between them and records each decision.

Why use a model if matching rules already exist?

Rules perform the numerical comparison; the model interprets messy descriptions and exception context to propose how a person might resolve the remaining difference.

Does an accepted explanation authorize a payment?

No; payment release remains a separate finance-controlled action unless explicitly included and approved in the workflow.

Enterprise use case · SAP + Coupa + OpenAI

Three-way match with proposed resolutions

Clean invoices move through matching rules, but disputed quantities and receipt differences still require manual investigation. Accounts payable receives explained invoice, order and receipt discrepancies with a reviewable next action.

Discuss this use case Enterprise overview

Systems involved

What each system contributes

SAP

97 actions

Procurement17
Invoice10
Finance20

Coupa

2 actions

Invoices2

OpenAI

25 actions

Chat Completions8

The model step runs against the AI provider you choose, including Anthropic, Google Gemini or a model you host yourself. Anything outside a pre-built action 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.

Architecture

One governed run

Trigger: schedule / webhookIntegration: Coupa + SAPRules + CodeAI step: model of your choiceHuman ApprovalSystem Action: SAPAudit

How it starts: A Coupa invoice is approved for matching or a previously held invoice is ready for another review.

Step by step

How the process runs

01
Assemble the documents
Read the Coupa invoice and the corresponding SAP purchase-order and receipt context.
02
Settle exact comparisons
Deterministic checks identify clean matches and isolate differences using the configured quantity, amount and timing rules.
03
Interpret the discrepancy
The selected model compares the unresolved lines and available notes, explaining what differs and proposing an evidence-backed resolution.
04
Test the suggestion
Rules verify the proposal against source values and allowed actions, keeping missing receipts or unsupported explanations explicit.
05
Apply the reviewed action
After finance approval, the workflow performs the permitted SAP action or returns the invoice for correction.

Control

Human decision and exception path

Human decision

The named accounts-payable or procurement owner approves any proposed adjustment, tolerance override or posting release. The model cannot change the invoice, manufacture receipt evidence or authorize payment.

Exception path

Missing orders or receipts hold the match instead of treating absent evidence as acceptance.
A proposal that contradicts document values is rejected and sent for manual investigation.
Changes to invoice lines or receipts invalidate the previous comparison and trigger revalidation.

Evidence

What gets audited

Invoice, purchase-order and receipt references with compared values.
Matching-rule version and unresolved differences.
Model proposal, supporting references and reviewer decision.
Approved destination action and its response.

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

Coupa-SAP integration
Integration pattern · Approved invoice data reaches SAP with matching, posting controls and status visibility.
SAP connector
97 pre-built actions
Coupa connector
2 pre-built actions
OpenAI connector
25 pre-built actions
Enterprise automation
Governed processes across the systems you already run.
Order to cash across CRM, ERP and billing
Another enterprise use case.

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 Coupa invoice is approved for matching or a previously held invoice is ready for another review.
What if a step is not covered by a pre-built action?: The model step runs against the AI provider you choose, including Anthropic, Google Gemini or a model you host yourself. Anything outside a pre-built action 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.
Why use a model if matching rules already exist?: Rules perform the numerical comparison; the model interprets messy descriptions and exception context to propose how a person might resolve the remaining difference.
Does an accepted explanation authorize a payment?: No; payment release remains a separate finance-controlled action unless explicitly included and approved in the workflow.

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