Power Automate PO Approval with Multi-Entity Policy
Validate purchase orders in Power Automate against entity-specific approval thresholds, vendor approval lists, and budget availability before routing — without maintaining complex approval matrices per entity.
Das Problem
Validate purchase orders in Power Automate against entity-specific approval thresholds, vendor approval lists, and budget availability before routing — without maintaining complex approval matrices per entity.
Einrichtungsschritte
- 1
Import Corules Custom Connector to Power Platform
- 2
Configure entity-specific parameters in Corules admin (AU thresholds: $10k/$50k/$100k, EU: €8k/€40k/€80k)
- 3
Add Corules 'Get Constraints' action to PO creation Flow to retrieve required approver level
- 4
Route the PO to the correct approver based on returned constraint (manager / director / executive)
- 5
On approval completion, call Corules 'Validate Decision' with approver identity for audit log
Codebeispiel
// Get Constraints: what approval level is required?
POST /v1/constraints
{
"use_case": "po_approval",
"actor": "{{ requestor_upn }}",
"context": {
"amount": 45000,
"currency": "AUD",
"entity": "AU",
"vendor_id": "VND-0042",
"department": "engineering",
"budget_code": "ENG-2026-Q1"
}
}
// Response:
{
"constraints": {
"required_approver_level": "director",
"vendor_status": "approved",
"budget_remaining": 112000
}
}Frequently Asked Questions
Can thresholds be maintained in Corules rather than Power Automate?
Yes — that is the design intent. Approval thresholds live in Corules parameters, not in Flow logic. Business owners update thresholds in Corules; the Flow reads them at runtime.