SAP SD Returns Process — Stock Back, Money Back
RE & LR · goods receipt · credit memo · lean vs advanced · troubleshooting · Last updated October 2026
Order-to-Cash run backwards, with one important difference: you do not have to accept everything. The goods arrive before the money goes back, the quantity received may not match the quantity claimed, and what you do with the returned stock decides whether it can be sold again.
This guide follows one return end to end — five documents, with what happens to stock and money at each one — then the configuration behind it, when to use a credit memo request instead, how SAP’s two returns variants differ, and what to check when the credit never appears. Written for SAP S/4HANA on-premise and Private Edition; the classic flow is unchanged from ECC.
On this page
The returns flow
Scroll the diagram sideways to see all of it →
The returns process in SAP SD: five documents, two of which actually change something.
The original invoice
VF03The starting point. Creating the returns order with reference to the invoice is what keeps the credit at the price actually charged, rather than today’s price list.
Returns order
VA01 — type REA sales document of category H. It records intent, carries a reason for return, and usually carries a billing block so nobody credits the customer before the goods have been seen.
Returns delivery
VL01N — type LRThe inbound counterpart of a normal delivery. It exists so the warehouse has a document to receive against, and so the quantity actually returned can differ from the quantity claimed.
Goods receipt
VL02N — post goods receiptThe physical moment — but not yet the financial one. With the standard returns movement type 651 the goods land in blocked returns stock, which is non-valuated: the quantity is back, no accounting document is created, and the stock cannot be sold. Value returns only when a usage decision moves the goods into unrestricted stock with 453.
Credit memo
VF01The financial close. Revenue is reduced and the receivable is cleared or reduced. Until the billing block is released, this step cannot happen.
Worked example: 5 of 100 come back
A distributor invoiced a retailer for 100 units at ₹500 each. The retailer reports five of them damaged and sends all five back. The distributor wants the goods inspected before crediting anything, and does not want damaged units going back out to another customer. Follow the stock and the money separately — they do not move at the same time.
| Step | Document | Stock | Accounting |
|---|---|---|---|
| Original sale | Invoice for 100 @ ₹500 | 100 units gone | Receivable ₹50,000, revenue ₹50,000, COGS posted |
| Return raised | Returns order RE for 5, referencing the invoice | No change | Nothing — billing block 08 holds the credit |
| Goods on the way back | Returns delivery LR for 5 | No change | Nothing |
| Goods arrive | Goods receipt, movement type 651 | 5 units in blocked returns stock, not sellable | Nothing posts — blocked returns stock is non-valuated |
| Inspection | 3 resaleable moved with 453, 2 scrapped | 3 units sellable again, 2 written off | Inventory value returns for those 3 units only |
| Credit | Credit memo RE for 5 @ ₹500 | No change | Customer credited ₹2,500, revenue reduced |
The two details that matter: stock and money part company in the middle. The quantity is back at the goods receipt, but with movement type 651 it lands in non-valuated blocked returns stock — no accounting document, nothing sellable. The inventory value only returns when the usage decision moves 3 units to unrestricted with 453. And all five units are credited, including the two scrapped: whether goods can be resold is your problem, not the customer’s. Scrap is a cost you absorb, not a reduction of their credit.
Free download
Free: SAP SD Interview Starter Kit
A free sample of The SD Vault, sent to your inbox. No payment, no account.
- ✓25 most-asked interview questions, with full answers
- ✓1 complete configuration scenario, IMG paths and T-codes
- ✓A 7-day prep plan you can actually follow
One email with your kit. Occasional SAP SD tips after that — unsubscribe any time.
What happens to stock and money
This is where returns designs genuinely differ, and where most of the confusion lives. Two decisions:
Which stock do the goods land in?
SAP standard receives into blocked returns stock with movement type 651, so returned goods are not sellable until somebody looks at them. That stock is non-valuated: the goods receipt moves quantity only and creates no accounting document. After inspection they move to unrestricted with 453 — and that is the step where the inventory value comes back — or they are scrapped. Other configurations post the goods receipt straight into valuated stock, which is faster but trusts the return sight-unseen.
It is set on the schedule line category — DN in SAP standard — not on the order type.
When is the customer credited?
The billing block on the returns order holds the credit until somebody releases it. That is the approval gate: goods received, inspected, quantity confirmed, then credit. Remove the block from the order type and you have a process where customers can be credited for goods that never arrived.
Standard REN is billing relevance B, order-related, so the credit memo is created from the returns order via VTFA — which means an unposted goods receipt does not hold the credit back. Only the billing block does.
Both decisions have a finance consequence worth being able to state. With the standard 651 design, three things happen at three different moments: the quantity returns at the goods receipt, the inventory value returns when the goods are moved to unrestricted stock, and the revenue reduction happens at the credit memo. If those land in different periods, the margin in each period is distorted — which is why month-end so often brings a push to clear the returns backlog and make the usage decisions nobody got to.
Configuration
Returns order type RE
VOV8
In SAP standard: SD document category H, delivery type LR, billing type RE for the credit memo, and billing block 08 so credits need approval. Set reference mandatory if the business insists every return points at an invoice — the cheapest control there is against phantom credits.
Item category REN
VOV4 / VOV7
Determined from RE + NORM. The returns flag is set and pricing is taken from the referenced document through copy control. Billing relevance is B in SAP standard — order-related — so the credit memo is created from the returns order, not the returns delivery. That one field decides which copy control table the credit needs, so read it before designing around it.
Schedule line category
VOV5 / VOV6
DN in SAP standard, carrying movement type 651. This is where the blocked-versus-unrestricted decision is actually configured — not in the order type, and not in the item category.
Copy control: invoice → returns order
VTAF
The entry that lets a return be created with reference to the invoice. Set the pricing type so prices are copied unchanged — crediting at today’s price instead of the invoiced price is a genuine revenue leak.
Copy control: order → delivery → billing
VTLA and VTFA / VTFL
RE to LR for the returns delivery, and RE to RE in VTFA for the credit memo — VTFA because standard REN bills order-related. If your REN has been changed to delivery-related billing, the entry belongs in VTFL instead. A missing entry here is the classic "the return will not credit" ticket.
Order reasons
SPRO → Sales and Distribution → Sales → Sales Documents → Sales Document Header → Define Order Reasons
An order reason on the returns order is what makes returns analysable later: damaged, wrong item shipped, customer changed their mind. Without it you can count returns but never explain them. Reasons for rejection are a different field, used to kill a line that will not be credited at all.
None of this is exotic — it is the same sales document type, item category and copy control machinery as a normal order, pointed at documents that run in the opposite direction.
Returns vs credit memo request
Both end in a credit. Choosing the wrong one leaves either your inventory or your customer wrong.
| Returns order (RE) | Credit memo request (CR) | |
|---|---|---|
| Use it when | Goods are physically coming back | Only the money is wrong |
| Typical reason | Damaged, wrong item, over-delivered | Overcharge, pricing error, goodwill |
| Delivery | Returns delivery (LR) | None |
| Stock effect | Goods receipt brings stock back | None at all |
| Approval | Billing block on the returns order | Billing block on the request |
| Ends with | Credit memo after goods are received | Credit memo after approval |
There is a third option for a related case: the invoice correction request, which carries both a credit and a debit line so only the difference is posted — the right tool when an invoice was simply wrong and the goods are staying with the customer.
Lean returns vs Advanced Returns Management
SAP’s product documentation for SAP S/4HANA (on-premise), release 2025 documents two solution variants for customer returns, and knowing which one a client runs changes the whole conversation:
Lean Customer Returns
In SAP’s words, the core activities: creating a returns order, posting the goods receipt, and creating a credit memo. The returns order can reference an existing sales order or invoice, or be created without reference. Enough for a business whose returns are simple and whose goods go straight back into stock.
Customer Returns — advanced returns management
The end-to-end variant, which SAP also calls advanced returns management (ARM in customizing). It adds product inspections, logistical follow-up activities driven by the inspection result, and refund determination — so the customer can be compensated with a credit memo or a replacement through a free-of-charge delivery.
The advanced variant also covers scenarios the lean one does not: returns taken at a counter, returns that ship to a warehouse with reverse logistics afterwards, and goods sent directly from the customer to a supplier without ever entering your own stock.
Check before you design: in the lean variant SAP describes the goods receipt posting into valuated stock and the credit memo being created with reference to the returns delivery. The classic SD configuration many projects still run receives into blocked stock first and bills the credit memo from the returns order. Both are legitimate — read the item category’s billing relevance and the schedule line’s movement type in the system in front of you rather than quoting a textbook.
Troubleshooting
No returns delivery can be created
- ·The returns order type does not propose delivery type LR
- ·No copy control from RE to LR
- ·The item is not delivery relevant, or the schedule line category has no movement type
- ·A delivery block on the returns order
Fix: Check the delivery type on the order type first, then copy control. Returns use a returns delivery type — a returns order pointed at LF will not behave.
The credit memo will not be created
- ·The billing block on the returns order was never released — usually deliberate
- ·No copy control entry to the credit memo billing type
- ·REN has been set to delivery-related billing and the goods receipt has not been posted
- ·Billing relevance points at a document that does not exist yet
Fix: The billing block is the answer in most cases, and it is doing its job. If the block is clear, compare the item category’s billing relevance with what copy control actually supports: order-related billing (standard REN) needs a VTFA entry, delivery-related needs VTFL. Worth knowing: with standard order-related billing an unposted goods receipt does not block the credit — only the billing block does.
The credit is for the wrong amount
- ·The pricing type in copy control redetermined prices instead of copying them
- ·The return was created without reference to the original invoice
- ·A manual change to the quantity or conditions on the returns order
Fix: Credit at the price the customer was charged, not today’s price. That means creating with reference and using a pricing type that copies pricing elements unchanged.
The returned stock is available to sell when it should not be
- ·The goods receipt posted straight into unrestricted stock
- ·Nobody moved it onward after inspection
Fix: If returned goods must be inspected first, they should land in blocked stock and move to unrestricted only after a usage decision. Check the movement type on the schedule line category.
The customer returned less than they claimed
- ·Only the returns delivery quantity was corrected, not the returns order
- ·The undelivered difference was left open instead of being rejected
Fix: This is where standard REN catches people out. Because billing is order-related, the credit memo follows the returns ORDER quantity — correcting only the delivery leaves the credit too high. Reduce the quantity on the returns order as well, or reject the difference with a reason for rejection.
Returns cannot be reported on by reason
- ·No order reason is captured on the returns order
- ·The field is optional and users skip it
Fix: Make the order reason mandatory through the incompletion procedure. Without it you can count returns but never explain them.
Interview questions
Walk me through the returns process.
Returns order (type RE, SD document category H) created with reference to the original invoice, carrying billing block 08. Returns delivery (type LR) so the warehouse has something to receive against. Goods receipt with movement type 651, which brings the quantity back into blocked returns stock — non-valuated, so nothing posts to accounting yet. A usage decision then moves the goods to unrestricted with 453, and that transfer is where the inventory value actually returns. Finally the credit memo, once the billing block is released. The point worth saying out loud: stock and money move at different moments.
Why create the return with reference to the invoice?
So the credit is calculated at the price the customer actually paid. With a reference and the right pricing type in copy control, the conditions are copied unchanged. Without it, pricing is redetermined at today’s prices — if the price has risen since, you over-credit; if it has fallen, you short-change the customer and get a complaint.
Where is the billing block set and why?
On the returns order type in VOV8, so every return carries it automatically. It stops anyone crediting a customer before the goods have been received and inspected. Releasing it is the approval step, which is how most businesses control returns without workflow.
What is the difference between a return and a credit memo request?
A return means goods are physically coming back, so there is a returns delivery and a goods receipt. A credit memo request corrects money only — an overcharge, a pricing error, a goodwill gesture — with no stock movement at all. Choosing a credit memo request when goods are actually returning leaves the inventory wrong.
What happens to the stock when the goods come back?
That depends on the movement type on the schedule line category — DN with movement type 651 in SAP standard. That receives into blocked returns stock, which is non-valuated: the quantity is visible, but the goods are not sellable and nothing has posted to accounting. After a usage decision they move to unrestricted with 453, and that transfer is what brings the inventory value back. Some configurations post the goods receipt straight into valuated stock instead, in which case value returns at the goods receipt.
What does Advanced Returns Management add over the simple process?
SAP calls the two variants customer returns, known as advanced returns management, and lean customer returns. Lean covers the core: returns order, goods receipt, credit memo. The advanced variant adds product inspections, logistical follow-up activities based on the inspection result, and refund determination — so the customer can be compensated with a credit memo or a free replacement, and goods can be returned to a supplier rather than taken into your own stock.
More of these, graded by depth, in the SAP SD interview questions collection.
Where this sits in the SD landscape
Returns are the Order-to-Cash process reversed, built from the same parts: a sales document type with its blocks and proposed follow-on documents, item category determination for the returns item, and copy control to carry the original prices into the credit. Consignment has its own return path — see the consignment guide.
Frequently Asked Questions
What is the SAP SD returns process?
It is the after-sales flow for goods a customer sends back: a returns order (type RE), a returns delivery (type LR), a goods receipt that brings the stock back, and a credit memo that refunds the customer. It is normally started with reference to the original invoice.
Which document types are used in SAP SD returns?
In SAP standard: returns order type RE with SD document category H, returns delivery type LR, item category REN, schedule line category DN, and billing type RE for the credit memo. The returns order type also carries billing block 08 so the credit needs approval.
Why does the returns order have a billing block?
So nobody credits the customer before the goods arrive and are inspected. Billing block 08 is set on the RE order type in VOV8, applies automatically to every return, and releasing it is the approval step. With standard order-related billing it is the only thing holding the credit back.
What is the difference between a returns order and a credit memo request?
A returns order is used when goods physically come back — it creates a returns delivery and a goods receipt. A credit memo request corrects only the money, with no stock movement, and is used for overcharges, pricing errors and goodwill.
What movement type is used for customer returns?
It comes from the schedule line category — DN in SAP standard, carrying movement type 651. That receives the goods into blocked returns stock, which is non-valuated, so the goods receipt moves quantity only and posts no accounting document. Movement type 453 then transfers inspected goods to unrestricted stock, and that is where the inventory value returns. Other configurations post the goods receipt directly into valuated stock — check your schedule line category rather than assuming.
What is the difference between lean customer returns and Advanced Returns Management?
SAP documents two variants for SAP S/4HANA (on-premise) release 2025. Lean customer returns covers the core activities — returns order, goods receipt, credit memo. Customer returns, also known as advanced returns management, adds product inspections, logistical follow-up activities based on the inspection results, and refund determination including replacement by a free-of-charge delivery.
Can a customer return be created without reference to an invoice?
Yes, SAP supports creating a customer return without reference, for example in VA01. But without the reference, pricing is redetermined rather than copied, so the credit may not match what the customer paid. Many businesses make the reference mandatory on the returns order type.
How do you credit only the quantity actually returned?
Reduce the quantity on the returns ORDER, not just the returns delivery. Because standard REN bills order-related, the credit memo follows the returns order quantity — so correcting only the delivery leaves the credit too high. Either adjust the order quantity or reject the undelivered difference with a reason for rejection.
Written by
Rahul Narain Saxena
SAP SD Solution Architect with 17+ years of hands-on implementation experience across SAP ECC and S/4HANA. Every guide on The SD Vault is written from live project experience, not summarised from documentation.
“The customer returned 4 of the 5 they claimed. What does the credit show?”
Returns questions separate people who have run the process from people who have read the flow diagram. The SD Vault has 230+ depth-graded questions and 38 configuration scenarios, including returns with a quality decision, step by step.
Get Lifetime Access →Or start free with the sample pack, Order-to-Cash guide, and Copy Control guide.