Service Procurement: Service PO, Service Entry Sheet and Acceptance
Buying work instead of goods: the PO has a service item charged to a cost center, the supplier performs the service, a service entry sheet records what was done, and its acceptance — not a goods receipt — posts the cost and allows the invoice.
Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.
Digital twin
01Order the service
PO 4500003300 to Demo Compressor Services (fictional): compressor servicing, ₹40,000, cost center CC-4100 (Maintenance).
Business scenario
Maintenance orders the annual servicing of four air compressors from an external service company for ₹40,000, charged to cost center CC-4100.
All companies, numbers and documents are fictional demo data.
Step-by-step flow
- 01
Order the service open in twin
PO 4500003300 to Demo Compressor Services (fictional): compressor servicing, ₹40,000, cost center CC-4100 (Maintenance).
There is no material to stock; the cost has to land on a cost object.
- 02
The technician does the work open in twin
The technician services the four compressors on site.
Nothing is posted until someone confirms what was done.
- 03
How is the service confirmed? open in twin
The work is done. How is it recorded in SAP?
They describe work done (lines, quantities, hours), which a goods receipt cannot.
- 04
Services are not received in MIGO open in twin
A classic service item has no material and no goods receipt. MIGO has nothing to receive.
Its acceptance creates the same effect: a confirmed receipt the invoice can be matched to.
- 05
Enter and accept the service entry sheet open in twin
Service entry sheet 1000000400 is entered and accepted: ₹40,000 is charged to CC-4100 (Maintenance).
Typically the requester accepts, so the person who saw the work confirms it.
- 06
Invoice open in twin
The invoice is matched to the accepted entry sheet and clears GR/IR.
Only accepted services are paid.
- 07
Service paid for open in twin
Service PO → work → entry sheet accepted → invoice.
In S/4HANA, lean services simplify this with service items on normal POs and a lighter entry sheet app.
SAP documents
Stock impact
This part of the process does not change stock.
Accounting impact
Acceptance of a service entry sheet
TypicalEnter and accept the service entry sheet
- Dr Maintenance services — CC-4100 (Maintenance)₹40,000
- Cr GR/IR clearing (WRX)₹40,000
Acceptance posts the cost to the account-assigned cost object against GR/IR, like a goods receipt for a consumable.
Invoice for the service
TypicalInvoice
- Dr GR/IR clearing (WRX)₹40,000
- Cr Supplier (payable)₹40,000
Matched to the service entry sheet.
Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.
Movement type
This flow spans several documents rather than a single movement type.
Procures external services with the same controls as goods: an ordered value, a confirmation of work performed, and invoice matching.
Transactions & Fiori apps
- ME21N — Create Service PO
- ML81N — Service Entry Sheet (ECC / classic)
- MIRO — Invoice
- Manage Service Entry Sheets — Lean ServicesS/4HANA; availability depends on release and scope
Differences by SAP version
Classic service procurement with service specifications and ML81N.
Classic service procurement still available; lean services offered as a simpler option.
Lean services with Fiori apps.
Configuration
Item category D (classic) vs lean services
Configuration dependentClassic uses service specifications and ML81N; lean services use a simpler service item and app.
Unplanned services limit
Configuration dependentHow much may be entered beyond the planned services.
Prerequisites
- Service master or short-text services
- Cost center or other account assignment
- Acceptance authorisation for the requester
Master data
- Service master (classic)
- Standard service lines and prices.
Organizational structure
- Purchasing organization 1000 (demo)
- CC-4100 (Maintenance)
Tables
| Table | Description |
|---|---|
| ESSR | Service entry sheet header (classic) |
| ESLL | Service lines (classic) |
Integration
- COService cost on the cost center at acceptance.
- FIGR/IR and payable.
Common errors
“Invoice cannot be posted”
Likely causes: Entry sheet not accepted; Value exceeds the ordered limit
Where to look: Service entry sheet status · PO limits
Troubleshooting
Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.
CHECK 1
Acceptance
- Is the entry sheet accepted?
- Within the PO value?
Interview questions
What replaces the goods receipt for services?
The service entry sheet. It records the services performed against the PO; its acceptance posts the cost to the account-assigned object against GR/IR and allows the invoice to be matched.
Quiz
References
- SAP SE — SAP Help Portal: External Services Management (source)
- SAP SE — SAP Help Portal: Lean Services (source)
Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.
Version history
| Version | Change |
|---|---|
| 1.0.0 | Initial version. |