case-header-mgmt

Multi Level Approval Workflow: Patterns, Platforms, and Governed Rules

Sreenidhe SP Head of Content

Updated on 20 Nov 2026 • 9 min read

TL;DR

  • Multi-level approvals follow four routing patterns: sequential, parallel, conditional by dollar amount, and hybrid.
  • Each level with several approvers needs an any-or-all rule: one approver decides, or all must agree.
  • A threshold ladder sets who signs, such as a manager alone under $1,000 and Finance added above it.
  • Kissflow chains stay moving when written rules cover delegation, reminders, escalation, and who may change a threshold.

A multi-level approval workflow routes a request through two or more reviewers before it is finalized. Reviewers act in sequence, in parallel, or by rule. Common requests include invoices, purchase orders, and leave requests. A rejection at any level stops the flow and notifies the requester, and every decision is recorded for audit.

A weak approval chain shows at close. A vendor invoice above the CFO’s limit sits with an approver who is out on leave. The requester cannot see where it stands, and the auditor wants to know who signed the last three like it. If you are the Controller in that seat, the missing piece is a written rule for what happens next.

This guide covers the parts of an approval chain, the routing patterns, and the approval matrix. It then walks through the build, the failure cases, the audit record, and the tools teams use.

What AI changes in a multi-level approval workflow

Enterprises usually revisit approvals when the close slips or an AI mandate arrives. Most delays are not the decision itself. They are the wait while an approver chases documents and checks policy. AI changes that slow part. An agent gathers the invoice, PO, and receipt, checks them against the approval matrix, and flags what is missing. The approver then decides with the full picture. A named person stays accountable at every level.

An agent can only follow rules that exist. That is why the matrix and the failure rules below matter more with AI, not less. Invoice and PO approvals are steps inside Procure-to-Pay, and leave requests sit inside Hire-to-Retire. Treat each chain as part of that larger stream, not a standalone form.

What are the core components of a multi-level approval workflow?

Every working approval chain rests on the same parts, whatever tool runs it. One part is easy to miss: the person who owns the rules.

  • The request: The item under review, such as an invoice, purchase order, or leave request, carries the amount, department, and type that routing reads.
  • The levels: Ordered tiers of reviewers form the chain, for example Level 1 (Team Lead) → Level 2 (Manager) → Level 3 (CFO).
  • The rules: Conditions decide which levels a request visits, so a small purchase skips the CFO while a large one climbs all the way.
  • The outcome: Each decision ends in approve, reject, or return with comments, and the request moves forward, stops, or loops back.
  • The record: Every step logs who decided, when, and why.
  • The owner: One named person decides who may edit thresholds and approver lists.

What types of multi-level approval routing are there?

Microsoft Learn documents sequential and parallel approvals as separate Power Automate patterns. Real approval chains end up mixing both, with conditions layered on top.

  • Sequential: Each level acts only after the one before it approves, so the order is fixed (Team Lead → Manager → CFO). Microsoft Learn’s sequential example holds invoices over $1,000 for pre-approval before the Finance department signs.
  • Parallel: Several reviewers act at the same time and each decision stands on its own (Legal and Finance reviewing one contract together). Microsoft Learn applies the same pattern to invoices, purchase orders, and vacation requests.
  • Conditional: The request’s own data picks the route, whether that is dollar amount, department, request type, or risk. An invoice under the manager’s limit never reaches Finance.
  • Hybrid: A parallel review runs first, then the request moves up a sequential path for executive sign-off. Cognito Forms treats this kind of combination as the normal shape of real-world approval work.

The pattern settles who sees a request. How many people at one level must agree is a separate setting.

Must every approver sign, or only the first to respond?

Power Automate makes you choose at each approval step: “Everyone must approve” or “First to respond.” Microsoft Learn states that under the everyone-must-approve type, a single rejection rejects the whole request.

The same choice appears outside Power Automate. Routable lets accounts payable teams require “any” or “all” of the approvers listed on a bill. In Business Central, workflow user groups order approvers by sequence number, and a configuration can require only one of two approvers.

A practical decision rule:

  • Use all when each reviewer checks a different risk, such as Legal reading contract terms while Finance reviews budget.
  • Use any when approvers are interchangeable, such as two AP managers covering one invoice queue.
  • Log the responder whenever you use any. The first responder carries the decision alone, and auditors will ask who it was.

Once each level has its rule, the next question is where the levels come from. That answer lives in the approval matrix.

