Guide · Expense management

Expense Approval Workflow: How Many Levels Does Your Company Need?

By the TequioTI team · Updated: · 6 min read

A good expense approval workflow balances control and speed: too many levels and reimbursements are approved after the trip is over; too few and nobody reviews what matters. These are the criteria to decide how many levels your company needs and how to configure them.

Design principles

  • Amount should decide the level. The higher the amount, the more review.
  • Nobody approves their own expenses. Separation of duties is the foundation of control.
  • Requests and expenses are different. Approving a travel budget before spending is not the same as approving an expense already incurred.
  • The workflow should be as short as the risk allows.

Example levels by amount

The structure below is illustrative; amounts depend on each company's size and risk.

Request or expense amountWho approves
Up to a defined low amountAuto-approved if within policy
Medium amountDirect manager
High amountDirect manager and department head
Very high amount or out of policyDirect manager, department head and finance or executive

Cumulative amount: the control almost nobody configures

Someone can avoid a second approval level by splitting a purchase into several small requests. To prevent it, in addition to the individual amount, review the cumulative amount over the period: when what one person or department has requested exceeds a limit, add an approval level even if each request looks small on its own.

How many levels does your company need?

  • Small teams: one or two levels are usually enough.
  • Mid-size companies with several departments: two or three levels, with rules by amount.
  • Multi-location or multi-entity operations: separate workflows per unit, plus approval by cumulative amount.

Common mistakes

  • Adding levels “just in case” that nobody truly reviews.
  • No delegates: when the approver is on vacation, everything stops.
  • Approving by chat or email instead of leaving a record in a system.
  • Not measuring how long each level takes to respond.
  • Using the same workflow for travel, petty cash and reimbursements.

How it is configured in the Expense Portal

The portal lets you define one or several levels by amount (direct manager, a second level or specific roles), with priority and different rules for requests (travel, petty cash, reimbursement, advance) and for expenses. If no workflow is configured, the request is auto-approved. Each approver sees an inbox with what is pending and what they have already resolved, with the supporting document, the policy evaluation and the history on the same screen.

Amounts in this article are illustrative; set yours based on your operation. Last reviewed: November 2026.