> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Build an Expense Approval Workflow With Multiple Approvers
- URL: https://blog.jestor.com/expense-approval-workflow-multiple-approvers/
- Published: 2026-07-31T15:23:56.000Z
- Updated: 2026-07-31T15:23:56.000Z
- Author: Bruno Bannach

An **expense approval workflow with multiple approvers** defines, for each stage, which person or hierarchy needs to sign off before the request moves forward. In **Jestor**, the **Approvals** app supports an approval hierarchy combined with a tier by amount and cost center, all inside a single flow.

## When does an expense need more than one approver?

Expenses above a certain amount, or that involve more than one area, often need more than one sign-off before moving to payment. Without a structured flow, that extra step just becomes one more thread of messages with no history.

## What companies are trying to solve?

- Expenses that require sign-off from more than one person before payment
- No clarity on which stage of the hierarchy a request is stuck at
- No record of who approved each stage of the process
- Difficulty applying different rules depending on the expense amount

## How does the approval hierarchy work in Jestor?

Each stage of the Kanban can require a different approver, forming a hierarchy within the same flow.

| Flow stage   | Approver                     | Criterion                      |
| ------------ | ---------------------------- | ------------------------------ |
| 1st approval | Owner of the cost center     | Every request from the area    |
| 2nd approval | Finance manager              | Amount above the defined limit |
| Approved     | Posting to the connected ERP | After every stage is complete  |

## Why choose Jestor?

- The approval hierarchy is configured right inside the Kanban, with no parallel system
- Every stage records who approved it and when, keeping a full history
- The tier by amount can automatically trigger a second approval

## Frequently Asked Questions

### Can different stages have different approvers?

Yes, each stage of the flow can have a different owner or group of owners.

### Does the system notify the next approver automatically?

Yes, notifications can be configured for every stage change on the card.

### Does the flow stay on record for future reference?

Yes, each card's history shows every approval made. Learn more at jestor.com.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.