MM / P2Padvanced

MM Service Procurement Part 5: Invoice Verification, GR/IR and Limits

Key takeaway

Close the service cycle: GR-based invoice verification against SES, limits (overall limit, expected value) for unplanned services and how invoices consume them, GR/IR for services, accruals, and troubleshooting invoice blocks and variances.

Explanation

📌 KEY POINTS
✅ With GR-based IV, invoices are matched to accepted SES.
✅ Limits: overall limit caps total; expected value feeds commitments/budget.
✅ Unplanned services can be accepted up to the limit; invoices beyond need approval/PO change.
✅ GR/IR for services: SES acceptance credits, invoice debits.
⚠️ Invoices exceeding accepted SES or limits must be blocked, not paid.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered architecture. Now invoices and limits.

━━━━━━━━━━━━━━━━━━━━
▶ 1. GR-BASED IV

Invoice per SES; quantity/value matching.

━━━━━━━━━━━━━━━━━━━━
▶ 2. LIMITS

Overall limit, expected value, no-limit flag; consumption by SES/invoices.

━━━━━━━━━━━━━━━━━━━━
▶ 3. GR/IR AND ACCRUALS

SES acceptance creates accrual via GR/IR.

━━━━━━━━━━━━━━━━━━━━
▶ 4. BLOCKS AND VARIANCES

Price/quantity tolerances; limit exceeded.

━━━━━━━━━━━━━━━━━━━━
▶ 5. TROUBLESHOOTING

Invoice without SES, SES revoked, wrong account assignment.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Post SES within limit.
Post invoice exceeding SES; check block.
Resolve via SES/PO update.

✅ CHECKPOINT: paid amounts never exceed accepted services within limits.

Code example

ABAP Code

===== STEP 1: limits =====PO limit item: overall limit 20,000, expected value 15,000 | SES unplanned up to limit ===== STEP 2: invoice =====MIRO with GR-based IV → reference SES → tolerance check → block if exceeded ===== STEP 3: GR/IR =====SES: Dr cost | Cr GR/IR → invoice: Dr GR/IR | Cr supplier

Real project scenario

A facilities client used large limit items and paid invoices directly against them without SES. Overbilling went unnoticed. Requiring SES acceptance before invoicing (GR-based IV) and monitoring limit consumption stopped unverified payments.

Common mistakes

Invoices without SES.
Huge limits with no monitoring.
Ignoring expected value.
No tolerance checks.
Wrong account assignment.

Best practices

Use GR-based IV.
Size limits realistically.
Monitor consumption.
Configure tolerances.
Review blocked invoices.

Interview angle

Questions: "How are service invoices verified?", "What is a limit?", "Overall limit vs expected value?"
Strong answer: GR-based IV via SES, limit mechanics, GR/IR and accruals, blocks and troubleshooting.

Practice this lesson

Quick check

1. What does the expected value of a limit item influence?

2. A team proposes setting "no limit" on service limit items to avoid blocks. What is the risk?

3. Invoices are paid directly against large limit items without SES. What fixes this?

Interview questions

1. On a purchase order limit item, which configuration fields control the overall value limit and the expiration/validity period, and how does the system track consumption against that limit differently from a standard account-assigned line item?

Answer it in your own words first, then compare.

2. Service invoices are paid against limit items without SES, and some exceed agreed budgets. How do you control service invoicing and limits?