The standard story in Nepal goes like this: a business decides it needs to stop running approvals through WhatsApp and phone calls, asks an IT vendor what it would cost to build something, gets a quote between NPR 3 and 5 lakhs for custom development, and quietly shelves the idea. The process stays manual. The approval bottlenecks stay. The audit trail stays nonexistent.
What most businesses do not know is that modern ERP platforms already include visual workflow builders designed for exactly this purpose. You describe the approval rules - who needs to approve, under what conditions, what happens if they do not respond - and the system enforces them. No developer. No custom code. No NPR 5 lakh project.
This is a step-by-step walkthrough of how to actually build a purchase approval workflow from scratch using the kind of visual configuration tool available inside a modern ERP. The same approach works for payment approvals, leave requests, expense claims, and any other process that currently runs through a combination of memory, WhatsApp, and goodwill.
Map Every Approval That Happens in Your Business Today
Before touching any software, write down every approval that currently exists in your business. Who approves a purchase order? Who releases a vendor payment above NPR 50,000? Who authorises a staff leave request? Who signs off on an expense claim before reimbursement? Who approves a sales discount beyond the standard rate? Who must clear a credit note before it is issued to a customer?
Most Nepal businesses, when they do this exercise, discover between 8 and 15 distinct approval types. They also discover that 70 to 90 percent of them route to the same one or two people. That concentration is both the operational bottleneck and the control gap that a workflow system is designed to address. Without a clear map of what currently exists, you cannot write rules for it - and you will configure a system that handles 60 percent of your real processes while the other 40 percent continue on WhatsApp.
Set the Conditions That Determine Routing
Conditional routing means the system decides who needs to approve based on what the transaction looks like. Amount is the most common condition. A purchase order under NPR 10,000 might need only department head approval. NPR 10,001 to NPR 1,00,000 routes to the finance manager. Above NPR 1,00,000 requires director sign-off. Transaction type is another condition - capital expenditure and vendor payments often warrant different approvers than routine operational purchases.
You can layer conditions. A purchase under NPR 10,000 for IT equipment might route differently than a purchase under NPR 10,000 for office supplies, because IT procurement carries additional evaluation requirements. The visual builder lets you express these combinations as simple if-then rules without writing code - select the condition from a dropdown, set the value, assign the approver.
Most Nepali businesses run all approvals through one senior person regardless of transaction size - the owner's trusted manager, or the owner directly. A NPR 2,000 stationery purchase waits in the same queue as a NPR 20 lakh equipment order. Amount-based routing removes the director from small routine decisions immediately, freeing their attention for transactions that genuinely need that level. When the owner travels for supplier meetings in India or China, or is managing a site in Birgunj, operations no longer stop waiting for a call back.
Assign Approvers by Role, Not by Person Name
This distinction matters more than it appears. If you configure "Ram Shrestha" as the purchase approver, every workflow that references Ram breaks the moment Ram resigns, transfers, or goes on extended leave. Role-based assignment means you assign "Finance Manager" as the approver. Whoever currently holds the Finance Manager role receives approval tasks automatically. Staff changes, promotions, and restructures do not require any workflow reconfiguration.
Role-based assignment also handles acting assignments automatically: when a stand-in Finance Manager covers while the primary is on leave, they inherit the approval responsibilities as soon as the HR record is updated. No manual changes. No approvals sitting in an absent person's inbox while the backup has no idea the task exists.
Keep your role list simple. Four to six roles cover 95 percent of approval scenarios in most Nepal businesses: Director, Finance Manager, Department Head, and Supervisor. Adding more roles creates ambiguity about who to assign to which workflow and increases configuration complexity without adding meaningful control.
Configure Escalation and Delegation Rules
The most operationally valuable part of a workflow system is what happens when nothing happens. If a purchase approval sits unactioned for 24 hours, the system should escalate automatically - either sending a reminder to the same approver or routing up to the next level in the chain. If the primary approver marks themselves as unavailable, pending approvals transfer to a designated backup without anyone needing to send a WhatsApp message to ask who should handle it.
Escalation rules also protect the business from costs that accumulate silently. A vendor payment approved two days late carries a late penalty. A purchase order approved a week late misses the supplier's stock window. These costs appear in bank statements and supplier relationships, not in any approval log. A configured escalation rule keeps the queue moving without adding a manual follow-up burden to anyone in the business.
Test With Real Transactions Before Going Live
Once the workflow is configured, run five to ten real transactions through it in a test environment before announcing it to staff. Watch where it breaks. A purchase order for an item category you did not explicitly configure will fall to the default route - verify that default is correct. Check that escalation fires after the configured time by deliberately leaving an approval unactioned. Confirm that mobile notifications reach the approvers on their phones and that the full transaction detail is visible in the notification.
Pay particular attention to edge cases that will definitely arise in practice: what happens to a purchase that spans two departments? What happens when both the primary and backup approver are simultaneously unavailable? What happens to in-progress approvals when you update a workflow rule? A half-day of careful testing prevents a frustrating first week after go-live - which is precisely the moment when most staff form their lasting opinion of a new system.
Building a no-code approval workflow is not a technical project - it is a business design exercise. The software does not decide who should approve what. You do, through the mapping and condition-setting steps. The platform then enforces those decisions consistently, without relying on anyone's memory, availability, or goodwill.
Requests sent manually, tracked in chat history, no guaranteed response time or format
Transaction routed to the correct approver automatically based on amount and type
No record of who approved, when they approved, or what information they saw before deciding
Every action recorded: approved by, at what time, with any rejection comment attached permanently
Vendors wait, purchases stall, payments delay while everyone waits for one person to respond
Backup approvers receive tasks automatically when primary is marked unavailable or unresponsive
Director approves NPR 2,000 stationery and NPR 20 lakh equipment in the same daily queue
Routine small purchases approved at department level without involving senior management
Any change to who approves what becomes a technical project with a budget and a waiting period
Update approval rules, add conditions, and reassign roles without writing any code
Frequently Asked Questions
No. Visual workflow builders are designed for operations managers, finance managers, and administrators - not developers. Configuration involves selecting conditions from dropdowns, assigning roles, and setting time limits. If you can describe an approval rule in plain language, you can configure it in the system. Technical staff are not required at any stage of the setup or ongoing management process.
Transactions already in an approval queue when you change the rule typically continue on the original path until they are completed or cancelled. New transactions follow the updated rule from that point. The exact behaviour depends on your platform, so test any rule change in a non-production environment before applying it during a busy period such as month-end or the Ashadh fiscal year close.
Yes. Conditional routing lets you set department as one of the routing conditions alongside amount and transaction type. A purchase requisition from the construction department might route to the site engineer first, then procurement manager, then director for amounts above a threshold. A purchase from HR might go directly to the finance manager. You define separate chains for each department and transaction-type combination that warrants it.
Approval Workflows Configured by You, Not by Developers
MISAC's approval system covers every transaction type - purchase orders, vendor payments, journal vouchers, leave requests, expense claims, and project tasks - from a single configuration panel. Rules are defined by your operations or finance manager through the admin interface. Amount thresholds, transaction categories, department routing, and escalation timers are all set without any developer involvement. When a rule needs updating, the manager updates it. No IT ticket, no project, no waiting period.
For businesses where the approving director is frequently away from the office - travelling between branches, visiting suppliers in Birgunj or across the border, or managing a project site - MISAC's mobile app delivers every approval request to their phone with full transaction detail. They review, comment, and approve or reject with one tap. The response timestamp and any comment attach permanently to the transaction. If they are unavailable, the configured escalation rule fires and routes to the backup approver automatically.
The businesses we work with at MISAC Intelligence Pvt. Ltd. typically start with purchase approval - the workflow with the most direct impact on vendor relationships and cash flow - and add payment approval and leave management within the first month. Each workflow takes a few hours to map, configure, and test. The time recovered from WhatsApp follow-ups and manual approval queues shows up in the first week of operation.
Ready to See MISAC in Action?
See how MISAC configures a purchase approval chain specific to your business structure - no developer, no project cost.