Sales are not a straight line from order to invoice; returns, price corrections and under-billing are part of the process too. If SAP SD returns and credit/debit memo processes are not designed well, unexplained differences appear in accounting and disputes arise with customers.
Three needs, three documents
- Return order: the customer physically sends goods back. A returns delivery and goods receipt follow, and then a credit memo.
- Credit memo request: goods do not come back but money is refunded, for example for a pricing error, a discount on damaged goods or a late-delivery penalty.
- Debit memo request: an under-billed amount is charged to the customer, for example missing freight or a price difference.
Why a reference document is essential
Return and credit memo documents should be created with reference to the original invoice whenever possible. A referenced document takes customer, material, quantity and price from the original. Without a reference, the price is recalculated from today's condition records and the customer may be refunded a different amount from what they paid. This is controlled by the pricing type in copy control; see the pricing procedure article for details.
Approval blocks: who, up to which amount?
Because credit memo requests mean money going out, they are usually created with a billing block. A credit memo cannot be issued until an authorised person reviews the request and removes the block. Defining different approvers by amount thresholds gives both control and speed. These authorisations should follow segregation of duties: the person who creates a request should not approve it.
Stock status of returned goods
Returned goods do not always go back into unrestricted stock. Returns needing inspection go to quality inspection stock, damaged goods to blocked stock. The movement type and stock type at goods receipt should reflect that decision. Which cost the returned goods enter stock at (original cost of sale or current cost) should be agreed with accounting. These steps are a direct part of SD–MM–FI integration.
Reason codes and reporting
Make an "order reason" mandatory for every return and credit memo: pricing error, damaged product, wrong product, customer cancelled… Without these codes, returns are just a cost line; with them, they become a valuable data source showing which product, customer or process causes problems. Tracking returns separately in CO-PA shows true profitability.
Common mistakes
- Creating returns without a reference document and issuing credit memos at a different price
- Creating credit memo requests without a billing block
- Putting returned goods into unrestricted stock without inspection
- Leaving the reason code optional and being unable to analyse returns
Returns are the most sensitive moment of the customer experience. Building a process that is fast but controlled is one of the most overlooked yet most appreciated parts of SAP SD consulting.
