Financial services use case · SAP Concur + SAP + Microsoft 365
Expense and budget governance
Budget adjustments are agreed informally and SAP finance records are updated later, if at all. Budget changes are checked against policy, approved and followed up in SAP with notification.
Systems involved
What each system contributes
15 actions
- Budget4
- Budget Item4
- Budget Category5
- Budget Adjustments1
97 actions
- Finance20
- Procurement17
SAP Concur actions cover budgets and adjustments. Expense report data outside those groups uses the Concur API.
Architecture
One governed run
How it starts: A schedule, webhook or Teams request starts the run.
Step by step
How the process runs
- 01
Budget context
SAP Concur budget, budget item and budget category are read.
- 02
Policy check
Rules + Code compares the request with thresholds and remaining budget.
- 03
Approval
The budget owner approves in Teams or email.
- 04
Apply
SAP Concur budget adjustments are recorded and SAP finance or procurement follow-up runs.
- 05
Notify
Requester and finance are told the outcome.
Control
Human decision and exception path
Human decision
The budget owner approves every adjustment. Larger amounts need a second approver.
Exception path
- Requests over budget are rejected with a reason.
- SAP write failures are retried.
- Expired approvals are re-requested.
Evidence
What gets audited
- Request.
- Policy result.
- Approvals.
- Concur and SAP 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 deploymentRelated
Patterns, connectors and next steps
- Salesforce-SAP integration
Integration pattern · Commercial commitments reach ERP fulfilment and finance without re-keying.
- SAP Concur connector
15 pre-built actions
- SAP connector
97 pre-built actions
- Microsoft 365 connector
45 pre-built actions
- Human-in-the-loop
Where approval belongs in a running workflow.
- Lead to account and ERP handoff
Another financial services 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 schedule, webhook or Teams request starts the run.
- What if a step is not covered by a pre-built action?
- SAP Concur actions cover budgets and adjustments. Expense report data outside those groups uses the Concur API.
Use case review
Discuss this use case
Bring your version of the process. We will map the systems, approvals and evidence it needs.