Every payment your business makes to a supplier started somewhere - a staff member who needed something, a manager who approved it, a supplier who delivered it. In most Nepali businesses, that journey is a chain of phone calls, WhatsApp messages, handwritten notes, and paper files. Each step involves someone re-entering information that was already recorded somewhere else. The purchase-to-payment cycle is where procurement errors are born.
The gap between knowing you have a procurement problem and understanding what the solution actually looks like is wider than most finance managers expect. It is not just about buying software. A well-designed purchase-to-payment workflow changes how decisions are made at every step - from who can request what, to who approves how much, to which invoices get paid when.
This guide follows a single purchase request from the moment a department head identifies a need through to the moment a supplier receives payment - showing at each stage what automation replaces and what it adds.
Raise a Purchase Requisition
The process begins when someone in the organization identifies a need - a store needs packing material, an accountant needs a new laptop, a construction site needs 200 bags of cement. In a manual system, this is communicated verbally or via WhatsApp and lands in the purchase manager's memory. In an automated workflow, the department head raises a digital purchase requisition that captures: what is needed, quantity, estimated price, required date, and the cost center the expense belongs to. The system links the requisition to that department's budget. If the requested amount exceeds the available budget balance, the system flags it before anyone approves anything. Every requisition has a unique number, a timestamp, and an originator - details that paper-based systems can never guarantee.
Approve the Requisition Through a Multi-Level Workflow
Once submitted, the requisition routes automatically to the designated approver - typically the department manager for amounts below a threshold, the CFO or MD for amounts above it. The approver receives a notification on their phone. They review the request, approve or reject with a written reason, and the originator is notified immediately. No one needs to follow up by phone. No request disappears into someone's inbox. The approval history is permanently recorded with user, timestamp, and decision - this becomes part of the audit trail for every payment eventually made against this requisition.
Nepali businesses frequently make advance payments to suppliers before goods arrive - particularly for imported goods with LC requirements or seasonal inventory builds. In a manual system, advance payments are the highest-risk transaction category because they happen before any goods receipt. An automated workflow requires the advance to be linked to an approved purchase order before any payment can be initiated, making unauthorized advances visible and traceable. Similarly, PDC (post-dated cheque) payments to suppliers can be scheduled against approved POs so that cash flow planning reflects future commitments accurately.
Generate the Purchase Order
With the requisition approved, the purchase team converts it to a formal Purchase Order. In an automated system, this conversion carries over all the details from the requisition - quantity, estimated price, cost center - and the purchase officer fills in the supplier name, agreed unit price, delivery terms, and payment terms. The PO is auto-numbered, dated, and linked back to the original requisition. Supplier terms such as credit days and payment method are pulled from the supplier master automatically. The issued PO can be sent to the supplier by email directly from the system. The moment a PO is issued, the committed expenditure appears in the budget report as an open commitment - the finance team can see that rū 85,000 is committed to a supplier even before goods have arrived or an invoice has been received.
PO commitment accounting is one of the most overlooked benefits of a P2P system. When your budget report shows only actual expenses and not open PO commitments, you are working with incomplete numbers. A department might appear to have rū 2 lakh available when four pending POs have already committed rū 1.8 lakh of it. Commitment reporting closes this gap and prevents over-spending before it happens.
Receive Goods and Record the GRN
When goods arrive at the warehouse or site, the store keeper or receiving staff records a Goods Receipt Note directly against the open PO. They enter what was actually delivered - item by item, with quantities. The system immediately highlights any variance between what was ordered and what arrived. If 200 bags of cement were ordered and 185 were delivered, the variance is flagged. The GRN is accepted, but the open quantity of 15 bags remains on the PO as a pending delivery. The inventory count updates in real time - goods are now in stock the moment the GRN is saved. The accounting entry for goods receipt posts automatically to the asset or expense account, depending on item type. No separate posting step is required.
Match the Supplier Invoice to PO and GRN
When the supplier's invoice arrives, it is entered into the system against the relevant PO. The three-way match runs automatically: the system compares the invoice quantity and price to the PO and the GRN. If the supplier invoiced for 200 bags at the agreed price but only 185 were received, the system flags the discrepancy before any payment is processed. The finance team can choose to pay only for the 185 bags delivered and hold the balance, or request a credit note. When all three documents match within the accepted tolerance, the invoice is cleared for payment and the payables entry is posted to the supplier's account. This single step eliminates the most common cause of supplier overpayment in Nepali businesses.
Release Supplier Payment
With the invoice matched and approved, the payment is scheduled according to the credit terms. The payment can be initiated through a payment voucher that carries forward all supplier details, account numbers, and bank information from the supplier master. Multi-level payment authorization requires a second approver for amounts above a set threshold. The authorized payment generates the journal entry automatically - crediting the bank account and debiting the supplier payable. Bank reconciliation entries update as the payment clears. The supplier's account statement reflects the payment immediately, and the outstanding payables balance reduces accordingly. The entire journey from purchase request to payment is documented, linked, and traceable in a single audit trail.
A complete P2P workflow does not just speed up procurement - it closes the control gaps that allow unauthorized spending, duplicate payments, and supplier overbilling to happen quietly. Every rupee committed starts with an approved requisition and ends with a matched invoice. The audit trail writes itself.
No record, no cost center link, no budget check before buying decisions are made.
Every request tied to a cost center and budget balance - over-spend flagged before approval.
No record of who approved what amount or when - disputes resolved by recollection.
Approver notified on phone, decision recorded with timestamp and reason. Permanently traceable.
PO not linked to requisition, no committed spend visibility in budget reports.
Committed spend appears in budget immediately. Supplier receives PO directly from system.
Delivery variances go unrecorded. Partial deliveries accepted without flagging open balance.
Actual received quantity auto-compared to ordered quantity. Open balances tracked until fully delivered.
Suppliers paid for quantities never received. Duplicate invoices processed without detection.
Invoice cannot be paid unless it matches both the PO and the GRN within tolerance. Overbilling blocked.
Frequently Asked Questions
The purchase-to-payment process covers every step from identifying a procurement need to making the final supplier payment. It includes: purchase requisition, approval, purchase order issuance, goods receipt, invoice matching, and payment release. An automated P2P system links all these steps in one workflow so that every payment can be traced back to an approved need and a verified goods receipt.
Mobile ERP allows managers and directors to approve purchase requisitions, POs, and payments directly from their phones - without being at the office. In Nepali businesses where senior approvers often travel between sites or branches, waiting for an in-person signature delays the entire procurement cycle. A mobile approval workflow sends notifications, displays the request details, and records the approval decision with timestamp - keeping the P2P cycle moving regardless of the approver's location.
An automated P2P workflow prevents unauthorized payments through several linked controls. First, every payment must trace back to an approved purchase order - no PO means no payment can be processed. Second, the three-way match check verifies that the invoice matches both the PO quantity and price and the GRN quantity before payment is cleared. Third, payment amounts above a threshold require a second-level authorization. Fourth, every step - requisition, approval, GRN, invoice match, payment - is recorded in the audit trail with user identity and timestamp. These controls collectively make it very difficult to process a payment for goods that were not ordered and received through proper channels.
Complete P2P Automation Built on Accounting-First Architecture
MISAC's purchase-to-payment workflow is built on an accounting-first foundation - meaning every step in the procurement cycle automatically generates the correct accounting entry. When a GRN is saved, the inventory and liability accounts post automatically. When a three-way matched invoice is approved, the payables entry is created. When a payment is authorized, the bank and payables entries both post in one action. There is no separate posting step, no end-of-month journal catch-up, and no reconciliation gap between the procurement module and the accounting module.
The mobile ERP capability means the P2P workflow does not pause because an approver is on-site in Hetauda or at a branch in Biratnagar. Purchase requisitions, PO approvals, and payment authorizations all work on the MISAC Android and iOS app with the same user and permission controls as the desktop. GPS-verified and timestamped approval records give the finance team and auditors a complete mobile audit trail. Advance payments to suppliers for LC-linked imports can be raised, approved, and scheduled through the same workflow, with open commitment automatically reflected in the payables aging and cash flow forecast.
Businesses working with us across Nepal's trading, construction, and import sectors tell us the biggest change after automating P2P is not speed - it is visibility. Management can see every open requisition, every pending PO, every unmatched invoice, and every overdue supplier payment on one dashboard. That visibility changes how procurement decisions get made. MISAC Intelligence Pvt. Ltd. builds that visibility into every module from day one.
Ready to See MISAC in Action?
See how MISAC's P2P workflow handles the full procurement cycle - from digital requisition to supplier payment - for a trading or construction business like yours.