Public sector use case · SAP + ServiceNow + Microsoft 365
Procurement exception handling
Blocked invoices and procurement exceptions are emailed around. Corrections are made in SAP without a record of who decided. Procurement and invoice exceptions reach a named owner, and SAP changes happen only after approval.
Architecture
One governed run
How it starts: A scheduled SAP check finds exceptions. ServiceNow is a trigger source for the approved change leg.
Step by step
How the process runs
- 01
Detect
SAP procurement and invoice records are read on a schedule and checked by Rules + Code.
- 02
Ticket
Each exception opens a ServiceNow ticket for the responsible team.
- 03
Decide
Corrections are raised as a ServiceNow change and approved by the budget owner.
- 04
Correct
The approved SAP procurement or invoice operation runs.
- 05
Notify
The requester and team are informed by email and Teams.
Control
Human decision and exception path
Human decision
SAP corrections run only from an approved ServiceNow change.
Exception path
- SAP rejections keep the change open with the response.
- Unknown cost centres or suppliers route to the ERP owner.
- Operations outside pre-built actions use SAP RFC.
Evidence
What gets audited
- The exception and the rule that flagged it.
- The ticket and change record.
- Approver and decision.
- The SAP request and 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 deploymentRelated
Patterns, connectors and next steps
- SAP-ServiceNow integration
Integration pattern · ERP exceptions reach service operations, and approved changes reach SAP.
- SAP connector
97 pre-built actions
- ServiceNow connector
55 pre-built actions
- Microsoft 365 connector
45 pre-built actions
- Compliance evidence
Evidence produced by the work itself.
- Citizen request to case resolution
Another public sector 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 scheduled SAP check finds exceptions. ServiceNow is a trigger source for the approved change 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.