Study guide
8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows
SAP S/4HANA Sales C_TS462
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure
1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration
2 Chapter 2: The Order-to-Cash Process and Sales Master Data
2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling
3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements
3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries
4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs
4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders
5 Chapter 5: Pricing and the Condition Technique
5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement
6 Chapter 6: Availability Check (ATP) and Delivery Scheduling
6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements
7 Chapter 7: Delivery Processing and Embedded EWM
7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries
8 Chapter 8: Billing and Integration with Financial Accounting
8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options
9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output
9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables
10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core
10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels
11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition
11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM
8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows
Key Takeaways Explain This Topic AI
Credit and debit memo requests (CR, DR) can be created without reference, with reference to an order, or with reference to the invoice; referencing the invoice copies its prices and links the document flow.
Credit and debit memo requests can receive a billing block automatically (standard block 08 for credit memo requests), so a responsible employee must release them before billing.
The customer returns workflow coordinates the Returns Order (RE), Returns Delivery (LR), and Goods Receipt (PGR) before generating the Credit for Returns billing document.
Down payment requests (billing type FAZ) are posted in FI as noted items with special G/L indicator F; payments are posted with indicator A and cleared in the final invoice through condition AZWR.
Cancellation with VF11 creates cancellation billing type S1 (for F2), posts an offsetting accounting document, and reopens the preceding documents for billing.
Last updated: October 2026
Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows
In enterprise Order-to-Cash processing, commercial operations do not end with the creation of an initial customer invoice. Commercial disputes arise from pricing discrepancies, volume rebates, damaged merchandise, or incorrect tax calculations. High-value capital manufacturing projects require structured customer down payments prior to fabrication. Furthermore, operational errors occasionally mandate the complete statutory reversal of an issued invoice.
To address these business requirements, SAP S/4HANA provides robust, audit-compliant workflows for Credit and Debit Memo Requests , Customer Returns Processing , Down Payment Requests , and Invoice Cancellations . Understanding the controls, document flows, and financial impacts of these processes is essential for maintaining commercial integrity.
Credit and Debit Memo Requests ( CR / DR )
When a customer disputes an invoice—such as reporting that an agreed 5% promotional discount was omitted or that unit prices were misquoted—the enterprise must adjust the customer's balance. In SAP, billing adjustments are never made by manually editing a posted invoice. Instead, the enterprise executes a controlled Credit Memo Request ( CR ) or Debit Memo Request ( DR ) . Dispute / Pricing Error Identified
- │
- ▼
- [ Create with Reference to Invoice F2 (VA01) ] ──> Copies Pricing & Partners
- │
- ▼
- [ Credit Memo Request (CR) Created ] ────────────> Default Billing Block Active (08)
- │
- ▼
- [ Managerial Audit & Approval ] ─────────────────> Remove Billing Block (VA02 / Fiori)
- │
- ▼
- [ Billing Execution (VF01 / VF04) ] ─────────────> Order-Related Billing (Item Cat G2N, FKREL C)
- │
- ▼
- [ Credit Memo Document (G2) Issued ] ────────────> Updates Universal Journal ACDOCA
- Credit Customer AR
- Debit Revenue / Deductions
- Creating the Request with Reference
According to the official billing course, credit and debit memo requests can be created without reference, with reference to an order, or with reference to a billing document. Creating them with reference to the original invoice ( F2 ) is good practice:
Data Integrity : Referencing copies the exact original pricing conditions, currency, exchange rate, customer account assignment groups, and tax codes into the request.
Fewer Errors : The user only adjusts the quantity or value to be credited instead of entering the whole document again.
Audit Trail : Establishes an unbroken link in the SAP Document Flow ( VBFA ), enabling auditors to trace adjustments back to the original sales order and delivery.
Internal Governance: The Default Billing Block ( VOV8 )
Because issuing a credit memo directly decreases enterprise revenue and reduces customer accounts receivable, organizations must enforce segregation of duties. Sales representatives who enter customer complaints should not have the authority to unilaterally disburse corporate funds.
In customizing for sales document types (transaction VOV8 ), document types CR and DR are preconfigured with a Default Billing Block ( VBAK-FAKSK ):
Standard default block: 08 (Check credit memo).
When the request is saved, it enters the system with billing status Blocked .
The Billing Due List ( VF04 / VF06 ) will systematically refuse to process the document.
An authorized sales manager or financial controller must review the commercial claim and remove the billing block (using transaction VA02 or the list of documents blocked for billing, V.23 ).
Once released, the request enters the billing due list and generates a Credit Memo ( G2 ) or Debit Memo ( L2 ) through order-related billing (item categories G2N / L2N , billing relevance C ).
Customer Returns Processing Workflow ( RE )
When a customer physically returns damaged, defective, or unwanted merchandise, the business must execute a two-pronged workflow coordinating Logistical Physical Receipt with Financial Commercial Crediting . 1. Returns Order (RE) Sales Order type RE created with reference to Invoice F2.
Carries default billing block to hold credit.
- │
- ▼
2. Returns Delivery (LR) Returns delivery (delivery type LR) created without picking.
(Picking status KOSTA is not relevant).
- │
- ▼
3. Post Goods Receipt (PGR) Warehouse posts goods receipt (Movement Type 651 or 653).
Increments Returns Stock; decrements customer possession.
- │
- ▼
4. Inspection and Release Goods inspected: scrap, repair, or return to unrestricted stock.
The responsible employee removes the billing block.
- │
- ▼
5. Credit for Returns (RE) Billing document type RE issued via VF01/VF04.
Credits customer AR; debits revenue; closes document flow.
Returns Workflow Stages
Stage Document / Transaction Key Configuration & System Action
1. Returns Order RE (Trans. VA01 ) Created with reference to invoice F2 . Item category REN . Automatically assigns default billing block 08 (Check credit memo).
2. Returns Delivery LR (Trans. VL01N ) Delivery document type LR . Does not require warehouse picking ( KOSTA = blank ). Generates shipping paperwork.
3. Post Goods Receipt PGR (Trans. VL02N ) Posts goods receipt with movement type 651 (blocked stock for returns), the movement type of schedule line category DN ; other movement types such as 653 (unrestricted use) can be configured. Creates a material document.
4. Release Billing Block VA02 / Fiori app Once physical goods are verified at the warehouse, supervisor removes the billing block.
5. Credit for Returns RE (Trans. VF01 ) Billing document type RE generated. Posts credit to Customer AR and debit to Sales Returns / Revenue in ACDOCA .
Note
In SAP S/4HANA, standard returns can be enhanced using Advanced Returns Management (ARM) (document type CBAR ). ARM automates customer replacement orders, vendor returns, logistical follow-up activities, and immediate or delayed credit memo creation from a centralized coordinator dashboard.
Down Payment Processing in Sales
In capital equipment manufacturing, engineering-to-order projects, and high-value wholesale transactions, manufacturers require customers to pay advance deposits (e.g., 20% upon contract signing, 30% upon engineering completion) before assembly or shipping begins. Standard invoicing cannot be used because revenue cannot legally be recognized before fulfillment.
SAP S/4HANA integrates sales orders with Financial Accounting using Milestone Billing Plans and Down Payment Requests .
The Milestone Billing Plan Architecture
A milestone billing plan is assigned to the sales order item (item category with billing relevance FKREL = I ). The plan defines a schedule of commercial milestones:
- Milestone 10 : Order Confirmation → 20% Down Payment
- Milestone 20 : Completion of Assembly → 30% Down Payment
- Milestone 30 : Delivery & Acceptance → Final Invoice (100% value minus 50% down payments cleared)
- The Down Payment Request ( FAZ ): Statistical Noted Item
When Milestone 10 is reached, the billing clerk generates billing document type FAZ (Down Payment Request):
Statistical Document : FAZ is a purely statistical billing document. It does not recognize revenue, and it does not update normal accounts receivable in ACDOCA .
Noted Item in FI : In Financial Accounting, FAZ generates a Noted Item (Special G/L Indicator F ). A noted item is an informational record that does not alter balance sheet totals or consume customer credit limits, but it appears on customer account statements as an advance payment demand.
Incoming Cash Receipt (FI Posting)
When the customer pays the advance deposit, financial accounting posts the incoming bank receipt (transaction F-29 or Fiori app Post Incoming Payments ):
The noted item ( F ) is cleared.
A true down payment receipt is posted with Special G/L Indicator A :
- Debit : Bank / Cash Account ($20,000)
- Credit : Customer Special G/L Down Payments Received ($20,000)
- The Final Invoice ( F2 ) and Down Payment Clearing ( AZWR )
When goods are delivered, the final commercial invoice ( F2 ) is created for the total sales order value ($100,000):
The system detects previously posted down payments linked to the sales order.
The pricing engine automatically inserts condition type AZWR (Down Payment Clearing) into the billing item pricing screen.
Condition AZWR deducts the $20,000 previously received from the invoice payable balance.
Net Due Payable from Customer : $80,000.
Financial Accounting Entry :
- Debit: Customer Regular AR ($80,000)
- Debit: Customer Special G/L Down Payments Cleared ($20,000)
Credit: Gross Operating Revenue ($100,000) +--------------------------------------------------------------------------+
- | Complete Down Payment Accounting Lifecycle |
- +--------------------------------------------------------------------------+
- | Step 1: Issue Down Payment Request (Billing Type FAZ) |
- | FI Posting: Noted Item (Special G/L Indicator F) |
- | (Informational only; no balance sheet change) |
- |--------------------------------------------------------------------------|
- | Step 2: Customer Advances Cash (FI Transaction F-29) |
- | Dr. Cash / Bank \$20,000 |
- | Cr. Customer Down Payments Received (SGL A) \$20,000 |
- |--------------------------------------------------------------------------|
- | Step 3: Goods Delivered & Final Commercial Invoice Issued (Type F2) |
- | Base Price PR00: \$100,000 |
- | Down Payment Clearing AZWR: -\$20,000 |
- | Invoice Net Due Payable: \$80,000 |
- | |
- | FI Journal Entry: |
- | Dr. Customer Regular AR \$80,000 |
- | Dr. Customer Down Payment Cleared (SGL A)\$20,000 |
- | Cr. Sales Revenue (Gross) \$100,000 |
- +--------------------------------------------------------------------------+
- Invoice Cancellation Workflows (Transaction VF11 )
In commercial enterprise operations, invoices are occasionally issued with erroneous pricing, incorrect delivery addresses, or invalid tax classifications. Because a posted invoice represents an immutable statutory legal document, a billing document in SAP can never be physically deleted from database tables VBRK / VBRP .
To reverse an incorrect invoice, the business executes an Invoice Cancellation using transaction VF11 .
Cancellation Mechanics in VF11
Document Entry : The user enters the billing document to be cancelled in VF11 . The system branches to an overview that shows the original billing document and the cancellation document side by side, so both can be compared before saving.
Cancellation Billing Type : The billing type of the original document names its cancellation type: invoice F2 is cancelled with S1 , credit memo G2 with S2 , and a cash sale with SV .
Reversal Accounting Document : The cancellation posts an accounting document with the opposite signs: it credits the customer receivable and debits revenue and output tax. With the negative posting indicator in the billing type (and if the company code allows it), cancellations and credit memos can instead be posted on the same side as the original, so the account totals return to zero (see section 8.7).
Reopening the Preceding Documents : The billing status of the preceding delivery or order item is set back to not yet billed , so the document reappears in the billing due list and can be billed again after the correction.
Cleared Invoices
An invoice whose receivable has already been cleared (for example, because the customer paid it) can still be cancelled in SD. The cancellation's accounting document cannot clear the original item, because that item is already cleared, so it remains as an open credit item on the customer account. Accounts receivable must then clear it manually, for example against a new invoice or by refunding the customer.
Credit Memo Request Workflow and Rejections
Credit memo requests are usually blocked for billing when they are created. The responsible employee can release the request (deciding the amount or quantity to credit) or reject items with a reason for rejection ; the reason controls whether the item is copied into the credit memo with zero value or not at all. With the Manage Credit Memo Request Workflow app (based on SAP standard workflow WS00800286 ), approvers are determined by value thresholds, requests below a minimum value can be released automatically, and managers receive the approval tasks in My Inbox .
Invoice Correction Requests
An invoice correction request corrects quantities or prices of an existing invoice in one document. It is created with reference to the invoice and contains item pairs: a credit item for the original values and a debit item for the corrected values. For a quantity difference (for example, damaged goods), the quantity to bill is corrected in the debit item; for a price difference , the pricing elements are corrected in the debit item. Unchanged item pairs can be removed in one step with Delete unchanged items . The result is billed as a credit memo for the difference.