Budget-Tiered Approval

Visual Flow

Rendering diagram…

When to Use This Pattern

Use budget-tiered approval when:

• Approval requirements vary by dollar amount (most purchase/expense processes)
• Senior leadership shouldn't be burdened by small requests under $500
• High-value requests need additional scrutiny from finance or executives
• You want to speed up low-risk approvals while maintaining controls on large spend

How It Works

Implementation Guide

Step 1: Define the Tiers

Work with Finance to establish thresholds. Store them in a configuration table (not hardcoded):

Tier	Min Amount	Max Amount	Approver Levels	Auto-Approve?
1	$0	$500	0	Yes (with audit log)
2	$501	$5,000	1 (Manager)	No
3	$5,001	$25,000	2 (Manager + Dept Head)	No
4	$25,001	$100,000	3 (+ Finance Director)	No
5	$100,001	∞	4 (+ CFO)	No

Step 2: Calculate the Request Value

The "amount" isn't always obvious:

• Purchase request: Total of all line items
• Expense report: Sum of all expenses
• Contract: Total contract value (not monthly)
• Recurring spend: Annual cost, not per-occurrence
• Multi-currency: Convert to base currency before comparing

Step 3: Resolve the Approval Chain

Based on the tier, build the approver list dynamically:

1. Manager — Look up from org chart (AD manager field, HR system)
2. Department head — Look up from department configuration
3. Finance Director — Static assignment or role-based
4. CFO — Static assignment

Step 4: Execute the Chain

Use a Serial Approval Chain for the resolved approver list. Apply the Escalation with SLA Timeout at each step.

Step 5: Handle Budget Codes and Cost Centers

Enhance the routing with budget validation:

1. Check the cost center balance before routing for approval
2. If over budget → add Finance Controller as a mandatory additional approver
3. If within budget → standard approval chain
4. After approval → deduct from budget and update the tracking system

Example: Purchase Order Workflow

1. Employee submits PO request: 3 monitors at $450 each = $1,350
2. System determines Tier 2 ($501–$5,000): Manager approval required
3. Manager receives task with full details: items, cost center, budget remaining
4. Manager approves → PO number is generated → Vendor is notified
5. If the request had been $30,000 → Manager + Dept Head + Finance Director

Tips & Best Practices

• Use annual thresholds too. An employee making twenty $400 requests per month might need review even though each one is below the threshold. Track cumulative spend per person per period.
• Account for split requests. Watch for gaming — a $12,000 purchase split into three $4,000 requests to avoid the higher tier. Flag requests from the same person for the same vendor within a short window.
• Dynamic thresholds. Consider varying thresholds by department. Engineering might auto-approve up to $2,000 for tools while Marketing has a $500 threshold.
• Show the budget context. When an approver receives the task, show: "This request is for $5,200. The cost center has $23,800 remaining of $50,000 annual budget."