What Is eProcurement? Process and Rollout Guide
What is eProcurement?
eProcurement means using software to run company buying, from the purchase request through approval, purchase order, goods receipt, invoice and payment. Many companies also include sourcing steps, such as RFQs and reverse auctions. The aim is to make buying faster, keep it within agreed rules and prices, and leave a clear record of every step.
eProcurement is mainly a change in how people work, not just new software. The system only helps if users raise requests in it, approvers approve in it, and suppliers receive orders and send invoices through it.
Short answer. The eProcurement process has six steps:
- A user raises a purchase request
- The request is approved according to value limits
- If there is no contract, the item is sourced through an RFQ, RFP or reverse auction
- A purchase order is sent to the supplier
- Goods or services are received and recorded
- The invoice is matched to the order and the receipt, and then paid
Key takeaways
| Topic | Key point |
|---|---|
| Scope | eProcurement covers buying from request to payment. eSourcing covers choosing the supplier and agreeing the price |
| Control | Approval limits and contract prices are applied every time, not only when someone remembers |
| Payment | Matching invoice, order and receipt stops payment for wrong or duplicate invoices |
| Adoption | Most projects fail because people go around the system, not because of the software |
| Suppliers | Key suppliers must be onboarded before go-live, or orders end up back on email |
| Measure | Track the share of spend that goes through the system each month |
What is the difference between eProcurement and eSourcing?
The two terms are often mixed up. The simplest way to separate them is by the contract. eSourcing happens before the price is agreed. eProcurement happens after.
| eSourcing | eProcurement | |
|---|---|---|
| Main question | Which supplier, at what price? | How do we buy from that supplier correctly? |
| Typical steps | RFI, RFQ, RFP, reverse auction, award | Request, approval, purchase order, receipt, invoice, payment |
| Main users | Buyers and category managers | Everyone who buys, plus approvers, stores and accounts |
| How often | Once per category or contract | Every day, for every purchase |
| Main benefit | A better price and better supplier choice | That price is actually paid, under the right rules |
The two depend on each other. A good price agreed through eSourcing is wasted if users then buy from other suppliers at other prices. eProcurement is what makes the agreed price stick.
What are the main parts of an eProcurement system?
| Part | What it does | What happens without it |
|---|---|---|
| Purchase requests and approvals | Users ask to buy, and the request goes to the right approver by value and category | Requests come by email and phone, and nobody can see what is pending |
| Catalogues | Users pick items at agreed contract prices | Users buy from any supplier at any price |
| Purchase orders | A formal order is sent to the supplier with price, quantity and terms | The supplier delivers against a phone call, and disputes follow |
| Goods receipt | Stores or the user record what actually arrived | Invoices are paid for goods that never came |
| Invoice matching | The invoice is checked against the order and the receipt | Wrong prices and duplicate invoices get paid |
| Supplier portal | Suppliers receive orders, confirm them and submit invoices | Every order and invoice has to be handled by email |
| Sourcing | RFIs, RFQs, RFPs and reverse auctions to choose suppliers | Prices are agreed in private emails with no clear record |
| Reports | Spend by supplier, category and site | Nobody knows how much is spent outside contracts |
How does the eProcurement process work, step by step?
1. Raise a purchase request
The user raises a request in the system, ideally by choosing an item from a catalogue. If the item is not in a catalogue, the user describes what is needed. A clear description here saves time later. A vague request leads to back-and-forth with the buyer.
2. Approve the request
The request goes to approvers based on its value and category. Keep the approval chain short. Each extra approval step adds days. If small requests need three approvals, users will split orders to stay under limits, or buy outside the system.
3. Source the item if there is no contract
If no contract or catalogue price exists, the buyer runs a sourcing event. This is the eSourcing part: an RFQ for clear specifications, an RFP for complex needs, and a reverse auction as the final negotiation step when the specification is fixed and several qualified suppliers are bidding.
4. Send the purchase order
The system creates a purchase order with the agreed price, quantity, delivery date and terms, and sends it to the supplier. The supplier confirms it. The purchase order is the document that later lets accounts check the invoice.
5. Record the goods receipt
When goods arrive, or a service is completed, stores or the user records it. Do this on the day it happens. Late receipts hold up payment, and suppliers then chase the buyer instead of accounts.
6. Match the invoice and pay
Accounts checks that the invoice, the purchase order and the goods receipt agree on item, quantity and price. This is called three-way matching. If they agree, the invoice is paid on the agreed terms. If not, the difference is sent back to the buyer or the supplier to fix.
In India, a supplier with aggregate turnover above ₹5 crore must issue GST e-invoices from 1 August 2023 (Tally). Your system should check that these invoices carry a valid invoice reference number before payment.
For the full cycle, see our guide to the procure-to-pay process.
What are the benefits of eProcurement?
- Contract prices are actually used. Users buy from catalogues at the agreed price, not from any supplier at any price.
- Approval rules are applied every time. The system routes each request by value and category. Nobody can skip a step without it being recorded.
- Fewer wrong payments. Three-way matching stops payment for goods not ordered, not received or charged at the wrong price.
- A full record of every purchase. Auditors can see who asked, who approved, who supplied and what was paid.
- Clear spend data. Every purchase is recorded by supplier, category and site, which makes spend analysis much easier.
- Less manual work. Buyers spend less time chasing approvals and more time on sourcing.
In public procurement, electronic bidding is often required by law. In India, Rule 160 of the General Financial Rules, 2017 requires central ministries and departments to receive all bids through e-procurement portals, and Rule 149 requires common-use goods and services to be bought through the Government e-Marketplace (GeM) (Baker McKenzie).
How do you manage change when introducing eProcurement?
The hardest part of eProcurement is getting people to use it. If users find the system slower than the old way, they will go around it, and the system will hold only part of your spend. These are the problems that come up most often, and what to do about them.
| Problem | What happens | What to do |
|---|---|---|
| Too many approval steps | Users split orders or buy outside the system | Set approval limits by value. Small, low-risk purchases need one approval at most |
| Catalogue prices out of date | Users stop trusting the catalogue | Give each catalogue an owner and a review date |
| Key suppliers not onboarded | Orders go back to email and phone | Onboard the suppliers that get most of your orders before go-live |
| Invoices paid without a purchase order | Nothing changes, because the old way still works | Agree a “no purchase order, no payment” rule with finance, with a short written list of exceptions such as utilities |
| Approvers not trained | Requests sit for days waiting for approval | Train approvers, not only buyers. Send reminders and allow approval on mobile |
| Too much launched at once | Every problem appears at the same time | Start with a few high-volume categories and one or two sites, then expand |
Start with the categories people buy most often
Start with items people buy often, such as office supplies, IT accessories, safety gear or maintenance spares. Users see the benefit quickly, and you learn what needs fixing before you add complex categories.
Get finance on your side early
The “no purchase order, no payment” rule is what makes the change stick. Finance has to own it, because accounts is where invoices without orders are stopped. Agree the exceptions in writing before go-live. Otherwise every department will ask for its own exception.
Onboard suppliers before go-live
Suppliers need to know how to receive orders and send invoices through the new system. Start with the suppliers that receive the most orders from you. Small suppliers may need help to register. If you charge suppliers a fee to join, many small suppliers will refuse, and you will lose them from your supplier base. Our guide to supplier onboarding covers this in detail.
Track adoption every month
Measure how much spend goes through the system, by site and by category. Share the numbers with site heads. When a site’s figure is low, find out why. The cause is usually a missing catalogue, a slow approver or a supplier not yet onboarded.
How do you measure whether eProcurement is working?
| Measure | What it tells you |
|---|---|
| Share of spend with a purchase order | How much buying goes through the system |
| Share of spend from catalogues or contracts | How much buying happens at agreed prices |
| Time from request to purchase order | Whether approvals are slowing users down |
| Invoices matched first time | Whether orders, receipts and invoices are accurate |
| Invoices paid without a purchase order | How much buying still happens outside the system |
| Suppliers onboarded | Whether suppliers can receive orders and send invoices online |
Measure these before you go live, so you can show the change. Without a starting figure, nobody can say whether the system has helped.
What are the common eProcurement mistakes?
- Treating it as an IT project. The software is the easy part. Changing how people buy is the hard part.
- Copying old approval chains into the new system. A slow paper process becomes a slow digital process.
- Going live without suppliers. Buyers end up printing purchase orders and emailing them.
- Allowing invoices without purchase orders. The old way remains easier, so people keep using it.
- Messy supplier data. If one supplier appears under several names, reports and approvals both go wrong. Clean the supplier master file before go-live.
- No owner after go-live. Catalogues go out of date and approval limits stop matching the organisation.
How does Krinati support eProcurement?
Krinati’s eSourcing platform covers the sourcing part of eProcurement: RFIs, RFQs, RFPs and reverse auctions. Suppliers bid online, every bid and award decision is recorded, and the awarded price is ready to be used in your purchase orders and catalogues.
Frequently asked questions about eProcurement
What is eProcurement?
eProcurement means using software to run company buying, from the purchase request through approval, purchase order, goods receipt, invoice and payment. Many companies also include sourcing steps such as RFQs and reverse auctions. The aim is to make buying faster, keep it within agreed rules and prices, and leave a clear record of every step.
What is the difference between eProcurement and eSourcing?
eSourcing covers choosing the supplier and agreeing the price, through RFIs, RFQs, RFPs and reverse auctions. eProcurement covers buying from that supplier after the price is agreed: requests, approvals, purchase orders, receipts, invoices and payment. Some people use eProcurement to mean both.
What are the steps in the eProcurement process?
A user raises a purchase request. It is approved according to value limits. If no contract exists, the item is sourced. A purchase order is sent to the supplier. Goods or services are received and recorded. The invoice is matched to the order and the receipt, and then paid.
What is three-way matching?
Three-way matching means checking that the invoice, the purchase order and the goods receipt agree on item, quantity and price before the invoice is paid. It stops payment for goods that were not ordered, not received, or charged at the wrong price.
Why do eProcurement projects fail?
Most fail because people do not use the system, not because of the software. Common causes are too many approval steps, catalogues with old prices, suppliers who were never onboarded, and invoices still being paid without a purchase order.
How do you manage change when introducing eProcurement?
Start with a few high-volume categories, set approval limits by value, train approvers as well as buyers, onboard key suppliers before go-live, and agree with finance that invoices without a purchase order are not paid except for a short list of exceptions. Track the share of spend going through the system every month.