```json
{
    "title": "Purchase Approval Hierarchies and Multi-Level Sign-Off in ERPNext",
    "url": "https://aavatto.com/blog/purchase-approval-workflow-software-erpnext/",
    "datePublished": "2026-10-23",
    "dateModified": "2026-10-23",
    "language": "en-US",
    "description": "How purchase approval workflow software works in ERPNext: design a multi-level sign-off matrix, configure Workflows, and close the gaps that leak spend.",
    "author": "Aavatto",
    "publisher": "Aavatto - Frappe & ERPNext Experts | Custom Development, Implementation & Support"
}
```

# Purchase Approval Hierarchies and Multi-Level Sign-Off in ERPNext

**Purchase approval workflow software routes each purchase request or order to the right approvers based on rules such as value, department, or item category. It records who approved what and blocks orders from going out unapproved. ERPNext does this natively through its Workflow engine, so most manufacturers and distributors don't need a separate tool.**

That's the short answer. The longer one depends on how your approval hierarchy is designed. Most approval problems we see in ERPNext projects start before anyone opens the Workflow screen. A sign-off chain that only exists in people's heads can't be configured, however good the software is.

This guide covers designing the hierarchy, mapping it to ERPNext, and handling the edge cases that make approvals leak.

## Step Zero: Decide Where the Money Is Actually Committed

Most companies try to add approvals to every procurement document and end up with three sign-offs for one purchase. Ask a simpler question first: at which document does the company become committed to spending?

In ERPNext, the procurement chain usually runs like this:

Material Request

Someone says "we need this." No money is committed.

Request for Quotation / Supplier Quotation

Prices are gathered. Still no commitment.

Purchase Order

Sent to the supplier. This is the commitment.

Purchase Invoice / Payment Entry

money actually leaves.

For most businesses, the Purchase Order is where the real multi-level sign-off belongs. Material Requests may need a light, single-step check (is this genuinely needed?). Payments usually need a separate finance-side approval. Putting a full hierarchy on all three slows buying down without adding much control.

## Designing Your Purchase Approval Hierarchy

Before configuring anything, write the hierarchy as a matrix. Here is an illustrative example for a mid-sized manufacturer. The value bands are placeholders, not recommendations:

PO value (illustrative)Raw materialsCapex / machineryServices & maintenanceUp to Band APurchase ManagerPlant HeadDepartment HeadBand A to Band BPurchase Manager → Plant HeadPlant Head → Finance HeadDepartment Head → Finance HeadAbove Band BPurchase Manager → Plant Head → DirectorPlant Head → Finance Head → Director Department Head → Finance Head → Director

Building this table usually surfaces three things:

Who the approver is depends on more than value

Capex almost always needs finance involvement earlier than raw material buying does.

Some approvers are roles, others are specific people

"Director" might be one person. "Plant Head" differs by plant.

There are exceptions nobody has written down

Examples include emergency breakdown purchases, repeat orders against an annual rate contract, or imports needing a different sign-off.

If you can't fill in the matrix, that is the first thing to fix. It's also where an outside view helps: we map this matrix with procurement and finance heads in workshops as part of a tailored ERPNext implementation before any configuration starts.

*If your current approval rules live in a WhatsApp group and a senior manager's memory, sketching this matrix is a useful hour even if you never change software.*

## How ERPNext Handles Multi-Level Sign-Off

ERPNext has two mechanisms for approvals. They behave differently, so it matters which one you use.
				Workflow (the main tool)

A Workflow is attached to a document type such as Purchase Order. You define:

States

for example Draft → Pending Purchase Manager → Pending Plant Head → Pending Director → Approved → Rejected

Transitions

which role can move the document from one state to the next, using which action (Approve, Reject, Send Back)

Conditions

expressions on a transition, such as only requiring Director approval when the grand total is above a threshold, or routing differently by cost center or purchase type

Document status per state

"Approved" maps to Submitted, so the PO only becomes a committed document once the final approval is in

Once a Workflow is active, users no longer see a plain Submit button. They see the actions their role is allowed to take, and every transition is recorded in the document's history. That record is the audit trail most standalone tools advertise.
				Authorization Rule (the simpler, older option)

Authorization Rules set a ceiling: for example, Purchase Orders above a given grand total need approval from a particular role or user. They're quick to set up for one threshold. They don't model a sequence of approvers, though, and they can confuse users when combined with Workflows. For a genuine multi-level sign-off ERP setup, Workflow is the right foundation. Use Authorization Rules sparingly, if at all.