What is an approval matrix, and where should the dollar thresholds sit?

Jotform notes that the approval matrix is also called a schedule of authority. It is a written table of who may approve what, up to which amount. Zenphi’s glossary offers a clean starting ladder:

Request amount Approvers required Basis
Under $1,000 Manager only Zenphi’s published ladder
$1,000-$10,000 Manager, then Finance Zenphi’s published ladder
Over $10,000 Manager, Finance, then a department head or executive Extension of the same ladder

Other teams set the executive trigger higher. An SPGuides tutorial adds director approval once a purchase passes $20,000. Moxo’s sample matrix reserves CFO sign-off for requests above $50,000.

No single number is correct. What matters is that the matrix, the workflow configuration, and the written spending policy carry identical figures. When the three disagree, the workflow is enforcing a policy nobody approved. A matrix written down this precisely also becomes the build specification.

How do you build a multi-level approval workflow step by step?

Settle the rules before you open the tool.

  1. Write the approval matrix first, with every threshold, approver role, and any-or-all rule in one place.
  2. Record the request on a form or list with the fields routing reads: amount, department, request type, and cost center. In Power Automate builds, this is usually a SharePoint list.
  3. Add the first level. In Power Automate, the “Start and wait for an approval” action holds the flow until the approver responds.
  4. After each approval, add a condition on the amount. The request climbs a level only when the matrix says so.
  5. Handle rejection explicitly by notifying the requester with the reason and ending the run. In Power Automate, add a Terminate control after the notification step.
  6. Send approval notifications where approvers already work, such as Slack or Microsoft Teams, with a link back to the full request.
  7. Test one request per tier, plus one rejection, before a real invoice goes through.

These steps cover the paths a request is supposed to take. The harder design work lies in the paths it takes anyway.

What happens when a request is rejected, an approver is away, or nobody responds?

A request that holds up a close is often waiting on an approver who is away or has not responded. Signavio notes that a rejection from the first approver takes effect immediately. That outcome is the clean case.

Absence and silence are messier. Kainolab’s guidance covers delegation, timed reminders, and returning an edited request to the right step.

What should the rules for failure cases cover?

Each failure case needs a written rule, a named owner, and a log entry.

Situation Rule to write down Who owns the rule What the log records
Rejection at any level Stop the flow, notify the requester with the reason, and treat any resubmission as a new request Process owner Rejecting approver, timestamp, and comment
Approver absent Route to a named alternate at the same or higher authority, never to someone below the threshold The approver’s manager Original approver, delegate, and delegation dates
No response Send a reminder, then escalate one level up Process owner Reminder and escalation times, and who received each
Request edited after approval Return it to the first level whose decision the edit affects, and void approvals from that level onward Process owner Fields changed and approvals voided
Threshold or approver change The policy owner approves the change, and an administrator applies it Policy owner, applied by IT Old value, new value, who changed it, and when

Who should be allowed to change an approval threshold?

The person who submits requests should never be able to edit the rule that routes them. Finance owns the number, IT applies it, and the log keeps both names.

A $10,000 limit that moves without a record is a control failure, even if every individual approval looked correct. Moxo’s tier model helps here: once each threshold sits in its own row, any change becomes a visible edit.

The log is only useful if it records the right fields.

What should a multi-level approval audit trail record?

An approval record that says only “approved” fails the first question an auditor asks: approved by whom, under which rule, and when?

  • Identity: Each entry names the approver and the level they acted at.
  • Decision: The decision is approve, reject, or return, with the comment that explains it.
  • Time: Every action carries a timestamp, including reminders and escalations.
  • Rule version: The rule version that routed the request stays on file, so a later threshold change does not rewrite history.
  • Delegation: Delegation events show who acted on whose behalf.
  • Request versions: Each request version is kept, so an edit after approval is visible and the voided approvals remain on the record.

For US public companies, SOX internal-control testing is one reason auditors ask for this level of detail. Tools differ in which parts of this record come by default and which you assemble yourself.

Which tools run a multi-level approval workflow?

Multi-level approvals run in flow builders such as Microsoft Power Automate, and also inside ERPs, accounts payable platforms, code-first orchestrators, and IT service tools.

This guide is published by Kissflow, so it is listed first. The other seven tools are listed in no particular order.

