Order-to-cash · Order processing
Automate order processing: from the won opportunity to the sales order.
The pack covers the stretch between CRM and ERP where most manual hand-offs happen today: from the won opportunity to the sales order, including feedback and special cases. The agent checks customer, pricing and availability, creates the order and reports it back. Automatically, as long as your rules allow it. Otherwise with approval.
- Salesforce
- SAP
- Microsoft
How an order runs through.
From the won opportunity to the sales order in the ERP. Standard cases go straight through, large orders go to approval first.
- Customer, terms and line items checked
- Order created in SAP, number back in the CRM
- Approval only where your rules require it
- Opportunity won
- Customer and terms checked✓
- Sales order created in SAPautomatic
- Opportunity won
- Large order for approvalApproval
- Sales order created in SAPapproved
Every step in the audit trail
Order processing in one minute.
An opportunity is closed-won in Salesforce, the agent checks it, gets approval and creates the order in SAP S/4HANA.
Order-to-cash: order creation from Salesforce to SAP
An opportunity is closed-won in Salesforce. The AI agent checks customer and line items, requests approval for the large order and creates the sales order in SAP S/4HANA.
What the video shows
- Opportunity set to “Closed Won” in Salesforce
- The AI agent starts automatically
- Business partner and line items checked
- Approval for the large order (guarded autonomy)
- Sales order in SAP S/4HANA (VA03)
- Order number written back to Salesforce
- Run log in the audit trail
The pack at a glance.
| Element | Order processing |
|---|---|
| Problem | Won orders are keyed from the CRM into the ERP by hand. Credit limits, blocks or price deviations surface only during entry, and questions go back and forth by email. |
| Trigger | Opportunity status changes to “won” in the CRM |
| Inputs | Opportunity with line items, quantities and terms; account and contact; business partner, pricing, availability, credit limit and blocks from the ERP |
| Automated actions | Map the account to the business partner, check the order data, create the sales order, write number and status back to the CRM, send the order confirmation |
| Boundaries | Ends with the created and confirmed sales order. Delivery, billing and cash collection stay in your existing processes. The agent does not negotiate prices or terms. |
| Approvals (Guarded Autonomy) | Special discounts, non-standard payment terms or an order value above your limit go to approval. In the example, a special discount above 10% or an order from €50,000 goes to the sales manager, an order from €250,000 or changed terms to finance and sales. With a credit or order block, the agent stops. |
| Target KPI | Share of orders without manual intervention (straight-through processing rate), cycle time to the order |
| Example systems | Salesforce, SAP S/4HANA or ECC, Microsoft 365 (Teams, Outlook). Other CRM and ERP systems after a case-by-case check. |
| Implementation effort | Depends on which interfaces already exist, how clean customer and material master data are and how many special cases your rules cover. Starts with a fixed-scope proof of value, typically 4 to 6 weeks. |
| Maturity | Video demo available. For your landscape, we measure in the proof of value with your systems. |
Before and after: the gap between sales and order management.
Today
- The opportunity is won in the CRM, the order is keyed into the ERP by hand.
- Credit limits, delivery blocks or price deviations surface only during entry.
- Questions between sales and inside sales go back and forth by email and Excel.
- Days later, the CRM still doesn’t show whether and how the order was created.
With Nexus
- The agent takes over the step from the won opportunity to the sales order.
- Customer, terms, pricing and availability are checked in the ERP before the order is created.
- The agent creates standard orders itself; special cases go to approval with full context.
- Order number and status appear in the CRM right away, and the customer gets a confirmation.
Which part of order-to-cash is automated?
Order-to-cash runs from the order to the incoming payment. The pack covers the stretch from the won opportunity to the confirmed sales order, including feedback and special cases. Delivery, billing and cash collection stay in your existing processes.
| Step | System (example) | Covered by |
|---|---|---|
| Take over the won opportunity | Salesforce | Order processing pack |
| Check the order: business partner, pricing, availability, credit limit, blocks | SAP | Order processing pack |
| Create the sales order | SAP | Order processing pack |
| Update the CRM and send the order confirmation | Salesforce, Outlook | Order processing pack |
| Assess special cases and route them for approval | Teams, Outlook | Order processing pack |
| Delivery | SAP | Your existing process; exceptions via the delivery exceptions pack |
| Billing and invoicing | SAP | Your existing process; invoice discrepancy pack in preparation |
| Incoming payments, dunning, DSO | SAP | Your existing process, not part of the pack |
The order arrives in the ERP already checked. The downstream steps stay in the processes you already run.
The flow in nine steps.
This is how an order moves through the pack, shown here with Salesforce, SAP and Microsoft 365. In the demo we walk through one standard case and one special case.
Opportunity won
The status change in Salesforce starts the process. Line items, quantities and terms come from the opportunity.
Check account and business partner
The agent maps the Salesforce account to the SAP business partner and checks master data and addresses.
Validate order data
Mandatory fields, material numbers, ship-to address and payment terms are checked against your rules.
Check pricing and availability
Pricing and availability checks run in SAP. Deviations from the quote become visible.
Assess risk
Order value, discount, credit limit and blocks decide according to your policies: execute, request approval or stop.
Create the sales order
In the standard case the agent creates the sales order directly, protected against duplicate execution.
Update the CRM
Order number, status and any deviations are recorded on the opportunity.
Customer gets a confirmation
The order confirmation goes to the customer via Outlook; sales sees it in the CRM.
Special cases go to the right decision-maker
Special discount, changed payment terms or a blocked customer: the request goes to the sales manager or finance with all the data.
Simulation: one order, sped up.
The following animation is a simulation with sample data. It shows how the agent reads, checks, decides and acts. It is not a recording from a customer system.
Order Agent. Detects won opportunities in Salesforce, creates the SAP sales order and confirms to the customer.
- OAuth / SSO
- RBAC
- Policies
- Audit Trail
- Encryption
voluro
Order Agent
Order processing: opportunity to sales order
Ready
- Read opportunity(pending)
- Load context(pending)
- Evaluate rules(pending)
- Create SAP order(pending)
- Update Salesforce(pending)
- Send confirmation(pending)
Listening for
business events
Salesforce
Sales Cloud
- Opportunity
- Customer
- Quote
Salesforce Sales Cloud
Read
- • Account
- • Opportunity
- • Quote
Write
- • Opportunity
- • Activities
SAP
S/4HANA
- Business Partner
- Pricing
- Sales Order
- Availability
SAP S/4HANA
Read
- • Customer
- • Pricing
- • Availability
Write
- • Sales Order
- • Delivery
Microsoft
365 / Azure
- Identity
- AI / Models
- Communication
Microsoft 365 / Azure
Read
- • Identity
- • Mail templates
Write
- • Outlook mail
- • Teams message
Monitoring & Operations
- Logging
- Audit Trail
- Runtime Monitoring
- Cost Control
- Human-in-the-Loop
- Waiting for activity…
Order Agent
Ready
- (pending)
Salesforce
New opportunity · ACME GmbH · €38,400
- (pending)
Order Agent
Context loaded · business rules evaluated
- (pending)
SAP S/4HANA
Sales order #104872 created
- (pending)
Salesforce
Stage: Proposal → Closed Won
- (pending)
Microsoft
Confirmation sent to purchasing@acme.de
- (pending)
Completed
8 actions · 0 manual handovers · fully logged
ROI hypothesis: where the value comes from.
With sales order automation, the value comes mainly from three sources. First, manual entry disappears for every standard order that runs through without intervention. Second, corrections and follow-up questions drop because pricing, availability and blocks are checked before the order is created. Third, the customer gets the confirmation sooner.
A first estimate needs only a few figures: orders per month, handling time per order today, the expected share of standard cases and an internal hourly rate. The calculator on the process check page gives you a rough business case in a few minutes.
The result remains a hypothesis. In the proof of value we measure the actual figures with your data, and only those figures should carry an investment decision.
Calculate and read on.
Rough out your business case
The calculator on the process check page estimates time saved and value from your own assumptions.
Order entry from email and PDF
The pack’s second entry point: read orders from the inbox, check them against SAP and create them.
Delivery exceptions
For shortages, price deviations or delivery blocks that come up after the order.
SAP–Salesforce integration
How Nexus connects CRM and ERP at the process level, beyond this pack.
- Insights
How AI agents write to SAP safely
Identity, policies, approvals and idempotency when an agent creates the sales order.
- Insights
What is agentic process automation?
Definition, how it differs from RPA and workflows, and an order-to-cash example.
Risks and how the pack limits them.
A sales order is a real transaction. That is why the rules in Nexus, not the language model, decide whether an action is executed, sent for approval or stopped.
Duplicate orders
Every execution is idempotent. If a run is retried or interrupted, the order is still created only once.
Unclear master data
If the account can’t be mapped to a business partner unambiguously, the agent creates no order and flags the case to your team.
Wrong terms
Prices come from ERP pricing. If they deviate from the quote, the order goes to approval instead of into the system.
Lack of traceability
Which data was read, which rule applied, who approved and what was created: every step is in the audit trail.
Untested changes
Agent, tools and policies are versioned and move through separate DEV, TEST and PROD environments.
Data quality
Incomplete master data raises the exception rate. The proof of value shows this early, and that alone is a useful result.
Integration scope, by example.
The pack uses your existing interfaces. Nexus turns them into controlled agent tools with their own permissions. In this example that means Salesforce, SAP and Microsoft 365. Other CRM and ERP systems are connected via suitable APIs, events or MCP, after a case-by-case check.
Salesforce
- Opportunity
- Opportunity line items
- Account
- Contact
SAP S/4HANA or ECC
- Business partner
- Pricing
- Availability check
- Credit limit
- Delivery block
- Sales order
Microsoft 365
- Teams (approvals)
- Outlook (approvals, confirmation)
KPI definitions: what we measure.
In the proof of value we agree on the KPIs up front, including the measurement period and a baseline from your current process. Measurement uses your data, so you decide on production based on real figures.
Order processing KPIs
- Straight-through processing rate: orders without manual intervention divided by all orders in the period
- Manual interventions per order: approvals, corrections and queries per order
- Cycle time: from the won opportunity to the created sales order
- Exception rate: share of orders with approval or stop, broken down by reason
- Approval time: from the approval request to the decision
Getting started: a fixed-price proof of value.
In typically 4 to 6 weeks we get the pack running against your systems in a test or sandbox environment. You end up with measured KPIs and a go/no-go decision on production.
In the proof of value
- Connection to your CRM and your ERP test system
- Capabilities mapped to your fields and interfaces
- Your approval rules as policies in Nexus
- Standard and special cases run with real data
- KPI evaluation and go-live recommendation
Questions about order processing.
We are still on SAP ECC, not S/4HANA. Does that work?
Usually, yes. The pack works with business capabilities such as erp.salesOrder.create. Whether an OData service in S/4HANA or an ECC function exposed via OData, SAP Integration Suite or a custom API sits behind it is mapped during implementation. The process stays the same.
Our orders use a lot of custom fields. Is that a problem?
No. Nexus reads your systems’ metadata, including custom objects and fields in Salesforce and customer-specific fields and APIs in SAP. We decide together which of them the agent reads or writes.
Our ERP isn’t reachable from the internet. How does Nexus connect?
Through a small relay service in your network. It only opens outbound connections, you don’t open any inbound port, and a local allowlist defines which target systems it can reach. Your systems stay behind your firewall.
We already use Agentforce. Why the pack?
Agentforce is strong inside Salesforce. The order, however, is created in the ERP, with credit checks, pricing and approvals. Nexus handles that cross-system part and can bring in Agentforce as a trigger or conversational front end. Policies and audit trail apply to the actions that run through Nexus tools.
Start with one process.
30 minutes · free · with a senior architect. You get a verbal initial assessment and concrete next steps.