Credit Memo: Correcting an Invoice Without Moving Goods

Business scenario

Demo Retail Pvt. Ltd. was invoiced ₹2,200 per EA for 50 EA of FG-2000 instead of the agreed ₹2,000. The goods are correct and the customer is keeping them — only the price is wrong, so ₹10,000 has to be credited.

All companies, numbers and documents are fictional demo data.

Step-by-step flow

1. 01

   Customer disputes the price open in twin

   Demo Retail was billed ₹2,200 per EA instead of ₹2,000. The goods are fine and they are keeping them.

   This is the defining feature of the credit memo process. Because no goods are involved, there is no returns order, no delivery and no goods movement anywhere.

2. 02

   Credit memo request is created open in twin

   Request 70000222 (type CR) is created with reference to the invoice — and is blocked for billing immediately.

   Creating it with reference to the invoice copies the original pricing, so the correction is calculated against what was actually charged rather than typed in by hand.

3. 03

   The request is blocked open in twin

   A billing block sits on the request. Decide how to deal with it.

   A credit memo reduces revenue and reduces what a customer owes. That is money leaving the company, so it is deliberately gated behind an approval.

4. 04

   Credits without approval open in twin

   Removing the block lets anyone who can create a credit memo request reduce a customer's balance unchecked.

   The problem is not technical, it is control. The automatic billing block on credit memo request types exists so that creating a credit and approving a credit are two different people's jobs — the same separation-of-duties principle behind release strategies in purchasing.

5. 05

   Review and release the block open in twin

   Credit control checks the invoice against the agreed price, confirms ₹10,000, and releases the block.

   Releasing the block is the approval. From this moment the request appears in the billing due list and the credit can be issued.

6. 06

   Credit memo is billed open in twin

   Credit memo 90002000 (type G2) credits ₹10,000 — revenue down, customer balance down.

   The credit memo is the mirror of an invoice: where an invoice debits the customer and credits revenue, this credits the customer and debits revenue.

7. 07

   Correction complete open in twin

   Invoice → credit memo request → approval → credit memo. Three documents, zero goods movements.

   Keeping the correction as its own document chain — rather than cancelling and reissuing the invoice — preserves the history of what was charged, disputed and credited.

SAP documents

Stock impact

This part of the process does not change stock.

Accounting impact

Movement type

This flow spans several documents rather than a single movement type.

Corrects the value of a sale after invoicing — a pricing error, an agreed discount, a goodwill gesture — without any goods coming back and without cancelling the original invoice.

Transactions & Fiori apps

Configuration

• Automatic billing block on order type CR

  Typical

  The approval control for the whole process. Standard configuration sets it; removing it is a significant internal-control decision.

• Copy control (invoice → CR → G2)

  Configuration dependent

  Controls what may be referenced and copied, including whether pricing is re-determined or copied unchanged from the original invoice.

• Account key on the credit condition

  Configuration dependent

  ERL posts against revenue, ERS against sales deductions. Which one is used decides whether the credit nets off revenue or shows separately.

• Credit memo versus invoice cancellation

  Typical

  Cancelling (VF11) undoes the invoice entirely and is right for a wrong invoice. A credit memo leaves the original standing and corrects it — right when the invoice was issued correctly but the amount must change.

• Debit memo request (DR)

  Typical

  The exact opposite process for undercharging: order type DR, billing type L2, posting Dr Customer / Cr Revenue.

Prerequisites

• Credit memo request order type (CR) configured with an automatic billing block
• Copy control from the billing document to the credit memo request, so it can be created with reference
• Copy control from order type CR to billing type G2
• Order reasons maintained for reporting on why credits are issued
• Authorisation split: who may create a request versus who may release the block

Master data

Customer / business partner

The credit reduces this customer's balance; sales area data drives pricing on the request.

Pricing condition records

Determine the correct price, which is what the disputed invoice is compared against.

Order reasons

Essential reporting: how much is being credited, to whom, and why.