Tool Where it sits Approval behavior What adopting it requires
Kissflow Agentic platform connected to ERP, CRM, and other core systems Agents prepare each decision, people approve, and an audit trail records every step A business outcome to start from; Kissflow helps set it up in year one, and your team runs it from year two
Microsoft Power Automate Microsoft flow builder, usually paired with SharePoint Approval actions inside flows, with the any-or-all and rejection settings covered in the earlier sections A flow builder who wires each level, condition, and notification
SAP S/4HANA ERP system of record Multi-step approvals, including block steps for journal entries SAP administrators who configure workflow inside the ERP
Business Central (Microsoft Dynamics) ERP system of record Workflow user groups ordered by sequence number An administrator who sets up each user group and its sequence
Jinba AI approval workflow builder Natural-language design refined in a visual editor, automated audit trails, and a vendor-stated SOC 2 certification A team that writes the workflow in plain language, then refines it visually
Routable Accounts payable platform Multiple approvers on bills over a set amount, such as anything over $1,000 going to the AP Manager and then the CFO An AP team that configures bill approval rules and approver lists
Temporal Code-first workflow orchestrator Each level waits for every user assigned to it before the workflow moves on Engineers who write and operate the workflow code
Jira (Atlassian) Issue tracking with approval fields Two custom fields, approval group 1 and approval group 2, mapped to federated groups controlled in Google Workspace A Jira administrator who maps approval fields to groups

Read the “What adopting it requires” column before “Approval behavior.” The setup a tool demands predicts fit better than its feature list does.

Which approval pattern fits what you are routing?

The request type decides the pattern. These examples match common requests to a pattern.

  • Vendor invoices suit conditional sequential routing on amount, with the matrix thresholds deciding when Finance and executives join.
  • Purchase orders with contract terms suit a hybrid chain: Legal and Finance review in parallel, then executive sign-off above the top threshold.
  • Leave requests follow a short sequential path, team lead to manager to HR, and rarely need conditions.
  • IT service requests for application access pair the requester’s manager with the system owner, often as an any-mode group in ServiceNow or Jira.
  • If a request type fits none of these, add a new row to the matrix before you add a new branch to the workflow.

Where does Kissflow fit when approvals span SAP, Oracle, and Workday?

A purchase that needs a Salesforce contract review, a Workday headcount check, and an SAP posting has no single system that owns its approval chain. Many of these chains still run on email and spreadsheets.

Kissflow works with large enterprises to redesign how work gets done, builds it on its own agentic platform, and stays with the change until the customer’s team owns it. For approvals, Kissflow starts from the outcome your finance or operations team owns, such as a faster close. It redesigns approvals across the whole Procure-to-Pay stream, not one chain at a time.

Agents gather the documents, check them against policy, and flag what is missing. People decide at the points the matrix defines, and the result posts back to the ERP. Teams describe the process in a prompt, sketch, photo, or requirements document. No code is generated. Role-based access, data controls, and an audit trail cover every step. In year one, Kissflow helps your team set up the capability. From year two, your team runs it.

If your chain already lives in Power Automate, compare on three questions. Who builds the chain? Who governs a rule change? Does one request cross systems beyond Microsoft 365?

Frequently asked questions

What is the difference between a workflow and an approval process?

An approval process is one decision stage inside a workflow. The workflow carries a request from intake to completion, while the approval process is where reviewers decide whether it may proceed. A workflow can have no approval at all, but every approval process runs inside some workflow.

How do I implement a Power Automate multi-level approval workflow with multiple approvers?

Use one “Start and wait for an approval” action per level, and choose “Everyone must approve” or “First to respond” for any step with more than one approver. Between levels, add a condition on the amount so the request climbs only when your approval matrix says it should, and end rejected runs with a Terminate control after notifying the requester.

What is a workflow in management?

In management, a workflow is an ordered path that work follows between people or systems, with rules that decide who acts next. For approvals, that means a request passes through defined levels, each ending in approve, reject, or return. A governed workflow also names an owner for the rules and keeps a record of each decision.

What do I need before creating an approval workflow?

You need an owner for each rule, not only a matrix. List every threshold, approver role, and any-or-all rule, then name who may change each one. Confirm the platform can route by amount and send reminders, and agree the figures with the policy owner before anyone builds.

How many approval levels should a workflow have?

Use as many levels as your written spending policy names, and no more. Each level adds another queue a request waits in, so a level that never changes a decision costs time without adding control. When a threshold changes, review the levels and drop any whose approvers no longer add a check.

Tell us which approvals are slowing your business down.