SAP MM process guide
Buying a service is different from buying a material. A material can be counted at goods receipt; a service must be described, performed, checked and formally accepted before the invoice is cleared. This guide follows that control chain from the initial requirement to payment.
What is SAP MM service procurement?
SAP MM service procurement is the process used to request, order, record and approve work performed by an external supplier. Typical examples include equipment maintenance, security, consulting, calibration, transport and facility services. The business is not receiving a stocked material. It is confirming that an agreed activity was delivered for the correct period, quantity, value and cost object.
The central evidence is normally a service entry sheet (SES). It records the service actually performed with reference to a purchase order. Acceptance of that entry sheet is an operational approval: it confirms that an authorised person has reviewed the work before the supplier invoice proceeds. This makes the SES comparable to a goods receipt in the control flow, although the business evidence and configuration are different.
A learner should first understand standard purchasing documents. The existing SAP MM purchase order guide explains document types, items, pricing and follow-up. Service procurement builds on that foundation by adding service specifications, value limits, acceptance and service-based invoice checks.
SAP MM service procurement process flow
The cleanest way to learn this process is to follow the documents and the business owner at every hand-off.
- Define the requirement. The requesting department describes the work, delivery location, performance dates, expected quantity or value, and the cost object that will receive the expense.
- Create and approve the purchase requisition. A requisition can carry the service requirement and its account assignment. Release or workflow rules should reflect value, risk and responsibility rather than merely the document creator.
- Source the supplier. Purchasing selects an approved supplier, agrees the commercial conditions and converts the requirement into a service purchase order.
- Issue the service purchase order. The PO defines what may be performed, the validity or delivery period, pricing or limits, account assignment, acceptance expectations and invoice-related controls.
- Record the work in a service entry sheet. The receiver enters the completed service against the relevant PO item. Planned lines can be copied from the order; permitted unplanned work must stay within the applicable limit.
- Accept or reject the service entry sheet. An authorised approver checks the work, dates, quantity, evidence and cost. Rejection should return a clear reason instead of leaving the document in an ambiguous status.
- Post and verify the invoice. The invoice is checked against the order and accepted service. Variances are handled according to tolerances and policy before the liability becomes payable.
- Review PO history and close the commitment. The team confirms that no service or value remains open unnecessarily and that the final entry or completion status reflects reality.
Document and ownership map
| Stage | Main record | Business question | Typical owner |
|---|---|---|---|
| Demand | Purchase requisition | What work is needed, why and for which cost object? | Requester / cost owner |
| Commitment | Service purchase order | What is the supplier authorised to perform and charge? | Purchasing |
| Performance | Service entry sheet | What was actually delivered during the stated period? | Service receiver |
| Acceptance | Accepted SES | Is the work complete, accurate and approved? | Operational approver |
| Liability | Supplier invoice | Does the claim agree with the PO and accepted work? | Accounts payable |
Planned services, unplanned services and limits
A planned service is described in advance. The PO can specify the service, quantity, unit, price and expected period. During entry, the receiver selects the relevant planned line and records what was completed. This approach gives purchasing and the approver a precise baseline for comparison.
An unplanned service is not fully known when the order is created. The PO therefore provides a controlled value boundary instead of pretending that every eventual task is predictable. When work is entered, the description, quantity, price and performance details still need to be recorded. The limit is permission to manage genuine uncertainty; it is not permission to accept vague or unrelated charges.
For training exercises, compare a planned monthly equipment inspection with an emergency repair covered by a limit. Ask which details can be agreed before performance, which evidence must be supplied after performance, and who is allowed to approve the additional value.
Controls that make service purchasing reliable
Account assignment
Services are commonly procured for consumption rather than stock. The purchase document therefore needs a valid account assignment, such as a cost center, internal order, asset, project or maintenance order. The correct category determines which fields are required and where the expense or commitment is reported. When a PO is created without a material master, material-group defaults can assist account selection, but the business owner must still confirm that the cost object represents the purpose of the work.
Separation of duties
The person requesting the work should not automatically have unlimited authority to order, accept and approve payment. A practical design separates commercial ordering, operational confirmation and invoice processing. Flexible workflow or release rules can route decisions by company code, purchasing group, cost object and value. For the approval concepts behind purchasing documents, see the SAP MM release strategy and flexible workflow guide.
Acceptance evidence
The SES description should let a reviewer understand what was done. Depending on the service, evidence could include a completion note, timesheet, inspection result, milestone sign-off or attachment. Acceptance should be withheld when the period is wrong, the claimed quantity is unsupported, the service is outside the PO scope or the approver lacks operational knowledge.
Invoice matching
Invoice verification should use the accepted service rather than relying only on the supplier invoice. The PO establishes the commercial basis; the accepted SES establishes performance; the invoice establishes the claim for payment. Readers who need a broader explanation of matching and blocks can use the SAP MM invoice verification guide.
Common SAP MM service procurement problems
| Symptom | Likely area to inspect | Useful check |
|---|---|---|
| The PO cannot be selected for an SES | Item type, status, validity, deletion or completion | Confirm that the PO contains an eligible open service item. |
| An unplanned line exceeds the permitted value | Overall or expected limits | Compare entered value with the approved limit and prior consumption. |
| The SES is created but the invoice remains blocked | Acceptance status, quantity, value or tolerance | Review PO history and confirm that the correct entry sheet was accepted. |
| The expense reaches the wrong cost object | Account assignment and distribution | Trace the account assignment from requisition through PO, SES and invoice. |
| Open commitments remain after work is complete | Final-entry and delivery-completion handling | Confirm whether remaining quantity or value is genuinely expected. |
Troubleshooting should start from the visible document flow. Check status and history before changing configuration. A status may be correctly preventing an invoice because acceptance is missing; increasing a tolerance or bypassing an approval would hide the control failure rather than solve it.
Practice scenario
A plant hires a supplier for quarterly compressor maintenance. The PO contains one planned inspection line and a controlled limit for minor corrective work. In the first visit, the supplier completes the inspection and replaces a seal. Build a test case that records both activities, attaches evidence, sends the SES to the maintenance owner, rejects an intentionally overstated quantity, corrects it, accepts the entry and verifies the invoice. Document the account assignment and PO-history changes after each step.
After mastering service purchasing, compare it with the SAP MM consignment process, where liability is triggered by stock withdrawal, and with the SAP MM automatic account determination guide, which explains how logistics events reach G/L accounts.
Frequently asked questions
Is a service entry sheet the same as a goods receipt?
No. Both can provide receipt evidence in procurement, but an SES records and accepts performed services against a service PO. A material goods receipt updates material quantities and may update stock value. The document behavior depends on the procurement scenario and system configuration.
Can an invoice be posted before the SES is accepted?
In a controlled service process, invoice verification relies on accepted service performance. If acceptance is missing, the invoice may not be eligible for normal processing or may be blocked. Exact behavior depends on the PO and invoice-verification settings.
What is the difference between planned and unplanned services?
Planned services are specified in the purchase order before work begins. Unplanned services are entered after performance under an approved value limit. Both require meaningful description, authorisation and acceptance.
Which team accepts the service entry sheet?
The approver should be the person who can verify that the service was actually delivered, often a maintenance owner, project manager or department representative. Purchasing controls the commercial commitment, while accounts payable verifies the invoice.