Organizational structure

• Company code 1000
• Sales organization 1000, distribution channel 10, division 00
• No plant, storage location or shipping point is involved — nothing physical happens

Tables

Integration

• FIThe credit memo posts the revenue reduction and reduces the customer's open balance in accounts receivable.
• COReduces revenue in profitability analysis, so credits show up in margin per customer — which is how systematic pricing problems get noticed.

Common errors

• “Credit memo cannot be created from the request”

  Likely causes: Billing block still set; Copy control missing between order type CR and billing type G2; Request already fully billed

  Where to look: Request billing block field · Copy control configuration · Document flow of the request

• “Credit posted to the wrong account”

  Likely causes: Condition uses ERL where ERS was intended, or vice versa; VKOA condition record missing for the account key

  Where to look: Account determination analysis in the credit memo · Pricing procedure account keys · VKOA records

• “Credit value is wrong”

  Likely causes: Request created without reference, so pricing was entered manually; Copy control re-determined pricing instead of copying it; Quantity on the request does not match the disputed quantity

  Where to look: Reference document on the request · Copy control pricing type · Request item quantity and conditions

• “Tax was not credited”

  Likely causes: Tax condition not copied into the request; Manual value entered on a net condition only

  Where to look: Pricing conditions on the credit memo · Tax condition records

Troubleshooting

Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.

1. CHECK 1

   Cannot bill the credit

   • Is the billing block released?
   • Is copy control maintained from CR to G2?
   • Has the request already been billed?

2. CHECK 2

   Wrong value

   • Was the request created with reference to the invoice?
   • Does copy control copy pricing or re-determine it?
   • Does the quantity match the dispute?

3. CHECK 3

   Wrong accounts

   • Run account determination analysis on the credit memo
   • Which account key does the condition use — ERL or ERS?
   • Are VKOA records complete for that key?

4. CHECK 4

   Control review

   • Does order type CR still have an automatic billing block?
   • Can any single user both create and release a credit memo request?
   • Are order reasons mandatory?

Interview questions

• What is the difference between a credit memo request and a credit memo?

  The request (order type CR) is a sales document: it records what should be credited, why, and against which invoice, and it normally carries an automatic billing block. The credit memo (billing type G2) is the billing document created from the released request; it is what actually posts to accounting and reduces the customer's balance. The request is the proposal, the memo is the execution.

• Why does a credit memo request carry an automatic billing block?

  Because it reduces revenue and reduces what a customer owes — effectively giving money away. The block forces a separate, authorised person to review and release it, so creating a credit and approving it are different jobs. Credit memo types without a billing block, or users who can both create and release, are standard audit findings.

• When would you cancel an invoice instead of issuing a credit memo?

  Cancel (VF11) when the invoice itself should not exist — wrong customer, duplicate, billed in error — because cancellation reverses it completely. Issue a credit memo when the invoice was legitimately raised but the amount needs correcting, such as a pricing error or an agreed discount. The credit memo keeps the original invoice and its history intact, which is usually what auditors and customers both prefer.

• Does a credit memo ever move stock?

  No. A credit memo is a pure value document with no delivery and no goods movement. If goods are physically coming back, that is a returns process: a returns order, a returns delivery and a goods receipt (651 or 653), which then produces its own credit. Price-only disputes use a credit memo and nothing moves.

• A customer was undercharged. What is the process?

  The mirror image: a debit memo request (order type DR) billed as a debit memo (billing type L2). It increases the customer's balance and revenue, posting Dr Customer receivable / Cr Revenue. It is configured the same way, usually including an approval block.

Quiz

Related processes

• 601Order to Cash
• 651 · 453 · 653Customer Returns
• FlowThird-Party Sales

References

• SAP SE — SAP Help Portal: Credit and Debit Memo Requests (source)
• SAP SE — SAP Help Portal: Complaints Processing (source)
• SAP SE — SAP Help Portal: Revenue Account Determination (source)

Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.

Version history