ERP & Finance · 15 pre-built actions
SAP Concur integration with Nexus
Govern SAP Concur budget changes end to end. Budget, category, item, tracking field and adjustment actions let budget changes run with approval and a complete record.
Pre-built actions
What you can automate
15 pre-built SAP Concur actions, grouped by what they work on.
15
PRE-BUILT ACTIONS
- 01Budget and Budget Item actions create and update budgets.
- 02Budget Category and Budget Tracking Field actions organise how spend is tracked.
- 03Budget Adjustments actions record approved changes.
Workflow
How it fits into a Nexus workflow
SAP Concur steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the SAP Concur API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Approved budget adjustment
A budget change request pauses for the budget owner, then the adjustment is applied in Concur.
Budget setup from planning
Approved plans create budgets and items in Concur with consistent categories.
ERP alignment
Budget data is checked against SAP finance records and differences go to review.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Industry use cases
Processes that use SAP Concur
FAQ
SAP Concur connector questions
- Which SAP Concur actions are pre-built?
- Nexus includes 15 pre-built SAP Concur actions across Budget Category (5), Budget (4), Budget Item (4), Budget Tracking Field (1) and Budget Adjustments (1).
- Can SAP Concur start a workflow?
- Runs that use SAP Concur start from a webhook, a schedule or another trigger source. SAP Concur steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the SAP Concur API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- SAP connector
Finance, procurement and sales orders.
- Human-in-the-loop
Where approval belongs in a running workflow.
- When there is no connector
API, protocol and code steps in one run.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how SAP Concur fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.