Skip to content
NexusBook a demo

Enterprise use case · SAP + Coupa + Xero + ServiceNow

Procure-to-pay exception workflow

Procure-to-pay spans several systems and exceptions fall between them. Invoice, procurement and payment exceptions are resolved with approval across four systems.

Discuss this use case Enterprise overview

Systems involved

What each system contributes

SAP

97 actions

  • Procurement17
  • Invoice10
  • Finance20
Coupa

2 actions

  • Invoices2
Xero

41 actions

  • Invoices13
  • Payments8
  • Bank Transactions10
ServiceNow

55 actions

  • Tickets10
  • Change Management10

Trigger source: ServiceNow

Coupa coverage here is its 2 pre-built invoice actions: create invoice and create invoice line. Reading approvals, suppliers or other Coupa data uses the Coupa API. SAP operations outside the listed groups use the SAP API or RFC.

Architecture

One governed run

Trigger: schedule / ServiceNowIntegration: Coupa + SAPRules + CodeHuman ApprovalSystem Action: XeroAudit

How it starts: A webhook, schedule or ServiceNow change starts the run.

Step by step

How the process runs

  1. 01

    Invoice

    Coupa invoice and invoice lines are created from validated data. These are the two pre-built Coupa actions.

  2. 02

    ERP validation

    SAP procurement, invoice and finance records are checked against the invoice.

  3. 03

    Accounting

    Xero invoices, payments and bank transactions are matched or recorded.

  4. 04

    Exceptions

    Mismatches open a ServiceNow ticket, or a change where a record must be corrected.

  5. 05

    Approval

    Finance approves the correction before any payment or ERP record changes.

Control

Human decision and exception path

Human decision

Corrections to procurement, invoice or payment records need finance approval and an approved ServiceNow change.

Exception path

  • Unmatched records open tickets.
  • Write failures are retried.
  • Duplicate payments are blocked.
  • Bank transactions without a matching invoice wait for review.

Evidence

What gets audited

  • Invoice data.
  • Checks.
  • Ticket and approval.
  • SAP, Coupa and Xero responses.

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 webhook, schedule or ServiceNow change starts the run.
What if a step is not covered by a pre-built action?
Coupa coverage here is its 2 pre-built invoice actions: create invoice and create invoice line. Reading approvals, suppliers or other Coupa data uses the Coupa API. SAP operations outside the listed groups use the SAP API or RFC.

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