Sales Order Approval Workflow
Catch risky orders before they ship — automate amount and term control.
What problem does it solve?
High-value or off-policy sales orders get approved without control; margin erodes, credit limits are breached and the accountability trail goes unrecorded.
How does the solution work?
Conforcus's sales order approval workflow automatically blocks the order against amount, customer and pricing/payment-term thresholds and routes it through a multi-level release flow. Delivery and billing stay locked until approval completes.
What changes in practice?
The control runs directly on the sales order. When an order is created or changed (VA01/VA02), the amount, customer-group and condition-based rule tables are read; if a defined threshold is exceeded, the document receives an approval block through status management and the multi-level release flow starts. Orders that stay within the thresholds continue through the standard flow without waiting. On an order carrying the approval block, the delivery and billing lock is in force, so the shipping team cannot process the document. The order status shows which approval level the document is waiting at, and the sales representative and the manager read the same information from the order.
Every approval step is recorded: who approved what, and when, can be followed order by order. A rejected order stays blocked; the sales representative corrects the document and submits it for approval again. Because thresholds are kept in rule tables, a change in pricing or credit policy means updating table entries rather than the flow itself. In daily work the sales team does not wait for approval on standard orders, and only exceptions reach managers. Margin and credit risk become visible while the order is being entered, not in a report after shipment, and the decision is taken at that stage.
Benefits
- Margin and credit risk are caught at order entry, not after shipment
- Fully traceable approval chain — who approved what and when
- Sales accelerates on standard orders; only exceptions reach managers
Where it sits in SAP
Status management and approval block on the sales order (VA01/VA02); amount, customer-group and condition-based rule tables, multi-level release workflow and a delivery/billing lock. Live across multiple sectors.
Who it is for: Sales Director, Sales Manager, CFO (credit/margin control)
Frequently asked questions
Which sales orders go to approval, and do we have to wait for approval on every order?
No; rule tables decide which orders enter approval. Criteria such as an amount threshold, the customer group and price or payment terms are defined in these tables, and an order that hits a rule is blocked automatically and enters the approval flow. Orders that do not hit a rule continue to delivery through the standard flow, so the sales team waits for approval only on exceptions.
Can an order awaiting approval be delivered, and what happens on rejection or when the order changes later?
Until approval is complete the order stays blocked, and neither a delivery nor an invoice can be created. A rejected order also stays blocked; the sales representative corrects the document and submits it for approval again. The rules are evaluated on order changes as well (VA02), so an approved order whose amount or conditions later move beyond a threshold goes back into approval.
How does the multi-level approval work, and can we see afterwards who approved what and when?
The approval levels an order has to pass are determined by the amount, customer-group and condition-based rules; when a level approves, the document moves on to the next. The status on the order shows which level it is currently waiting at. Who took each decision and when is kept on record, so sales management and finance can trace the approval chain afterwards.