The challenge
Routine requests, manual effort
PO changes and goods-receipt requests often create tickets and repeated validation work.
Live pilot
P2P Self-Service Agent
Controlled procurement requests through natural language.
A pilot for a global FMCG shared-service organisation: business rules, impact review and user confirmation remain central to every permitted action.
What the pilot shows
Natural-language requests
The agent retrieves records and checks business rules before presenting proposed actions.
The control model
Human confirmation and exceptions
Permitted actions require review; blocked requests include reasons and next steps.
The business problem
Procurement operations receive repeated requests to cancel or amend purchase orders, check goods receipts or understand transaction status. These require accurate ERP state and business-rule validation, not just a conversational answer.
Demonstrated pilot behaviour
- Retrieve the current purchase order or goods receipt
- Check eligibility and transactional dependencies
- Present impact before user confirmation
- Refuse blocked actions and route exceptions
How it works
-
01
Ask
Describe a PO or goods-receipt request.
-
02
Validate
Retrieve ERP data and test rules.
-
03
Confirm
Show impact and request explicit approval.
-
04
Execute or route
Proceed only when permitted; otherwise explain the block and route it.
The procurement workflow in practice
Recreated interface with sample data, based on a live pilot in a global FMCG shared-service organisation.
Pilot walkthrough · 01 / 04
Start from the buyer request
The buyer requests a purchase-order action; the agent obtains the relevant order context.
- Natural-language request
- Order lookup and rule checks
Recreated interface · sample data
Pilot walkthrough · 02 / 04
Make the proposed change visible
Proposed changes and their consequences are presented before confirmation.
- Explicit impact information
- User reviews before confirming
Recreated interface · sample data
Pilot walkthrough · 03 / 04
Explain why a request cannot proceed
A goods-receipt reversal is blocked because invoices are already posted; the agent explains why.
- Business-rule and state checks
- Clear explanation and suggested handover
Recreated interface · sample data
Pilot walkthrough · 04 / 04
Maintain business ownership
Permissions, business rules, confirmation and exception handling constrain automation. A schematic, not a captured audit screen.
- Authorisation and approvals
- Exceptions routed to the responsible team
Recreated interface · sample data
What the pilot demonstrates
Live pilot evidence, not measured results. No ticket-reduction or financial-savings claims are made.
A simpler request channel
Buyers can describe standard PO issues without starting from a complex form.
Validation before action
The proposed operation is checked against current transaction state.
Clear exceptions
Blocked requests are explained rather than silently failing.
Owner-controlled automation
Confirmation and business rules remain part of the workflow.
Pilot scope: purchase-order and goods-receipt requests with rule checks, impact review, confirmation and exception routing.
