Keep a purchase request, approval and supplier order distinct, with clear scope, authority and a reviewed route for exceptions.
A supervisor asks for materials, a staff member messages the supplier and the owner later discovers that the order has already been placed. The material may be genuinely needed, but the business has lost the chance to review quantity, timing and the financial commitment before agreeing to it.
A purchase approval workflow makes the decision visible before the supplier order. It should help people buy what is needed without turning every routine purchase into an unexplained delay.
This article proposes an operational control for a hypothetical Nepal manufacturer and distributor. Approval amounts are illustrative company-policy choices, not statutory limits or Nepal tax rules.
Separate the request from the commitment
A request explains the need. An approval authorises a defined purchase under the business’s rules. A supplier order communicates the actual commitment. These records can be linked without pretending they are the same event.
Ask the requester to identify the item or specification, quantity, required date, destination and reason. If the material relates to a production job, include the relevant job and approved specification reference. A message saying “buy the usual materials” leaves too much room for interpretation.
Check existing usable stock and outstanding orders before buying. A purchasing request should not become a duplicate supplier order simply because two departments notice the same shortage.
Hypothetical purchase review: approve the defined scope before committing to a supplier.
Approve a defined scope
The approver needs enough information to decide. Record the supplier or sourcing assumption, included charges, proposed quantity and the cost basis. Clarify whether the value is an estimate or a supplier quotation and which changes require renewed review.
ERPNext’s Workflows documentation illustrates configured approval states and transitions. The broader lesson is to make the route and authority explicit. Its example conditions are vendor implementation references, not a ready-made approval policy for your business.
| Stage |
Decision or evidence |
| Request |
Need, specification, quantity, date and destination |
| Review |
Existing stock, open orders and proposed cost basis |
| Approval |
Authorised scope and actual approving role |
| Supplier order |
Order matches approval and retains its reference |
| Receiving and payment |
Separate evidence and approvals |
Conceptual artwork: an approval gate comes before the supplier commitment.
Use a simple hypothetical approval example
A workshop requests forty units of a component at NPR 800 each, giving NPR 32,000. Delivery is quoted at NPR 2,000. The illustrative amount reviewed is therefore NPR 34,000 before any excluded charges.
Hypothetical purchase-approval panel uses the article’s NPR 34,000 example and an illustrative internal threshold. It is not a statutory limit or a live WorkSphere screen.
Assume the company’s own policy requires a second approval for the specified reviewed amount above NPR 30,000. The request needs that approval under the example policy. The threshold is not a legal requirement, and a business must define whether its actual control includes taxes, freight and other charges.
Do not split the same intended purchase into two smaller requests merely to avoid the authorised route. If the supplier changes the quantity or price, compare the change with the actual approval scope rather than assuming the earlier approval covers everything.
Use the company rule, not an invented legal threshold; review second approvals above policy limits.
Make changes and urgent exceptions traceable
A shortage may need urgent action. Define who may authorise an exception, what minimum evidence is required and how the decision is reviewed afterward. Urgency should not mean that nobody records who accepted the commitment.
If an approver is away, use an approved delegation arrangement. Keep the substitute’s authority visible and avoid asking a requester to approve their own request merely because the normal route is inconvenient.
Give rejected and returned requests an understandable reason. “Needs specification” and “not approved” call for different next actions. A request can be revised without deleting the fact that an earlier version was reviewed.
Changes need a scope check: compare modifications against the originally approved authority.
Link approval to the order that is actually sent
Before sending the order, confirm that its item, supplier, quantity, amount basis and delivery conditions match the approved scope. Record the approval reference on the purchase order or equivalent authorised record.
Once the order is sent, keep acknowledgement and changes under control. A supplier’s revised delivery date may affect production or a customer promise, but it should not silently rewrite the approval history.
For a manufacturing workflow, the request might link to a production job; Inventory might show usable stock and receipts; Accounting might review the commitment basis; and Tasks might hold missing information. These are proposed WorkSphere connections requiring design and verification, not claims of live functionality.
Approval does not prove receipt or payment: maintain distinct operational records.
Hypothetical delivery review: receiving evidence remains separate from purchase approval.
Keep receiving and payment checks separate
Purchase approval does not prove that goods arrived, that they were acceptable or that the supplier invoice is correct. Receiving should retain its own quantity and condition evidence. Accounts should follow the approved invoice and payment process.
Avoid treating a completed approval task as a financial posting or a physical receipt. A clear workflow explains the next authorised event instead of triggering unrelated records because one checkbox changed.
Review a small set of exceptions periodically: purchases sent without an approval reference, orders changed after approval, requests waiting without an owner and urgent purchases without a recorded reason. Use the findings to improve the route, not simply to add another signature.