Digital procurement: process, benefits and rollout in purchasing
How digital procurement differs from e-procurement and Procurement 4.0, how the digital procurement process runs step by step, and what purchasing, business units, finance, IT and audit actually get out of it.
A guide for private-sector companies with many requesters, several legal entities and an ERP that is meant to stay in charge. Includes a maturity model, common obstacles and an order of work for getting started in indirect procurement.
- Definition and terminology
- Process step by step
- Benefits by department
- Maturity model and roadmap
What is digital procurement?
Digital procurement means handling purchasing electronically from end to end: from the need through requisition, approval and purchase order to goods receipt, invoice and reporting, data is captured once and passed from system to system instead of being carried over by email, form or spreadsheet.
A procurement process is not digital just because a paper form has become a PDF. What matters is that the data is structured: item, price, supplier, cost center and approver are fields the next system can work with. Only then can approvals follow rules, orders reach the ERP without being retyped, and spend be analysed by category.
In practice, digitalization in purchasing starts with indirect demand: office and consumable supplies, safety equipment, lab supplies, tools, spare parts, IT accessories. That is where many requesters, many suppliers and many small transactions meet, and where a great deal of the manual effort arises.
Digital procurement at a glance
- Subject
- The entire procurement process, operational and strategic, including collaboration with suppliers
- Core principle
- Data is captured once in structured form and handed to the next step without re-entry
- Typical building blocks
- Electronic catalogs, purchase requisition, approval workflow, ERP integration, supplier portal, reporting
- People involved
- Purchasing, requesters in the business units, finance and controlling, IT, audit, suppliers
- Related terms
- E-procurement is the operational part of it; Procurement 4.0 describes the target picture of a connected purchasing function
Digital procurement, e-procurement, Procurement 4.0: the differences
The three terms are often used interchangeably but mean different things: an umbrella term, a system category and a guiding vision.
| Criterion | Digital procurement | E-procurement | Procurement 4.0 |
|---|---|---|---|
| What the term describes | The state in which procurement runs electronically and on structured data throughout | Electronic handling of ordering through catalogs, purchase requisitions and approvals | A guiding vision derived from Industry 4.0: connected, largely automated purchasing |
| Scope | Strategic and operational purchasing, supplier management, invoice handling, reporting | Mainly operational purchasing, from the need to the purchase order | The whole purchasing function, including its links to production, logistics and suppliers |
| Typical tools | ERP, e-procurement system, supplier portal, sourcing and contract management, invoice processing | Catalog system, internal procurement shop, punchout connections to supplier shops, approval workflow | No fixed tool; the term describes capabilities such as automatically triggered demand and end-to-end data exchange |
| Main users | Purchasing, business units, finance, IT and suppliers | Requesters, approvers and operational buyers | Procurement leadership and strategy |
| What the term is good for | A frame for a roadmap spanning several years | A concrete project with a definable scope | A statement of direction, not a project brief |
Related terms in brief
- Procurement digitalization
- The journey rather than the state: moving individual workflows to electronic, integrated processes step by step. Digital transformation of procurement means the same thing and includes roles and responsibilities.
- Purchase-to-pay and source-to-pay
- Process terms rather than system terms. Purchase-to-pay runs from the requisition to payment; source-to-pay starts earlier, with tendering and supplier selection.
- E-tendering in the public sector
- Electronic awarding of public contracts. It follows public procurement law and uses its own platforms. This page deals with procurement in private-sector companies.
The digital procurement process step by step
Seven steps, each as a comparison: how the task runs manually and what changes in a digital procurement process.
| Step | Manual | Digital |
|---|---|---|
| 1Providing assortment and terms | Price lists arrive as PDF or Excel files by email. Purchasing files them or keys individual items into the ERP by hand. Which list is currently valid is often known only to the person who negotiated it. | Suppliers deliver catalogs in structured formats such as BMEcat or CSV, or connect their web shop via punchout. Purchasing reviews and approves; after that the negotiated prices are available to every requester.Catalog management |
| 2Need and product search | Someone with a need searches the internet, phones the supplier or asks a colleague how it was ordered last time. Whether a framework agreement exists is not visible at the desk. | Requesters search one interface across all approved catalogs and supplier shops. They see only items released for their organisational unit, at the negotiated price.Catalog Shop |
| 3Purchase requisition | The need reaches purchasing as an email, a form or a verbal request. There, item, quantity, supplier and cost center are typed into the ERP again; queries about missing details are part of the routine. | The cart becomes a purchase requisition carrying item number, price, supplier and account assignment. For needs outside the catalog there are free-text items and forms with mandatory fields.What is a purchase requisition? |
| 4Approval | Approval is given by signature or email reply. Who is responsible follows from habit or from a signature policy on the intranet. When someone is absent the request waits, and later it is hard to show who agreed and when. | The system routes the requisition to the responsible approvers by value, cost center or category. Every decision is logged with person, time and comment.What is an approval matrix? |
| 5Purchase order and handover to the ERP | Purchasing creates the order in the ERP and sends it to the supplier as a PDF. Typing errors in quantity, price or item number surface only at delivery or on the invoice. | The approved requisition is passed to the ERP through an interface and becomes the purchase order there. Purchasing steps in only when a rule requires it, for example for free-text needs or above a value limit.Procurement alongside S/4HANA |
| 6Goods receipt and invoice verification | Accounting finds out whether goods arrived by asking the business unit. Invoices without an order reference have to be matched, coded and approved one by one. | Goods receipt is posted in the ERP against the purchase order. Because price, quantity and account assignment come from the order, the invoice can be checked against order and goods receipt without anyone having to ask.The full process: source-to-pay |
| 7Reporting | Spend is pieced together afterwards from accounting entries. Anything bought by credit card, out of pocket or directly from the supplier appears in no category. | Orders are recorded with category, supplier, cost center and requester. Purchasing sees which catalogs are used, which searches return nothing and where orders bypass the framework agreement. |
Benefits of digital procurement by department
Each department judges the change by its own standards. So instead of a general list, here is the view of the five groups that have a say in the project.
Purchasing
Operational purchasing stops retyping orders for other people and gains time for categories, suppliers and negotiations.
- Catalog orders run within defined rules without purchasing stepping in
- Negotiated terms actually reach the purchase order, because the contract item is the easiest route
- Maverick buying becomes visible and therefore manageable
- Suppliers maintain catalog data themselves; purchasing reviews and approves
Business units and requesters
People who order only now and then do not want to operate an ERP or memorise a purchasing policy.
- One search instead of several supplier portals, logins and price lists
- Ordering without training, much like in an online shop
- The status of your own request is visible: submitted, in approval, ordered
- Favorites for recurring needs
Finance and controlling
For finance, what counts is knowing about an expense before the invoice arrives.
- Commitments are visible from the requisition onwards, not only once the invoice is in
- Cost center and G/L account are set at requisition, not afterwards in accounting
- Budget limits per cost center apply before the order is placed
- Invoices with an order reference can be verified in the ERP without queries
IT
IT assesses whether the solution fits the system landscape and how much operational effort it creates.
- The ERP remains the system of record for order, goods receipt and invoice; it is not rebuilt for occasional users
- Connection via established routes such as OCI, cXML or API instead of custom development
- One platform for several legal entities, including those on different ERP systems
- The operating model follows your own requirements: in your own data center or in a private cloud
Compliance and audit
To an auditor, a process is only as good as its evidence.
- Every approval is documented with person, time and comment
- The four-eyes principle is built into the workflow, not just written into the policy
- Changes to catalogs and prices are traceable
- Supplier evidence and self-disclosures are held in structured form, for example for supply chain due diligence obligations
A word on savings claims
You will not find blanket percentages for cost reduction here. How much a company saves depends on the number of orders, the current effort per transaction and the share of demand that can be covered by catalogs. These figures can be collected in-house and tested in the ROI calculator.
Why digitalization projects in purchasing fail
When projects stall, the cause is rarely the software and more often catalog data, responsibilities and adoption. Six common obstacles and what helps.
| Obstacle | What happens | What helps |
|---|---|---|
| Empty or outdated catalogs | Only a few suppliers are connected at go-live. Requesters cannot find what they need and go back to phone and email. | Before go-live, identify the categories with the most order transactions and connect exactly those suppliers first. Hand catalog maintenance to the supplier, with review by purchasing. |
| The old process is rebuilt one to one | Every special rule and every signature that grew up over the years is carried into the new system. The result is a digital process that takes just as long as the old one. | Revise the approval matrix before rollout: few levels, clear value limits, responsibility by cost center. |
| Unclear system boundaries | It stays open which system owns suppliers, material numbers and cost centers and where the purchase order is created. The consequences are duplicate data maintenance and interfaces nobody is responsible for. | Decide early which system leads which step and which documents are exchanged in which direction. |
| Too much at once | Sourcing, contract management, catalog, invoice receipt and supplier evaluation are all meant to go live on the same date. Purchasing, IT and finance are tied up for a long time, and benefits show late. | Start with the bottleneck, usually the ordering process for indirect demand, and extend from there. |
| Requesters are involved too late | The project is planned from purchasing's point of view. The people who place orders every day see the system for the first time in training. | Bring in pilot users from the business units early and test search with the terms they actually use. |
| Free text as a permanent fix | Whatever is not in the catalog is ordered as free text. As that share grows, the work lands back in purchasing and reporting loses its value. | Review free-text orders regularly and move recurring needs into catalogs or forms. |
Five stages of digitalization in purchasing
A pragmatic model for orientation, not a standard. Most companies sit at different stages depending on category and legal entity. The roadmap follows from asking what is missing for the next stage.
Paper, email and Excel
Needs are reported informally, approvals given by signature or email. The ERP sees the transaction only when the invoice arrives.
Ordering in the ERP
Purchasing enters requisitions and purchase orders in the ERP. Requesters have no access of their own; purchasing types in what it is told.
Catalogs for requesters
Requesters order for themselves from electronic catalogs and connected supplier shops. Prices and items come from negotiated assortments.
Integrated process
Approvals follow rules, the approved requisition reaches the ERP without re-entry, suppliers maintain their own catalogs. Free-text needs are the exception.
Managing by data
Purchasing analyses orders, search behaviour and catalog usage, adjusts assortments and rules accordingly, and rolls the process out to further entities and countries.
Ovenca comes in at stages three to five: catalog, purchase requisition, approval, handover to the ERP and usage reporting.
What to digitalize first in indirect procurement
Indirect procurement is a good place to start because many similar transactions meet many requesters there. An order of work that has proven itself:
Standard needs that fit a catalog
Office supplies, safety equipment, lab supplies, tools, maintenance consumables: items with fixed prices and recurring demand. This is where a large number of transactions occur, and the catalog replaces the call to purchasing.
Suppliers with their own web shop
Large assortments, for example from technical distributors or IT resellers, are connected via punchout. The requester picks items in the supplier's shop and the cart comes back as a purchase requisition.
Approval paths and value limits
Once orders exist in structured form, the signature policy can be turned into an approval matrix: who approves up to which value for which cost center.
Catalog maintenance by suppliers
The supplier enters price changes and new items in a portal; purchasing reviews and approves. Without this step, catalogs go stale as soon as the project team moves on to other work.
Needs outside the catalog
For services, custom-made items and one-off needs there are forms with mandatory fields instead of informal emails. Purchasing receives complete requests and can see which needs deserve a catalog.
Which categories belong to indirect procurement and how software for it is structured is covered on a separate page.
Measuring progress: metrics for digital procurement
A business case only holds up with your own baseline. These metrics can be collected before the project and compared regularly afterwards.
- Catalog rate
- Share of order lines that come from a catalog or punchout shop, relative to free-text lines.
- Cycle time
- Time from creating the purchase requisition to the order reaching the supplier, split by catalog and free-text demand.
- Maverick buying rate
- Share of spend placed outside the intended ordering route or outside existing framework agreements.
- Orders without purchasing involvement
- Share of transactions that go to the ERP after approval without manual handling in purchasing.
- Invoices with an order reference
- Share of incoming invoices that are based on a purchase order. The figure comes from the ERP and shows whether the process is really being used.
- Active requesters
- Number of requesters who ordered through the system at least once in the period, per entity or site.
With your own figures for order volume and effort per transaction you can estimate the effect in the ROI calculator.
Digital procurement in practice: LANXESS
“By integrating SAP contracts and material numbers into product search, we were able to increase the automation of our purchase-to-pay processes as intended. On the clearly structured administration level we control the release and availability of content, manage user permissions and obtain the transparency we want through meaningful reports.”
LANXESS AG has worked with Onveda since 2014 and uses Ovenca worldwide as its eProcurement platform. Contracts and material numbers from SAP appear directly in product search.
Choosing software for digital procurement
Before comparing vendors, four sets of questions should be answered in-house. They determine which kind of solution fits at all.
Scope and system boundaries
- Which steps should the new solution lead, and which stay in the ERP?
- Is this about the ordering process only, or also sourcing, contracts and invoice receipt?
- Which system owns suppliers, material numbers and cost centers?
- Should you start with one component and extend later?
Integration
- Which ERP systems are in use, including in subsidiaries?
- Are SAP ECC and S/4HANA connected through standard routes, without modifying the ERP?
- Which documents are exchanged, and in which direction?
- How are interface errors detected and reprocessed?
Operations and data residency
- Is on-premise or private cloud available alongside public cloud?
- Where are data and backups stored, and who has administrative access?
- Who decides when updates are installed?
- How do you get your data back when the contract ends?
Adoption and suppliers
- Can occasional requesters find what they need without training?
- How do suppliers maintain their catalog data, and are they charged fees?
- How are needs handled that are not in the catalog?
- Is there a reference of comparable size and system landscape?
The detailed checklist with questions for your requirements specification is on the source-to-pay page.
Questions and answers on digital procurement
Digital procurement is the end-to-end electronic handling of purchasing, from the need through requisition, approval and purchase order to goods receipt, invoice and reporting. Its defining feature is that data is captured once in structured form and passed from system to system without re-entry.
E-procurement, or electronic procurement, means handling ordering through internet-based systems: electronic catalogs, purchase requisition, approval workflow and handover of the order to the ERP. The focus is on operational purchasing, especially for indirect demand.
E-procurement is one part of digital procurement. It covers the operational ordering process. Digital procurement is the umbrella term and additionally includes sourcing, contract management, supplier management, invoice processing and reporting.
Procurement 4.0 applies the idea of Industry 4.0 to purchasing: the systems of purchasing, production, logistics and suppliers are connected, and routine transactions run largely automatically. The term describes a target picture, not a product. Concrete projects on the way there include electronic catalogs, rule-based approvals and integration with the ERP.
Suppliers provide their assortment as an electronic catalog or via punchout. Requesters search it, add items to the cart and create a purchase requisition. The system routes it for approval by value and cost center. The approved requisition goes to the ERP through an interface and becomes a purchase order there. Goods receipt and invoice verification take place in the ERP with reference to the order.
Purchasing is relieved of routine orders, and negotiated terms are actually used. Business units order without detours and can see the status of their request. Finance knows about commitments before the invoice and receives invoices with an order reference. IT keeps the ERP as the system of record. Audit finds every approval documented.
The effort lies less in the software than in the preparation: catalogs have to be built, suppliers connected, approval rules clarified and interfaces to the ERP operated. Without well-maintained catalogs, requesters will not use the system. If the old process is rebuilt unchanged, the cycle time stays unchanged too.
With the ordering process for indirect demand that fits a catalog, such as office supplies, safety equipment or lab supplies. That is where a large number of similar transactions occur, and requesters feel the benefit immediately. Approval rules, catalog maintenance by suppliers and structured forms for needs outside the catalog come next.
That depends on the scope. The ERP handles purchase order, goods receipt and invoice but is usually too complex for occasional requesters. An e-procurement system adds catalog, procurement shop, approvals and supplier portal in front of the ERP. Integrated suites additionally cover sourcing, contracts and invoice processing. Ovenca belongs to the second category; sourcing events, contract administration and invoice receipt are not included.
Yes. Ovenca connects to SAP ERP and S/4HANA via OCI punchout, cXML or API. Microsoft Dynamics, Oracle, Infor and proprietary ERP systems are connected the same way. Legal entities on different ERP systems can use the same platform.
With metrics collected before the project and compared afterwards: catalog rate, cycle time from requisition to purchase order, share of orders without purchasing involvement, maverick buying rate and share of invoices with an order reference. General benchmarks are no substitute for your own baseline.
That depends on the scope. Starting with catalog and supplier portal is the smallest project, because the processes in the ERP remain unchanged. Replacing an existing procurement platform, including catalog migration, supplier onboarding and integration, is considerably larger. A reliable schedule is available once the system landscape, catalog inventory and interfaces have been reviewed.
Only to a limited extent. Public contracting authorities are bound by public procurement law; electronic tendering follows its own rules and uses its own platforms. This page describes procurement in private-sector companies, where framework agreements, catalogs and internal approvals shape the process.
Further reading
The individual building blocks of digital procurement and the neighbouring topics in detail.
Source-to-pay
The full process from supplier search to payment, phase by phase.
Indirect procurement
Categories, typical problems and software for indirect demand.
Catalog Management
Import and validate supplier catalogs and link them to contracts.
Catalog Shop
Search, cart and purchase requisition for requesters.
Vendor Portal
Suppliers maintain catalogs and evidence themselves, with approval by procurement.
S/4HANA procurement
Indirect procurement alongside S/4HANA, connected via OCI, cXML and API.
Related pages
Where does your purchasing stand, and what would the next step be?
In one conversation we map your ordering routes, systems and interfaces and tell you plainly which steps Ovenca takes on and which stay in the ERP.