Dynamic Hierarchical Approval automatically escalates invoice approvals based on user approval limits and supervisor hierarchy.

If the initial approver cannot approve the invoice amount, Brightflag adds their supervisor as the next approver.

This continues until an approver with sufficient approval authority is reached.

When an invoice reaches a Dynamic Hierarchical Approval stage in a workflow:

1️⃣ The initial reviewer receives the invoice.

2️⃣ Brightflag checks the reviewer’s Approval Limit.

3️⃣ If the invoice exceeds the limit, the reviewer’s Supervisor is added as the next approver.

4️⃣ The process continues up the supervisor hierarchy until someone with sufficient approval authority approves the invoice.

📌 Supervisors are added after the original reviewer — not instead of them.

Approval limits always use the customer’s account currency.

If an invoice is submitted in another currency:

1️⃣ Brightflag converts the invoice amount to account currency
2️⃣ The invoice date exchange rate is used
3️⃣ The converted amount determines whether escalation is required

A Fallback Reviewer is added if Brightflag cannot determine the correct escalation path.

This occurs when:

This prevents invoices from getting stuck in the approval workflow.

Yes — initially.

Brightflag Application Support must configure the approval limit values available in the system.

Once configured, Admins can assign those limits in User Management.

If an invoice exceeds the user's approval limit and no supervisor is configured, Brightflag adds the Fallback Reviewer.