Multi-Tier Supplier Approval Without the Bottleneck

Category: Procurement & Supply Chain | Reading time: 5 min

---

The Approval Bottleneck That Kills Procurement Efficiency

Every procurement team knows this scenario: a $40,000 purchase order for critical equipment needs VP approval, but the VP is in a week of back-to-back board prep. The order sits. The supplier chases. Operations is blocked. By the time approval arrives, the supplier has allocated inventory elsewhere.

The bottleneck isn't the approval requirement — it's the process. Manual approval workflows depend on email availability, calendar coordination, and individual responsiveness. These are not reliable mechanisms for time-sensitive procurement decisions.

AI-driven procurement with tiered approval routing eliminates the process bottleneck without eliminating the controls. The VP still approves the $40,000 order. But they do it in a structured queue with full context, on their timeline, and the AI handles everything else automatically.

---

The Tiered Approval Matrix

A well-designed procurement approval matrix has four tiers:

Amount Range	Required Approver	Typical Use Case
< $1,000	Automatic (no approval)	Office supplies, small subscriptions
$1,000 – $25,000	Procurement Manager	Standard vendor POs, recurring services
$25,000 – $250,000	VP Operations/Finance	Capital equipment, major contracts
≥ $250,000	CPO/CFO	Strategic supplier relationships, large projects

The matrix is straightforward. Enforcing it consistently across hundreds of daily transactions, multiple agents, and varying submitter roles is where the complexity lies.

---

Policy Encoding: The Matrix as Rego

package taos.procurement.purchase_approval

# Tier 1: Auto-approve
tier_auto {
    input.amount < 1000
    input.vendor_status == "approved"
    input.is_ofac_cleared == true
}

# Tier 2: Procurement manager
tier_manager {
    input.amount >= 1000
    input.amount < 25000
    input.vendor_status == "approved"
    input.is_ofac_cleared == true
}

# Tier 3: VP approval
tier_vp {
    input.amount >= 25000
    input.amount < 250000
    input.vendor_status == "approved"
    input.is_ofac_cleared == true
}

# Tier 4: CPO/CFO
tier_executive {
    input.amount >= 250000
    input.vendor_status == "approved"
    input.is_ofac_cleared == true
}

# Role assignments
required_role = "procurement_manager" { tier_manager; not tier_vp; not tier_executive }
required_role = "vp_operations"       { tier_vp; not tier_executive }
required_role = "cfo"                 { tier_executive }

# Allow auto-approved tier; require approval for others
allow { tier_auto }
action = "allow"            { tier_auto }
action = "require_approval" { not tier_auto; not deny_blocked }
action = "deny"             { deny_blocked }

This policy is evaluated in milliseconds. The routing decision — which approver tier is required — is made by the policy engine, not the application, not the LLM.

---

Routing in Practice: What the Approver Sees

When the policy engine determines that VP approval is required, the kernel creates a structured approval request:

{
  "approval_id": "appr-vp-7821",
  "required_role": "vp_operations",
  "request_summary": {
    "supplier": "Industrial Equipment Corp",
    "po_number": "PO-2024-0441",
    "amount": 87500.00,
    "category": "capital_equipment",
    "department": "Manufacturing",
    "justification": "Replacement of line 3 press — current unit failing MTBF",
    "budget_line": "CAPEX-2024-MFG-003",
    "budget_remaining": 142000.00
  },
  "submitted_by": "procurement_manager",
  "policy_rule": "tier_vp",
  "expires_at": "2024-03-17T17:00:00Z"
}

The VP sees: supplier, amount, category, department justification, budget line, and remaining budget. Everything needed to make an informed decision. No email chain to reconstruct. No missing context. One click to approve or reject with an optional note.

The AI assembled this context. The VP provides the decision.

---

Delegation Chains: When the Primary Approver is Unavailable

What happens when the VP is genuinely unavailable — on leave, in a restricted zone, illness? Taos supports delegation chains:

# Delegated approval: if primary approver has delegated authority
# to a backup, the backup's approval is sufficient
tier_vp_delegated {
    tier_vp
    input.vp_delegated_to != null
    input.approver_role == input.vp_delegated_to
}

action = "require_approval" { tier_vp_delegated }
required_role = input.vp_delegated_to { tier_vp_delegated }

The VP's out-of-office delegation is recorded in the system. The kernel routes to the delegated approver automatically. The OBO chain records both the original authority (VP tier) and the delegated approver — full accountability without process delay.

---

Budget Enforcement: Policy Before Payment

Approval routing is necessary but not sufficient. The VP shouldn't be approving orders that would exceed the department's approved budget — even if the transaction size is within their authority.

Add a pre-condition budget check:

# Block if this PO would exceed the department's remaining budget
deny_budget_exceeded {
    input.po_amount > input.department_budget_remaining
}

# Allow budget overrun only with explicit CFO override
allow_budget_override {
    deny_budget_exceeded
    input.cfo_budget_override_approved == true
}

action = "deny"             { deny_budget_exceeded; not allow_budget_override }
action = "require_approval" { deny_budget_exceeded; not allow_budget_override }
required_role = "cfo"       { deny_budget_exceeded }

Budget compliance is now a policy control, not a dashboard check after the fact.

---

Measuring the Efficiency Gain

For a procurement team processing 200 POs per month with the tiered structure:

Tier	Volume	Before Taos	After Taos
Auto (<$1K)	60% (120 POs)	1–2 day manual	Seconds
Manager ($1K–$25K)	30% (60 POs)	2–5 days email	Hours (queued review)
VP ($25K–$250K)	8% (16 POs)	3–10 days	Hours (structured queue)
Executive (>$250K)	2% (4 POs)	1–3 weeks	Days (structured queue)

The auto-approve tier eliminates 120 monthly manual reviews. The structured queues for higher tiers eliminate the email reconstruction overhead for every remaining review.

---

The Bottom Line

Multi-tier supplier approval doesn't have to be a bottleneck. The approval requirement exists for good reasons — financial control, budget management, supplier risk management. The bottleneck comes from the process, not the requirement.

Taos makes the approval process fast by making it structured, policy-driven, and context-complete. The right person approves every time. The wrong person can't self-approve. And the process takes hours where it used to take weeks.

---

Tags: procurement approval, multi-tier approval, supplier management, AI procurement, purchase order workflow, financial controls