## Setting Up a Purchase Approval Hierarchy in ERPNext: The Practical Sequence

Create the roles first

Map each approver in your matrix to a role (Purchase Approver L1, L2, Finance Approver, and so on). Assign roles to users, and use Role Profiles if several people share a set.

Restrict by plant or department where needed

If "Plant Head" means a different person per plant, use User Permissions on Company, Warehouse, or Cost Center so each approver only sees their own POs.

Define Workflow States

that match your matrix, including a Rejected state and, ideally, a "Sent Back for Revision" state.

Build the transitions with conditions

Start with value-based routing, then add category or cost-center conditions. Keep conditions readable. If they grow long and nested, the matrix is probably too complicated.

Decide on self-approval

Each transition has an "Allow Self Approval" setting. Turn it off for any transition where the creator might also hold the approver role.

Turn on notifications

Workflow actions can notify the next approver by email. Many teams also add an in-app or WhatsApp notification so approvals don't sit unseen.

Test with real past POs

across every band and category before go-live. Most mistakes show up here, usually as a condition that misses an edge value.

## The Edge Cases That Make Approvals Leak

A workflow that works on day one can still let spend through later. These are the gaps we check first when auditing an existing setup:

GapWhat happensHow to close itEdits after approvalA PO is approved, then the quantity or rate is changedApproved = Submitted; changes require Cancel & Amend, which restarts the workflowApprover on leavePOs pile up in one stateAssign the role to a backup user, or build a delegation mechanism (usually custom)Creator holds approver roleA manager raises and approves their own PODisable self-approval on that transitionSplitting ordersOne large purchase is split into several POs to stay under a bandReview supplier-wise PO reports regularly; consider budget controlsBudget overrunApproved PO exceeds the cost center's budgetUse ERPNext Budgets with "Stop" or "Warn" actions on Purchase OrderWorkflow changed mid-yearExisting documents are stuck in states that no longer exist Migrate open documents before changing states

Some of these need more than configuration: delegation rules, approvals that depend on remaining budget across periods, or sign-off from a mobile app outside ERPNext. Those are cases for ERPNext customization, done in a way that survives upgrades.

## Do You Need Separate Purchase Approval Workflow Software?

Standalone approval tools are good at what they do: clean mobile approvals, Slack or Teams integration, and polished request forms. The tradeoff is a second system. Approved requests have to sync into your ERP, budgets live in one place while commitments live in another, and the audit trail is split.

If ERPNext is already your system of record for purchasing, inventory, and accounts, a well-designed Workflow covers what most manufacturers and distributors need. A separate tool makes more sense when many non-ERP users (site staff, field teams) raise requests and will never log into the ERP. Even then, ERPNext's web portal or a lightweight custom request form is often enough.

## Frequently Asked Questions

[Can ERPNext route approvals by amount?](#collapse-8591)

Yes. Workflow transitions accept conditions on document fields such as grand total, so a PO can skip or require higher-level approval depending on its value.

[Can different departments or plants have different approvers?](#collapse-8592)

Yes, through a combination of roles, User Permissions on company, warehouse, or cost center, and conditions on the workflow transitions.

[What happens if someone edits a PO after it's approved?](#collapse-8593)

In a properly configured setup, they can't edit it directly. An approved PO is submitted, so changes require Cancel and Amend, which creates a new version that goes through approval again.

[Can approvers approve from email or mobile?](#collapse-8594)

ERPNext sends workflow notifications by email and can be used on mobile browsers. Approval through WhatsApp or a dedicated app generally needs an integration or custom development.

[Should Material Requests also have multi-level approval?](#collapse-8595)

Usually not. A single-step check on Material Requests, plus the full hierarchy on Purchase Orders, gives control without slowing down every request.

## Getting the Hierarchy Right Before the Configuration

The configuration in ERPNext is the easy part. The harder work is agreeing on who signs off on what, writing down the exceptions, and closing the gaps where spend slips through. Aavatto has been building and fixing ERPNext and Frappe setups since 2020 for businesses across India and the Middle East. Approval design is one of the areas we're asked to revisit most often.

If you want a second pair of eyes on your current approval matrix, or help designing one, **[book a free ERPNext consultation](/contact-us/)**. We'll walk through how your purchase sign-off works today and what it would look like in ERPNext.