SD / O2Cadvanced

SD Billing Part 5: Cancellation, Credit Memos and Debit Memos

Key takeaway

Correct invoices the right way: cancellation (VF11) with S1/S2, credit memo requests (CR → G2) and debit memo requests (DR → L2) with approval blocks, returns credit memos (RE), invoice correction requests (RK), and the FI and document-flow effects of each.

Explanation

📌 KEY POINTS
✅ Cancellation (VF11) reverses an invoice completely with S1 (or S2 for credit memos); the original becomes billable again if the delivery remains.
✅ Credit memo requests (CR) and debit memo requests (DR) are sales documents — usually with a billing block for approval — billed into G2/L2.
✅ Returns (RE) credit is billed after the returns delivery or order, depending on the process.
✅ Invoice correction request (RK) corrects quantities/prices of an invoice item by item (credit and debit lines).
⚠️ Cancelling an invoice to "fix a price" also reverses tax and receivables and may reopen follow-on steps — use credit/debit memos for partial corrections.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 4 covered volume billing. Now corrections.

━━━━━━━━━━━━━━━━━━━━
▶ 1. CANCELLATION

VF11: creates S1 with reference; FI document reversed and cleared (if open).
Only full cancellation of the whole invoice (or selected items, depending on release/config).
Delivery becomes billable again.\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 2. CREDIT MEMO REQUEST (CR → G2)\n• Created with reference to invoice or order; reason code (order reason).
Billing block for approval, release by authorized user.
Order-related billing into G2.\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 3. DEBIT MEMO REQUEST (DR → L2)\n• Additional charges (price increase, freight).
Same approval pattern.

━━━━━━━━━━━━━━━━━━━━
▶ 4. RETURNS AND INVOICE CORRECTION

RE: returns order → returns delivery → credit memo RE (billing relevance per item category).
RK invoice correction request: credit old item, debit corrected item in one document.

━━━━━━━━━━━━━━━━━━━━
▶ 5. FI AND CONTROLS

Credit memos create customer credits (cleared against invoices).
Reason codes for reporting; approval thresholds via blocks/workflow.
Credit memos with reference keep pricing via copy control (pricing type D).

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

Cancel an invoice with VF11 and check FI clearing.
Create a CR for a price complaint with billing block; release and bill.
Create an RK invoice correction and compare.

✅ CHECKPOINT: you choose cancellation, credit memo or invoice correction correctly for each complaint type.

Code example

ABAP Code

===== STEP 1: correction options =====Wrong invoice entirely          → VF11 cancel (S1) → correct → rebillPrice too high (partial)        → CR credit memo request (ref. invoice) → release block → G2Additional charge               → DR debit memo request → L2Quantity/price correction item  → RK invoice correction request → credit + debit linesGoods returned                  → RE returns order → returns delivery → RE credit memo ===== STEP 2: approval =====VOV8 CR: default billing block 08 (check credit memo) | release VA02 / V.23 list by authorized userOrder reason (reason code) mandatory for reporting ===== STEP 3: copy control =====VTAF F2 → CR (billing → sales doc) | VTFA CR → G2 | VTFF F2 → S1 (cancellation handled by VOFA)

Real project scenario

A company cancelled and rebilled invoices whenever a customer disputed any line. This doubled invoice volume, reset payment terms and confused customers' accounts payable. The team introduced credit memo requests with reason codes and approval for price disputes, and invoice correction requests for quantity/price corrections. Cancellations were restricted to genuinely wrong invoices, and dispute reporting by reason code became possible.

Common mistakes

Cancelling invoices for partial corrections.
Credit memo requests without approval blocks.
No reason codes for credits.
Repricing credit memos with new pricing instead of copying invoice prices.
Ignoring FI clearing after cancellation.

Best practices

Use the right correction document per case.
Enforce approval and reason codes.
Copy pricing unchanged for credits with reference.
Monitor credit memo volumes by reason.
Coordinate with AR on clearing.

Interview angle

Questions: "Difference between cancellation and credit memo?", "How is a credit memo request approved?", "What is an invoice correction request?"
Strong answer: VF11 S1 full reversal vs CR→G2/DR→L2 for partial corrections with billing block approval and reason codes; RK credits and debits items; returns credit RE; FI effects and pricing type D for references.

Practice this lesson

Quick check

1. An invoice contained the correct delivery but one price was too high. What is the appropriate correction?

2. What best describes the functional difference between a credit memo request and a direct credit memo in SD billing?

3. When a billing document is cancelled using a cancellation billing type, what is the standard system behavior?

Interview questions

1. What is the difference between a debit memo billing type and a credit memo billing type in SD, and how does the system determine which one to use?

Answer it in your own words first, then compare.

2. Customers dispute individual invoice lines, and the team cancels and rebills whole invoices each time. How would you redesign complaint handling?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.