SD / O2Cintermediate

SD Returns Part 3: Returns Integration with Inventory and Finance

Key takeaway

What returns do to stock and accounts: goods receipt into blocked returns stock (651), inspection and transfer postings to unrestricted, quality or scrap, valuation of returned goods, credit memo postings and revenue reversal, restocking fees, and controls against unapproved credits.

Explanation

📌 KEY POINTS
✅ 651 posts goods into blocked returns stock — non-valuated in many setups — so returns don't inflate usable inventory.
✅ Inspection decides: transfer to unrestricted (e.g. 453), quality inspection, scrap (551) or return to vendor.
✅ The credit memo reverses revenue (and tax) and credits the customer; COGS reversal happens with valued stock movements.
✅ Restocking fees are modelled as pricing conditions on the returns order.
⚠️ Transferring returns directly to unrestricted stock without inspection creates quality and accounting risk.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 configured returns. Now the effects on stock and accounts.

━━━━━━━━━━━━━━━━━━━━
▶ 1. STOCK POSTINGS

Goods receipt 651 → blocked returns stock.
453 → unrestricted (valuated), 551 scrap, transfer to quality.

━━━━━━━━━━━━━━━━━━━━
▶ 2. VALUATION

Value posted at transfer to unrestricted (standard/moving price).
Scrap posts to scrap expense.

━━━━━━━━━━━━━━━━━━━━
▶ 3. CREDIT MEMO

RE billing: Dr revenue (reversal), Dr tax, Cr customer.
Billing block released after inspection/approval.

━━━━━━━━━━━━━━━━━━━━
▶ 4. FEES AND DEDUCTIONS

Restocking fee condition (negative credit) on returns item.
Partial credits for damaged goods.

━━━━━━━━━━━━━━━━━━━━
▶ 5. S/4HANA ADVANCED RETURNS

Inspection results and follow-up activities (refund, replacement, return to supplier) in one process.

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

Post returns goods receipt (651) and check stock.
Transfer to unrestricted after inspection (453).
Release block and create credit memo; check FI.

✅ CHECKPOINT: stock and accounting match: returned goods valued once, customer credited once.

Code example

ABAP Code

===== STEP 1: stock =====651 GR returns → blocked returns stock (MMBE)453 transfer blocked returns → unrestricted | 551 scrapping | QM inspection lot (if active) ===== STEP 2: finance =====Credit memo RE: Dr revenue (ERL reversal) | Dr output tax | Cr customerTransfer 453: Dr inventory | Cr cost of goods (reversal) per valuation ===== STEP 3: fees =====Pricing condition ZRST restocking fee −10% on returns item

Real project scenario

A consumer electronics distributor posted returns straight to unrestricted stock to speed up resale. Defective units were resold, customer complaints rose, and inventory value included faulty goods. Introducing 651 blocked returns stock, inspection with transfer or scrap decisions, and credits only after inspection brought quality and inventory back under control.

Common mistakes

Skipping blocked returns stock.
No inspection decision tracking.
Crediting before inspection.
Forgetting restocking fee conditions.
Ignoring valuation effects.

Best practices

Use 651 and inspection.
Track follow-up decisions.
Credit after approval.
Model fees as conditions.
Reconcile returns stock monthly.

Interview angle

Questions: "What happens in inventory when goods are returned?", "How is the credit memo posted?", "How do you handle restocking fees?"
Strong answer: 651 blocked returns stock, 453/551/quality after inspection, valuation effects, credit memo reversing revenue and tax, restocking fee conditions, billing block release, ARM in S/4HANA.

Practice this lesson

Quick check

1. After inspection, returned goods are fine to resell. Which posting moves them to usable stock?

2. How should a restocking fee on returns be handled in SD?

3. Why is a billing block typically set on returns orders?

Interview questions

1. Design the end-to-end architecture for handling returns with ATP and requirements transfer implications when returned stock must be re-evaluated for resale versus scrap.

Answer it in your own words first, then compare.

2. Suppose you inherit an existing Returns solution. How would you review it before making a change?