SAP Returns

A return typically starts with a returns order (a special order type), followed by a return delivery (goods received back into stock, often into a returns/blocked stock) and a credit memo (refunding the customer, posting to FI-AR). Each step reverses the corresponding outbound step.

One variation worth knowing: a returns delivery can be created without a preceding returns order in some configurations, which is faster at the goods receipt and gives up the approval and the pricing reference. It exists for high-volume consumer returns where speed matters more than control, and using it by accident is a different matter.

• Returns order type (e.g. RE).
• Return delivery & goods receipt back into stock.
• Credit memo to refund the customer.
• Inspection/disposition of returned goods (with QM).

A return looks like a sale in reverse and behaves differently in three ways that account for most of the difficulty.

The goods may not be resaleable. A return receipt into unrestricted stock assumes the item is fine. Frequently it is not, and the decision belongs to somebody who has looked at it. That is why returns are often received into blocked stock or into quality inspection, with a usage decision afterwards, rather than straight back into sellable inventory.

The credit is a separate decision from the receipt. Goods arriving does not automatically mean the customer is owed the full amount. Restocking charges, damage, or a return outside the agreed window all change the number, which is why the credit memo request usually carries a billing block until somebody releases it.

Value has to reverse consistently. Inventory goes up at the cost it left at, revenue reverses at what was billed, and if the return references the original documents those numbers are found rather than retyped. A return created standalone, with no reference, is where the mismatches start.

The design instruction that follows: create returns with reference to the original order or invoice wherever possible. It carries the pricing, the quantities and the document flow, and it is the difference between a clean reversal and a reconciliation exercise.

Half an hour, and it covers the inventory and finance halves together.

1. Find a completed sales order with a delivery and an invoice.
2. Create a returns order with reference to the invoice. The material, quantity and pricing come across.
3. Create the return delivery and post goods receipt. Stock comes back, and an accounting document reverses the cost of sales.
4. Check where the stock landed: unrestricted, blocked or inspection, depending on configuration.
5. Release the billing block and create the credit memo. Revenue and the receivable reverse.
6. Open the document flow on the original order. Order, delivery, invoice, return, return delivery, credit memo, all linked.

Step six is what makes a return auditable, and it is the reason for creating with reference rather than standalone.

Returns affect inventory (stock coming back), finance (credits reducing revenue/AR), and often quality (inspecting returned goods). Handling them cleanly ensures accurate stock and financials and good customer experience. Advanced returns management provides richer control for complex return scenarios.

Returns are also a measure worth watching. A rising return rate for one material or one customer is telling you something about quality, about how the product is being described, or about how it is being sold. That analysis is only possible if return reasons are coded consistently, which is a small discipline at entry with a large payoff in reporting.

• Where returned stock is received. Blocked or inspection by default is safer; unrestricted is faster and assumes everything comes back saleable.
• Whether credit requires approval. A billing block on the credit memo request makes it a decision; no block makes it automatic.
• Return reasons. A short coded list people actually use beats a long one they ignore, and it is what makes the reporting possible.
• Returns authorisation. Whether a customer may return without asking, which is a commercial policy the system then enforces.

A physical return is one of several ways a sale is adjusted afterwards, and choosing the right one keeps inventory and finance consistent.

Return. Goods come back. Stock rises, revenue and cost both reverse.

Credit memo. Value is reduced with no goods movement. A price adjustment, a goodwill gesture, a shortfall the customer accepted rather than returned. Created from a credit memo request so it can be approved.

Debit memo. The reverse: an undercharge corrected, which nobody enjoys sending and which is the correct document.

Invoice correction request. Handles a price or quantity error against an existing invoice in one document, showing the original and the corrected values, which is cleaner for a disputed invoice than a credit and a reissue.

Subsequent delivery free of charge. Where goods were damaged and the customer wants replacements rather than money. Stock leaves, no revenue.

The test to apply is what actually happened: did goods move, did money change, or both. Each answer has one right document, and the mismatches that make reconciliation painful come from choosing by habit rather than by that question.

The finance half of a return gets the attention and the inventory half is where the value quietly goes wrong.

Where it lands. Return receipt can go to unrestricted, to blocked, or to quality inspection, and the choice is configuration per return type. Unrestricted assumes everything comes back saleable, which is optimistic for most businesses.

At what value. Stock returns at the current valuation rather than at what the customer paid, so on a standard price material the accounting is clean, and on a moving average material the return moves the average. That effect surprises people the first time a large return shifts the price of everything in stock.

Batch and serial numbers. Where these are managed, the return should reference the original batch, or traceability breaks. A return received against a new batch number severs the link between what shipped and what came back.

Scrapping. Where the goods are not resaleable, the decision is a write-off rather than a stock movement, and it needs its own authorisation because it destroys value.

The instruction that covers most of it: decide where returned stock goes before go-live rather than letting each return be a judgement, because the default is unrestricted and it is usually the wrong answer.

• Returned stock not received correctly, inventory wrong.
• Credit memo not linked to the return, accounting off.
• No inspection/disposition of returned goods.

• Credit issued before the goods arrive. Occasionally right as a commercial gesture, and it should be a decision rather than the default sequence.
• Returns created standalone. Pricing is retyped, the document flow is broken, and nothing reconciles.
• Returned stock never inspected. See the delivery, shipping, sales orders and output for the forward flow this reverses.

• Return reasons left uncoded. The reporting that would tell you which product or which customer is driving returns becomes impossible.

Processing a return is straightforward, and configuring the stock destination, blocks and reason codes so returns are controlled and measurable is the part you do in the course.

The instruction that prevents most returns problems: create with reference to the original document. It carries pricing, quantities and the document flow, and it is the difference between a clean reversal and a reconciliation exercise.