← All posts

Multi-Level Approval Workflows on NocoBase: Purchase Request → Manager → Accounting → Director

by BAMFLOW • • 5 min read

Multi-level approval workflow on NocoBase: purchase requests through manager, accounting and director — no chat drift, full approval history.

cover-final

Multi-Level Approval Workflows on NocoBase: Purchase Request → Manager → Accounting → Director

Every growing company runs an informal "approval system" on chat apps and paper — and suffers its two diseases. The first is drift: a purchase request posted at 9 a.m. is buried under forty messages by the afternoon; the approver never sees it, work stalls, and by the time anyone asks, the supplier is out of stock. The second is no trace: three months later accounting asks who approved a purchase, when, and why at that price — and the only answer is an archaeological dig through chat history. This article builds a multi-level approval workflow on NocoBase, the open-source, self-hosted no-code platform, following one purchase request through four approval levels — and states the current limitations plainly. New to the platform? Read What is NocoBase first.

One real process, end to end: a purchase request through four approvals

Follow a typical purchase request in a 60-person company. The requester creates it inside the system: items, quantities, intended supplier, unit prices, total, justification, needed-by date. On save, the system assigns a code and records creator and timestamp — no "v3_final" naming games.

Level 1 — the department manager is notified, opens the request with full context, and clicks Approve or Reject (a reason is mandatory on rejection). Approval moves it to the next level automatically; rejection sends it back with the reason attached — fix and resubmit, instead of guessing. Level 2 — accounting checks budget and documents. Level 3 — the director approves last, for requests above a value threshold. The approved request then grounds ordering, goods receipt and payment; every step has a named owner and a timestamp. In BAMFLOW's projects — as the official NocoBase partner in Vietnam — this is the most requested template, touching three pains at once: duplicate purchases, unapproved purchases, and unaccountable pricing.

NocoBase daily overview: requests and tasks waiting to be processed
NocoBase daily overview: requests and tasks waiting to be processed

Trigger, approval nodes and value-based branching

Technically, a NocoBase workflow for approvals has three parts. The trigger starts the process when a request is created or submitted. Each level is a manual approval node: you designate who approves, what they see, and their actions (Approve / Reject / Return). The request advances only when that human acts; the system never "approves on behalf" of anyone. And conditions branch the route by the request's own data. Illustrative thresholds (each company sets its own): under 10 million VND, manager → accounting; 10–50 million, add a deputy director; above 50 million, the director approves last. Small requests travel fast, large ones carefully — paper cannot reroute itself like that.

Notifications and a complete approval history

In practice, everything depends on one mundane thing: the approver must know something is waiting. When a request reaches a level, the approver is notified in the system (email can be configured too), and every pending item sits in one fixed "waiting for my approval" list — no longer hostage to drifting chat messages. Long-waiting requests can trigger an automatic reminder.

When the process ends, the system keeps the full approval history: who created the request and when, who approved or rejected at each level and at what time, plus rejection reasons and bounce count. Chat gives you messages detached from request status; paper gives a signature but not how long the form sat on each desk. When a dispute arises — late delivery, suspicious pricing, a wrong payment — this history is working evidence, not recollection.

Request and document list on NocoBase: each item shows its approval status and current handler
Request and document list on NocoBase: each item shows its approval status and current handler

Stated plainly: the current limitations

BAMFLOW presents these to every client before implementation, and they belong here too. First, approvers are designated as specific people. In a manual approval step you pick a concrete user account (for example, Tuan — Head of Sales). Selecting approvers flexibly "by role" — whoever currently holds the role approves, following automatically when personnel change — is still limited. When managers rotate, you update the approver in affected workflows — minor for stable teams. Second, the approval screen favours clarity over complex layouts — it shows the key decision information; elaborate multi-table screens may need simplifying. Third, built-in notifications are in-app and email; pushing approvals into external chat tools needs case-by-case integration. The core — sequential manual approvals, branching, clear statuses, full log — works in full; the limits sit in the convenience layer.

One framework, four processes

The best part of building approvals on one platform is reuse. The same pattern — form → approval levels → status plus log — covers nearly every internal document: leave requests (which then feed the timesheet, as detailed in our article on attendance and payroll on NocoBase), cash advances, spending proposals and purchase requests. Only the form, level count and branching rules differ; the rest is one mechanism learned once.

Get the sample diagram: BAMFLOW shares this article's 4-level purchase approval diagram, thresholds included — message us via bamflow.vn.

Build it yourself? Approval workflows and branching conditions are hands-on topics in the NocoBase AI Builder course (12 sessions).

Want it implemented for you? Message BAMFLOW via bamflow.vn for an approval system matched to your company's spending rules.

About BAMFLOW — BAMFLOW is the official NocoBase partner in Vietnam (300+ apps delivered, 150+ business customers, 1,000+ learners).

Đọc bản tiếng Việt RSS