The short answer
Procure-to-pay (P2P) is the supplier-facing spine of a manufacturing business: a shortage — surfaced by MRP, a reorder level, or a requisition raised against a BOM or stock — becomes a Purchase Estimate (PE) and then a Purchase Requisition (PR) that is checked and approved; the PR becomes a Purchase Order (PO); material arrives as a Goods Receipt (GRN) recorded against the PO; receipt inspection dispositions every line; the supplier bill is matched to the GRN and PO before approval; and payment closes the loop, with Tally receiving the purchase voucher automatically.
Unlike the enterprise-finance version of this topic, this guide is written for how an SME factory actually buys — urgent shortages, partial deliveries, rejected material, and an accounts team that lives in Tally. It follows the chain as it runs in Fast ERP's purchase module, and pairs with the quote-to-cash guide covering the sales spine that usually triggers it. Both sit under the pillar, what is ERP software?
The whole chain in one table
| Stage | Document | Gate | What it protects |
|---|---|---|---|
| 1. Demand | Shortage from MRP / reorder / BOM | Plan approval | Buying only what is actually needed |
| 2. Estimate | PE by category (RM, consumables, capital…) | Category budget | Spend visibility before commitment |
| 3. Requisition | PR — checked, then approved | Check + approve | Authorised requirements only |
| 4. Order | PO — released to supplier | Release by authorised role | Agreed rates, taxes and terms on record |
| 5. Receipt | GRN against the PO | Pending = ordered − received | Deliveries reconciled to commitments |
| 6. Inspection | Disposition per line: AC / RJ / AD | Quality gate | Bad material never enters stores |
| 7. Bill | Supplier bill, three-way matched | PO = GRN = bill | Paying only for what arrived, at agreed rates |
| 8. Payment | Payment; Tally purchase voucher | Bill approval | Books in step with operations |
Stage 1 — Where demand comes from
Good purchasing starts before the purchase department: with a reason to buy. In Fast ERP, demand enters the spine three ways. MRP explodes released orders through their BOMs, nets the requirement against stock, and surfaces the shortfall. Reorder levels on the item master trigger requisitions when on-hand falls below the line — which works precisely because the stock ledger is live. And requisitions against a BOM or against stock let planners and stores raise structured requests for specific needs, including replacements for rejected material.
The common property: every requirement arrives with its reason attached — the order, the plan or the level that produced it — so the person approving it can judge it.
Stage 2 — Purchase estimate and requisition
The Purchase Estimate organises intended spend by category — raw material, finished goods, capital, consumables, infrastructure, maintenance, new product development, tooling, services — so different kinds of buying get different scrutiny before anyone is committed. The estimate matures into a Purchase Requisition: the internal document that says what, how much, when and why.
The PR then passes two distinct gates — it is checked (is it complete, sensible, correctly specified?) and approved (is this spend authorised?). Requisition lines can be assigned to purchase executives for sourcing, and pending-PR reports keep the queue visible so approvals do not become the bottleneck. The distinction between PR and PO is the whole control: the PR authorises the need; the PO commits the money.
Stage 3 — The purchase order
The approved requisition becomes a Purchase Order — the external commitment, carrying the supplier from the party master, agreed rates, taxes from the tax configuration, and terms. Like every document in the system it moves draft-to-released, and until an authorised role releases it, nothing is committed (the mechanics are the standard lifecycle described in how ERP software works).
After release, the work is follow-up: PO follow-up screens and pending-PO MIS show what is due, from whom, and how late — and the on-time purchase report turns delivery performance into a fact you can put in front of a supplier at the next negotiation.
Want to see a gated purchase cycle on your own items?
In 30 minutes we run a requisition through approval, order, receipt, inspection and bill matching — with the Tally voucher posted at the end.
Stage 4 — Goods receipt: the GRN against the PO
When the truck arrives, the GRN records what actually came — against the purchase order, line by line. That one discipline does a surprising amount of work: pending quantity is always ordered-minus-received, so partial deliveries accumulate honestly; over-delivery is visible at the gate rather than discovered at stocktake; and the receipt posts the store engine, so stock rises the moment material is admitted, with barcode labels printed for the received lots where labelling is in use.
Receipts can also arrive against an advance shipping notice, and a wrong receipt can be cancelled — with the cancellation on record, like everything else. Either way, the GRN is the document the next two stages hang off: inspection dispositions it, and the supplier bill must match it.
Stage 5 — Receipt inspection: the quality gate
Between the gate and the stores shelf stands quality. Receipt inspection examines each GRN line and dispositions it three ways:
- Accepted (AC) — the line enters stores as usable, lot-tracked stock.
- Rejected (RJ) — the line is excluded from usable stock and drives the rejection flow: a purchase return or a replacement requisition, and, where warranted, an NCR against the supplier with 8D corrective action for repeat offenders.
- Accepted under deviation (AD) — usable, but with the concession recorded, so "we let it through" is a decision with a name and a date, not a shrug.
Inspection MIS accumulates these results into supplier quality history — which, alongside on-time delivery, is the evidence base for rationalising your supplier list.
Stage 6 — The supplier bill and three-way matching
The supplier's invoice is entered as a supplier bill and approved only after the three-way match: does the bill agree with the purchase order (rate, terms) and with the goods receipt (quantity actually received and accepted)? If any leg disagrees — billed more than delivered, rate higher than agreed, billed for rejected material — the bill waits until resolved.
Advances and adjustments are handled against the same chain, so part-payments and debit notes stay reconciled. This single control eliminates the classic quiet losses of SME purchasing: paying twice, paying for shortfalls, and paying old rates nobody checked.
Stage 7 — Payment, and the books that follow
Approved bills flow to payment with follow-up screens keeping due dates visible. And the accounts side is already done: each GRN posted to Tally as a purchase voucher when it happened, payments recorded in the ERP keep the payable picture in step, and GST input data flows from the same documents. Nobody in accounts re-types what stores and purchase already recorded — the operational chain is the accounting source.
Measuring the spine: follow-up screens and MIS
Because every stage is a document with a status, the health of purchasing is readable at any moment: pending PRs (approval bottlenecks), pending POs (supplier delays, with age), GRN and inspection reports (what arrived and what passed), supplier bill reports (what is owed), and the on-time purchase report (who delivers). These are the purchase family of Fast ERP's MIS screens, and together they answer the owner's real question — where is my money and my material right now? — without a single phone call. The benefits guide puts this visibility in the wider context of what an ERP changes.
Where procure-to-pay leaks without an ERP
Run the same cycle on phone calls and spreadsheets and the leaks are predictable: urgent orders placed without approval, at rates nobody recorded; deliveries accepted without checking against the order, so shortfalls surface months later; rejected material drifting into stock because nothing forced a disposition; and bills paid on the supplier's say-so because matching them by hand takes hours nobody has. Each leak is small and invisible; collectively they are one of the largest recoverable costs in an SME factory — and the reason the purchase module usually pays for the ERP first.
The chain in miniature
MRP flags a 200 kg shortfall of bar stock against a released order. A requisition is raised against the BOM, checked by stores and approved by the plant head the same day. The PO goes to the regular supplier at the contracted rate. The truck delivers 180 kg; the GRN records it against the PO, leaving 20 kg pending — visible, not forgotten. Receipt inspection rejects one bundle for surface defects; it is returned, a replacement requisition raised, and the supplier's quality history updated. The bill arrives for 180 kg; the match flags the rejected bundle; the corrected bill is approved and paid; and Tally has carried the purchase voucher since the day the material arrived. Every rupee is accounted for because every stage was a matched document — the flow proven in real deployments of the platform such as Micro India and Nikhtish Engineering.
Frequently asked questions
What is the procure-to-pay process?
Procure-to-pay is the supplier-facing spine of a manufacturing business: a shortage — from MRP, a reorder level, or a requisition raised against a BOM or stock — becomes a purchase estimate and then a purchase requisition that is checked and approved; the requisition becomes a purchase order; material arrives as a goods receipt (GRN) recorded against the PO; receipt inspection accepts, rejects or accepts-under-deviation each line; the supplier bill is matched to the GRN and the PO before approval; and payment closes the loop, with Tally receiving the purchase voucher automatically.
What is the difference between a purchase requisition and a purchase order?
A purchase requisition (PR) is an internal request to buy — it says what is needed, how much and why, and it must be checked and approved before anything is committed. A purchase order (PO) is the external commitment — the document sent to the supplier with agreed rates, taxes and terms. Separating them is the control: spend is authorised at the PR stage, and only approved requirements become orders.
What is three-way matching in procure-to-pay?
Three-way matching compares the purchase order (what was ordered and at what rate), the goods receipt (what actually arrived and was accepted), and the supplier bill (what the supplier is charging) before the bill is approved for payment. If quantity or rate disagrees, the bill waits. It is the single most effective control against paying for goods not received, quantities not delivered, or rates not agreed.
What happens when goods fail receipt inspection?
Each GRN line is dispositioned at receipt inspection: accepted lines enter stores as usable stock; rejected lines are excluded and drive a rejection flow — a purchase return or replacement requisition, and where warranted a non-conformance (NCR) against the supplier; accepted-under-deviation admits material with the concession on record. Rejected material never silently enters stock, and pending quantity against the purchase order stays honest.
How does procure-to-pay post to Tally?
Fast ERP posts each goods receipt to Tally as a purchase voucher, so incoming material hits the books as it hits stores. Supplier payments recorded in the ERP keep the payable picture in step. The accounts team keeps Tally as the book of record, without re-entering what the stores and purchase teams already recorded.