Procurement Process: 7 Phases from Requisition to Payment
The seven phases from identifying the need to payment
The procurement process covers every step a company takes to obtain goods and services: identifying the need, purchase requisition, approval, purchase order, goods receipt, invoice verification and payment. Business departments, purchasing, goods receiving and accounts payable are involved. The goal is to meet each need on time, at agreed terms and in line with internal rules.
- Identifying the need and requisition
- Approval and purchase order
- Goods receipt and invoice verification
- Payment
What Is a Procurement Process?
A procurement process is the defined sequence through which a company obtains goods and services, from the first need to the paid invoice. It consists of seven phases: identifying the need, purchase requisition, approval, purchase order, goods receipt, invoice verification and payment. In the broader sense it also includes supplier selection and contracts, which precede the individual need.
Last updated:
The 7 Phases of the Procurement Process
The phases build on each other: each one produces a document or a decision that the next one relies on.
Identifying the need
A department finds that it needs a product or service, such as lab supplies, spare parts or external consulting. It clarifies quantity, date and quality and checks whether a catalog item or framework agreement exists. For stock material, materials planning often handles this step automatically.
Indirect procurement: demand outside productionPurchase requisition
The need is recorded as a purchase requisition with quantity, delivery date, delivery location, account assignment and price or estimated price. The requisition is an internal document and does not yet commit the company to the supplier.
Purchase requisition: fields, process and requisitions in SAPApproval
Depending on value, cost center and material group, managers, budget owners or purchasing approve the requisition, in several levels for higher amounts. The approval matrix defines who may approve up to which amount.
Approval matrix: structure and example with value limitsPurchase order (catalog, punchout or free text)
The approved requisition becomes the purchase order, the binding order to the supplier. If the item comes from a catalog or punchout shop, supplier, price and material group are already fixed. For a free-text order, purchasing assigns the source of supply and price first, often after a request for quotation.
Punchout catalog: shop at the supplier, approve in your own systemGoods receipt
The delivery is accepted, checked for quantity and condition and posted with reference to the purchase order. For services, the department confirms the service rendered instead.
Invoice verification
Accounts payable matches the supplier invoice against purchase order and goods receipt. If quantity and price agree, the invoice is released for payment; discrepancies go to purchasing or the department for clarification.
Audit trail: documenting documents and decisions traceablyPayment
The invoice is paid according to the agreed payment terms, ideally within the cash discount period if one applies. Posting the payment completes the transaction.
Purchase-to-pay: the operational process up to the paid invoice
How many phases are named depends on the source. Some combine identifying the need and the requisition, or count supplier selection as a separate phase. The sequence stays the same.
Procurement Process, Purchasing Process and Purchase-to-Pay
In everyday use the terms are often treated as synonyms. Strictly speaking, they differ in scope and perspective.
| Term | Scope | Involved |
|---|---|---|
| Procurement process | All steps from identifying the need to payment, in the broader sense including supplier selection and contracts | Business departments, purchasing, goods receiving, accounts payable |
| Purchasing process | The tasks of the purchasing department: request for quotation, bid comparison, negotiation and purchase order | Purchasing |
| Purchase-to-pay (P2P) | The operational sequence from purchase requisition to paid invoice, usually seen from a process and system perspective | Requesters, operational purchasing, accounts payable |
| Source-to-pay (S2P) | Purchase-to-pay plus strategic sourcing: tendering, supplier selection, contract | Additionally strategic purchasing and supplier management |
Typical Weak Spots and How Software Helps
Most delays occur in the early phases, between need and purchase order, especially in indirect procurement with many small orders from all departments. Three weak spots appear in almost every company.
- Maverick buying: departments order directly from the supplier, bypassing the process, because the official route is too cumbersome. Negotiated terms and approvals then do not apply. Software helps when the right item is faster to find in the catalog than in the supplier's web shop and free-text needs also run through requisition and approval.
- Media breaks: needs arrive by email, phone or spreadsheet and are entered a second time in the ERP. Every transfer costs time and creates errors that often only surface during invoice verification. Software helps when the need is recorded once and travels from shopping cart to purchase order into the ERP via an interface.
- Slow approvals: requisitions sit idle because it is unclear who is responsible or because that person is absent. Software helps with an approval matrix of clear value limits, substitution rules and a status the requester can see at any time.
Which solution fits depends on where most transactions get stuck in your own company. Selecting software therefore starts with your own procurement process, not with a feature list.
Related Terms and Matching Ovenca Modules
- Purchase requisition
The document with which the procurement process formally begins.
- Approval matrix
Who may approve a requisition up to which value.
- Free-text order
Ordering without a catalog item and what can go wrong.
- Purchase-to-pay
The operational part of the procurement process from a process and system perspective.
- Maverick buying
Purchasing that bypasses the process and how to reduce it.
- Catalog Shop
Capture needs from catalogs, punchout shops and as free text in one shopping cart.
Three Levers for a Lean Procurement Process
What speeds up the early phases and pays off all the way to the invoice
Capture needs where they arise
When requesters assemble their requisition themselves from an approved catalog, coordination by email is no longer needed. The requisition contains item, price and supplier before purchasing sees it.
- Catalog instead of free text
- Complete requisition the first time
- Fewer queries from purchasing
Rules instead of case-by-case decisions
An approval matrix defines who approves up to which value. Requisitions reach the responsible people directly, and low values do not have to pass through the same levels as high ones.
- Value limits by cost center and material group
- Substitution during absence
- Traceable decisions
Record once, use throughout
The requisition data flows into purchase order, goods receipt and invoice without being entered again. Only then can the invoice later be checked against purchase order and goods receipt without anyone having to search.
- Interface to the ERP
- Order reference up to the invoice
- No duplicate entry
Which Phases Ovenca Covers
Ovenca supports the early phases of the procurement process before the ERP: identifying the need, purchase requisition and approval up to the handover to the ERP. Purchase order, goods receipt, invoice verification and payment remain in the ERP.
- Identifying the need in the Catalog Shop
- Requesters search across all approved catalogs and punchout catalogs and place catalog, punchout and free-text items in one shared shopping cart.
- Purchase requisition and approval
- The shopping cart becomes the purchase requisition. It runs through multi-level approvals by value, cost center or category.
- Handover to the ERP
- Ovenca hands approved shopping carts, purchase requisitions or purchase orders to the ERP via OCI, cXML or API, without re-entry.
- What stays in the ERP
- The ERP remains the leading system for purchase order, goods receipt, invoice verification and payment. Invoice receipt, invoice verification and payment processing are not part of Ovenca.
Procurement Process: Questions and Answers
A procurement process is the defined sequence through which a company obtains goods and services. It runs from identifying the need through purchase requisition, approval and purchase order to goods receipt, invoice verification and payment. Business departments, purchasing, goods receiving and accounts payable are involved.
A common division has seven phases: identifying the need, purchase requisition, approval, purchase order, goods receipt, invoice verification and payment. Some sources combine phases or add supplier selection as a separate phase. The sequence is the same everywhere.
The procurement process is the broader term: it runs from identifying the need in the department to paying the invoice and includes goods receiving and accounting. The purchasing process covers the tasks of the purchasing department, namely request for quotation, bid comparison, negotiation and purchase order. In everyday use both terms are often treated as synonyms.
That depends mainly on the type of order. A low-value catalog item with single-level approval can be ordered on the same day. Free-text orders with a request for quotation and multi-level approval tend to take days to weeks, capital investments with a tender often months. Most time is usually lost to queries and pending approvals, not to delivery.
Related pages
Where Does Your Procurement Process Get Stuck?
In a conversation, we walk through your phases from the request to the handover to the ERP and tell you openly which parts Ovenca takes over and which remain in the ERP.