When a procurement officer says the new system is too complicated, takes too long, or is not compatible with how vendors work in Nepal, those concerns deserve a serious response. Most of them contain a real operational point. Counter operations in Nepal's physical markets - Asan hardware, Kalimati wholesale, Birgunj import - involve relationships and negotiations that are genuinely difficult to fit into a structured digital workflow.
But procurement resistance is worth examining more carefully than other departments, because the environment that procurement teams are most reluctant to leave behind is also the one with the most financial exposure for the business. An informal procurement process - where vendor selection, pricing, and quantity recording all happen through personal relationships and paper documents - leaves certain things difficult to verify from the outside.
This is not an accusation of any individual. It is a description of what uncontrolled procurement environments structurally allow, and why that matters for the business owner who is considering whether to push through resistance or accommodate it.
What Procurement Resistance Looks Like in Practice
Procurement resistance is typically more operationally articulate than other forms of ERP resistance. The procurement officer can explain specifically why the system does not work: the vendor gives a handwritten invoice that does not match the purchase order format; the quantity received was different from what was ordered because the supplier ran short; the price changed between the PO date and delivery because of market movement. These are real scenarios in Nepal's trading environment.
The resistance pattern to watch for is whether these operational realities are raised as problems to configure around, or as reasons why the entire system is unworkable. A vendor who gives handwritten invoices is a data entry task, not a system problem - the quantities and amounts still need to be recorded somewhere, and recording them in the ERP takes the same time as recording them in a register. A quantity shortfall at delivery is handled through a GRN that records what was actually received against what was ordered - that function exists in every ERP for exactly this reason. When these standard situations are presented as system incompatibilities, the objection is probably not about the operational challenge.
Operational complexity in procurement is real and the system should be configured to handle it. The distinction worth making: does the procurement team raise operational challenges as things to solve, or as reasons the system cannot work? The former is implementation work. The latter is a different conversation.
What a Loose Procurement System Allows
When there is no price history on record, there is no baseline against which to evaluate whether a new vendor quote represents fair market value. A purchase negotiated at NPR 120 per unit when the market rate is NPR 95 is difficult to identify without a comparison point. In a system with a price history log, the same vendor's previous transactions appear automatically when a new purchase order is raised - and any significant variation from historical pricing surfaces as a visible discrepancy.
When there is no requirement for a goods received note (GRN) to match the purchase order before an invoice is approved for payment, the quantity recorded as received can differ from the quantity physically received without creating an automatic alert. The difference between 100 bags ordered and 92 bags received is visible to the person who recorded the GRN. It is not visible to anyone else unless they specifically investigate the transaction. A system that requires GRN-to-PO quantity matching before payment can proceed makes any discrepancy a step that requires explanation rather than a matter of routine discretion.
Nepal's physical trading markets in Kathmandu (Asan, New Road, Kalimati), Birgunj, and Biratnagar operate through long-standing vendor relationships that carry real commercial value. A procurement officer who has cultivated a supplier relationship over five years has access to better credit terms, priority on scarce stock, and genuine market intelligence. These relationships are worth preserving and the system should support, not undermine, them. The issue is not vendor relationships - it is whether purchasing decisions can be reviewed independently of the person who made them. A vendor comparison log records which suppliers were considered and at what price before a decision was made. It does not remove the procurement officer's discretion; it makes that discretion visible to management.
Vendor master management is another area where informal procurement systems create gaps. When a new vendor is added to the system without verification - without checking that the bank account number matches the business name, without confirming the PAN registration - the first payment to that vendor creates an unverifiable obligation. In controlled procurement, new vendor registration requires a separate authorization step, and any change to a vendor's bank account details triggers an independent review before the next payment proceeds.
The three controls that change the most about informal procurement are price history (what was paid before), GRN matching (what was actually received), and vendor comparison logs (who else was considered). Each of these makes something visible that was previously invisible only to the procurement team.
What Controlled Procurement Makes Traceable
A structured procurement process creates a paper trail from requisition to payment: the purchase requirement is documented, the vendor selection is logged alongside alternatives considered, the order is placed at a recorded price, the delivery is confirmed against the order, the invoice is matched against the GRN, and the payment is released only after each preceding step is complete. Each of these steps creates a record that can be reviewed independently of the person who performed it.
For the business owner reviewing the month's purchases, a controlled process answers questions that an informal process cannot: which vendors received payments above their historical pricing range, which purchase orders had delivery shortfalls, which orders bypassed the standard approval chain. In a manual system, answering any of these questions requires asking the procurement team directly - which makes the question answerable only by the person being asked about. In a system with a full procurement trail, the data is available without asking.
Vendor master deduplication is a practical starting point for procurement controls. In most Nepal businesses running manual vendor records, the same supplier appears under multiple names - "ABC Enterprises," "ABC Enterprise," "A B C Pvt Ltd" - sometimes with different bank account numbers attached to each variant. Consolidating the vendor master before ERP go-live, with one verified record per supplier, eliminates a structural gap before it moves into the digital system.
Three-way matching - purchase order, goods received note, and supplier invoice all reconciling to the same quantities and amounts - is the single most effective procurement control available. It is also the control that informal procurement processes most structurally resist, because it removes the ability to approve payment for goods that were not fully received or at prices not fully verified. Its implementation should be non-negotiable for any business where procurement represents a significant portion of outgoing cash.
Three-way matching - PO, GRN, and invoice all reconciling before payment - is the most effective procurement control and the one informal systems resist most. Its implementation answers, from the record, whether what was paid for was actually received at the agreed price.
How to Implement Controls Without Breaking Vendor Relationships
The argument that digital procurement controls will damage vendor relationships deserves a direct response: good vendors - those who deliver what they promise at the prices they quoted - have nothing to fear from a structured process. Controls make it harder to do business with vendors who deliver short, invoice above the agreed price, or provide goods that do not match the specification. Those vendors are the ones whose relationship is worth reconsidering regardless of how long it has existed.
The practical transition approach is to start with documentation before enforcement. In the first month, require that all purchases be entered into the system but do not hold payment on matching failures. This establishes the data baseline - how often do deliveries match orders, how often do invoices match the GRN, which vendors have consistent pricing and which do not. After a month of data, the pattern is visible. Enforcement then starts from a position of evidence rather than assumption.
The procurement team's operational expertise is genuinely valuable. They know which vendors are reliable and which are not, which market conditions drive price changes, which relationships need handling with care. The transition goal is to keep that expertise while adding the verification layer that makes it independently reviewable. These two things are not in conflict - they just feel that way during the transition period.
Start with documentation before enforcement. A month of data tells you exactly where the gaps are and which vendor relationships have the most discrepancy history. Enforcement that starts from evidence is easier to explain and harder to argue with than enforcement that starts from policy alone.
No baseline to evaluate whether a new quote is within range - comparison requires asking the procurement team
Previous prices paid to the same vendor appear automatically when a new order is raised
Quantity discrepancies between what was ordered and what arrived are recorded by the same person who received the goods
PO, GRN, and invoice must reconcile - discrepancies surface as exceptions requiring explanation before payment proceeds
Sole-sourcing is invisible - no record of whether alternatives were considered before a vendor was selected
Which vendors were considered, at what price, and why one was selected - logged on every purchase
Bank account details and PAN registration unverified - first payment creates unverifiable obligation
New vendors and bank account changes require separate approval before any payment is processed
Reviewing a purchase requires asking the person who made it - with no independent data to verify the answer
Every step from requisition to payment available to management without routing through the procurement team
Frequently Asked Questions
Manual entry resolves this. The vendor's handwritten invoice is scanned and attached to the GRN in the system; the procurement staff enters the quantities and amounts manually. This takes the same time as entering them in a register, with the difference that the data is now in a searchable, auditable system rather than a paper file. Nepal's informal market vendors are not going to change their invoicing practices for your ERP - but your ERP should handle their invoices as source documents, not obstacles.
Through a price variance approval step. When the invoice price differs from the PO price, the system flags the difference and routes it to a designated approver - typically the finance manager or procurement manager - before the invoice is cleared for payment. The approver reviews the variance, confirms the reason (market movement, supply shortage, forex change), and approves or rejects. This makes price changes a documented decision rather than a silent adjustment. The variance history over time also shows which vendors have the most unpredictable pricing.
Not necessarily for every purchase. Set a threshold - for purchases above NPR 50,000, for example, require documented evidence of at least two vendors considered. Below the threshold, a preferred vendor list with verified pricing is sufficient. The key is that the policy is documented, consistently applied, and visible in the procurement record. This is materially different from an informal arrangement where the threshold is the procurement officer's judgment on any given day.
Procurement Controls That Close Gaps Without Stopping Operations
MISAC's procurement module runs the complete purchase cycle: requisition, purchase order, goods received note, and supplier invoice - with three-way matching enforced before payment release. Every step auto-posts the corresponding accounting entry, so the financial record of every purchase is complete from the moment the GRN is saved. Price variance alerts surface when an invoice differs from the PO, routing to the designated approver automatically. No manual reconciliation between purchase records and accounting records at month-end.
The vendor master in MISAC includes a bank account verification step - any change to vendor banking details requires a separate authorization before the updated details become active for payment. New vendor registration follows a configurable approval chain. The price history for every vendor is visible at the point of raising a new purchase order, without any report generation or query. This does not require the procurement team to behave differently - it requires the system to capture what they are already doing and make it visible to management simultaneously.
MISAC Intelligence Pvt. Ltd. has implemented procurement controls across Nepal businesses in trading, construction, manufacturing, and import sectors. The consistent finding across those implementations: the businesses with the most initial procurement resistance also had the most meaningful variance discoveries in the first three months of controlled operation. The controls did not create the variances - they made existing patterns visible for the first time.
Ready to See MISAC in Action?
Talk to us about how to configure procurement controls for your specific vendor mix and purchase patterns in Nepal.