## TL;DR

Large invoices need sequential approvals up the chain, each level adding scrutiny. Design chains that escalate by amount, allow any level to reject back to the submitter, and run levels in order (not parallel) so each approver sees prior approvals. Time-box each level with escalation so chains do not stall.

## Steps

1. Define chain levels by amount tier.
   Expected: An escalation ladder.
2. Configure sequential (not parallel) approvals.
   Expected: Each level sees prior decisions.
3. Allow reject-to-submitter from any level.
   Expected: A clear failure path.
4. Time-box each level with auto-escalation.
   Expected: No stalled chains.
5. Record the full chain on the invoice.
   Expected: Audit trail.

## When to use

- High-value invoices
- Capital expenditure
- Regulated industries

## When not to use

- Routine low-value invoices
- Emergency payments
- PO-matched auto-approvals

## Compatibility

ERP workflows and AP tools.

## Variant phrasings

### multi-level invoice approval

### approval chain large invoice

### sequential approvals AP

## Root cause

No single person should approve very large spend alone. Sequential chains distribute accountability and let each level focus on its concerns.

## Edge cases

- Parallel approvals look faster but lose the information cascade; prefer sequential
- Delegation must preserve the level, not skip it
- Chain breaks (approver leaves) need automatic rerouting

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_UYxBNZfIHgNGFjExjhM9Ig