Service procurement is often a blind spot in business transformation programs. While organizations typically devote significant attention to direct material procurement, service procurement is still frequently handled through a mix of free-text orders, limit-based procurement, and manual confirmations. The result is complexity, limited transparency, and additional effort in invoice clarification and service confirmation. 
The issue is rarely a lack of tools. More often, organizations fail to differentiate between service types. A preventive maintenance visit, an urgent repair, and a large engineering project follow fundamentally different business logics. Yet in many organizations, they are handled in similar ways, reducing efficiency and limiting automation potential. 

A practical way to bring structure into service procurement is to distinguish between three service archetypes:

The first archetype is planned and standardized services. These are recurring or clearly defined demands with known scope, quantities, and pricing, such as facility management or preventive maintenance. The business objective is to ensure efficiency, enable automation, and minimize friction. 

The second archetype is unplanned or flexible services. These services are procured as needed, while scope, timing, or effort remain unclear upfront. Typical examples include reactive maintenance, small repairs, or consulting support. Here, the priority is controlled flexibility rather than maximum standardization. 

The third archetype is structured and complex services. These are project-based services with detailed requirements, multiple service components, milestones, and strong documentation needs, such as construction or engineering projects. In these cases, transparency, auditability, and cost control play a central key role.

Once this distinction is made, organizations can define more effective target processes. This is where technology-driven transformation (e.g. S/4HANA) becomes a real business opportunity. Instead of treating service procurement as a purely technical migration topic, organizations can redesign it around business needs and process requirements. 

1. Understand the service landscape 
The first step is to segment service spend according to business characteristics such as scope clarity, complexity, and required level of control. This creates a clear basis for identifying where standardization is possible and where flexibility or structured control is needed. 

2. Design the right process and procurement models 
Modern ERP environments such as SAP S/4HANA already provide different options to support different service types. Within SAP, Lean Services should be prioritized to maximize standardization, automation, and transparency. Within this model, master data-based services support recurring and highly standardized demand, while limit-items (enhanced limit) support budget-based procurement when scope is uncertain. For highly structured and hierarchical service specifications, classic MM-SRV remains relevant. 
Depending on the service category and operating model, additional platforms such as e-procurement solutions or SAP Fieldglass can complement the ERP backbone for specific use cases, for example, supplier-facing procurement flows or scenarios with a high share of external workforce. The key point is not the technology itself, but choosing the right model for each business scenario. 

3. Enable automation and AI 
Once the core process model is defined, organizations can use technology to reduce manual effort and improve control. Practical use cases include AI-supported extraction and validation of service confirmations, AI-based checks of purchase orders against contract scope or rate cards, and forecasting of service spend overruns based on PO, service confirmation, and invoice data. 

Service procurement should not be treated as a niche operational issue within Purchase-to-Pay. It is a strategic design topic with a direct impact on efficiency, financial transparency, compliance, and automation potential. 
Organizations that differentiate service types, align procurement models accordingly, and build the right digital foundation will reduce manual effort and create a stronger basis for future AI-enabled performance improvement. 
Better service procurement does not start with more control. It starts with a clear and well-defined structure.

Kubach, M.