How can the range of possible applications and the division of responsibilities with the ERP system be correctly determined?
Today, e-procurement systems cover a broad spectrum of the procurement process: from supplier management to spend analysis. This is precisely where the challenge lies: anyone selecting or designing a new system must decide which functions are of the highest priority and how functions and data can be sensibly divided between the e-procurement and ERP systems.
It is not just the range of functions offered by a software programme that is decisive. Only the interplay between processes, system architecture and users creates the foundation for efficient and transparent procurement.
E-procurement: from supplier management to operational procurement
E-procurement systems support a range of tasks throughout the procurement process. In supplier relationship management (SRM), registration, onboarding and qualification can be digitised. The management of certificates and self-declarations, supplier evaluations and risk monitoring creates transparency and helps companies to take sustainability requirements and due diligence obligations within the supply chain into account.
In strategic procurement, e-sourcing functions enable the execution of enquiries and tenders, the comparison of bids and digital communication with suppliers throughout the entire tendering process. Auctions, in particular reverse auctions, are also used to promote competition and achieve cost-saving targets. Furthermore, systematic product group management supports the development of procurement strategies and the analysis of various procurement scenarios.
Contract Lifecycle Management (CLM) complements these processes with centralised contract repositories, templates and clause libraries, digital approval workflows and electronic signatures. Automated deadline monitoring helps to keep track of termination and renewal dates and ensure compliance with contractual obligations.
In operational procurement, the focus is on requisitions, approvals and purchase orders. Electronic catalogues, punchout interfaces and online marketplaces enable guided buying: employees are directed specifically to designated procurement channels and agreed terms and conditions. Budget checks, account allocation suggestions and the monitoring of purchase orders can further support the process.
E-procurement and ERP: The right system architecture as a key to success
A key challenge when implementing e-procurement is ensuring a clear division of responsibilities with the existing ERP system. Whilst the ERP system generally manages organisational structures, financial master data, material master data and accounting supplier information (the accounts payable master), the e-procurement system should, in particular, handle supplier qualifications, certificates, catalogues, prices, product groups, as well as user roles and approval rules. The specific allocation depends on the existing system landscape.
A clear division of responsibilities is also crucial when it comes to transaction data. Purchase requisitions, tenders and approval processes can take place within the e-procurement system. If the ERP system handles the order, purchase orders should be created there or transferred to it. In this way, the ERP system retains central control over order numbers, order status and outstanding commitments. Depending on process requirements, goods receipts can be recorded in either the ERP system or the e-procurement system.
The interfaces between the systems must be taken into account from the outset. This includes determining which data is to be transferred synchronously or asynchronously and which IT systems are to be integrated. The integration of multiple ERP systems or existing solutions for invoice verification and approval must also be taken into account during the design phase. A well-thought-out integration strategy lays the foundation for reliable data exchange and end-to-end procurement processes. Furthermore, responsibilities and a clear correction process must be established to deal with erroneous data transfers.
An example of the division of responsibilities between e-procurement and ERP
E-Procurement
Master Data
Supplier qualifications
Certificates
Catalogs
Prices
Product categories
User roles and approval rules
Processes / Transaction Data
Purchase requisitions
Tenders
Approval processes
(optional) Goods receipt
Data Exchange
and Integration
and Integration
←→
Master Data
e.g. suppliers, materials, organizations
Transaction Data
e.g. purchase orders, order status, goods receipt
Status Information
e.g. approvals, outstanding commitments
ERP
Master Data
Organizational structures
Financial master data
Material master data
Vendor master data (accounting-related supplier information)
Processes / Transaction Data
Purchase orders
Purchase order numbers
Purchase order status
Outstanding commitments
(optional) Goods receipt
⚙ InterfacesSynchronous or asynchronous
Additional ERP Systems
e.g. multiple ERP systems
Invoice Verification and Approval Solutions
Additional IT Systems
Additional Integrations
Automation and AI open up new possibilities
Analytical and control functions are becoming increasingly important in procurement. Spend analytics enables expenditure to be analysed by product group, supplier or cost centre. Dashboards and key performance indicators help to track savings, identify variances and highlight non-contractual procurement – known as ‘maverick buying’.
AI-supported functions offer further opportunities for automation. Typical use cases include AI applications that prepare complex tenders, translate text from purchase requisitions into enquiries, transfer existing framework agreements into catalogues, or support recurring routine tasks by using AI to transfer order confirmations from emails into the e-procurement system. It is crucial to assess the specific added value of these use cases and to integrate them effectively into existing processes.
Integrate invoice processing efficiently with the ERP system
When processing invoices, the first step should be to check whether the company already has established and well-integrated solutions in place. These do not necessarily need to be replaced by functions within the e-procurement system. The aim is to avoid duplication of functionality and unnecessary interfaces.
Electronic invoices, for example in the XRechnung or ZUGFeRD formats, as well as the automated recognition of paper and PDF invoices, form important foundations. The reconciliation of purchase orders, goods receipts and invoices is particularly relevant. If the data matches within defined tolerances (3-way match), an automated posting can take place in accordance with the specified approval rules. Payment is governed by the designated payment process. Quantity and price discrepancies, on the other hand, must be resolved in a structured manner to ensure invoices are approved on time and to take advantage of cash discount periods.
Electronic Invoicese.g. XRechnung or ZUGFeRD
Paper Invoices
PDF Invoiceswith automated data extraction
3-Way Match
Purchase Order
Goods Receipt
Invoice
Data Matchingwithin defined tolerances
Data Matches
Automated posting according to approval rules; payment in line with the payment process
Quantity and Price Discrepancies
Structured clarification is required to approve invoices on time and take advantage of early payment discounts.
System architecture in selection and implementation
The selection of an e-procurement system must be based on a thorough analysis of existing processes and individual requirements. Vendor-neutral specifications, practical use cases and a transparent comparison of functions provide a sound basis for decision-making. In addition to the scope of functions, the extent to which the solution can be integrated into the existing system landscape is crucial. An important factor for the success of the roll-out is selecting the right implementation partner. Metroplan considers all processes end-to-end and incorporates its best-practice solutions, drawn from more than 20 years’ implementation experience, into the design.
For a successful implementation, procurement, business departments and IT must be involved at an early stage. Training and targeted communication promote acceptance. Pilot projects make it possible to introduce processes step by step, test technical integration and identify potential for optimisation at an early stage. Metroplan insists on defining responsibilities for data, processes and system maintenance right from the start.
Project example: Digitalisation roadmap and implementation of an e-procurement system.
Taking a holistic approach to e-procurement and ERP
The introduction of an e-procurement system is more than just an IT project. It is crucial to clearly delineate the functions and responsibilities between e-procurement and ERP, to design end-to-end processes and to involve users at an early stage. A well-thought-out system architecture lays the foundations for realising the potential for automation, increasing transparency and ensuring the long-term success of the procurement function.
