C_TS410_2022 Lead to Cash Processing

Lead to Cash Processing Detailed Explanation

The Lead to Cash process in SAP S/4HANA manages the complete sales cycle, starting from capturing customer leads and inquiries to delivering goods/services and collecting payments. This end-to-end process ensures timely fulfillment of customer needs while enabling accurate financial tracking and reporting.

As a beginner, understanding this cycle is crucial because it involves multiple steps, key data, and integrations with other SAP modules like Financial Accounting (FI), Controlling (CO), Materials Management (MM), and Sales and Distribution (SD).

6.1 Key Steps in the Sales Process

The Lead to Cash process can be divided into six main steps. Each step connects to SAP tools and transaction codes that you will use in a real-world scenario.

1. Opportunity and Inquiry

• Definition: This is the initial stage where customer leads, inquiries, and opportunities are captured in SAP.
• Purpose: Understand customer requirements, analyze potential sales opportunities, and determine the feasibility of fulfilling the customer's needs.

Key Tools:

• SAP Customer Relationship Management (CRM): Used to manage customer leads and opportunities.
• Inquiry Documents: A formal customer request for information, prices, or product details.

Steps:

1. A salesperson captures a lead (potential customer).
2. Customer makes an inquiry for specific products or services (e.g., asking for price and delivery times).

Example:

• A customer contacts your company asking for 500 laptops. This inquiry is recorded in SAP, capturing key details:
  • Customer Name: ABC Corp
  • Product: Laptops
  • Quantity: 500
  • Delivery Date: 30 days from inquiry

2. Quotation Management

• Definition: A Quotation is a formal offer sent to the customer that includes product pricing, delivery dates, and terms.
• Purpose: Provide customers with accurate information to make a purchase decision.

Key Steps:

1. The Sales Department generates a quotation based on the inquiry.
2. Pricing is determined using Pricing Conditions.
3. The quotation is sent to the customer for approval.

Transaction Code:

• VA21: Create Quotation

Example:

• Quotation for 500 laptops:
  • Unit Price: $1,000 per laptop
  • Total Amount: $500,000
  • Delivery: 30 days from order confirmation
  • Validity: 15 days

Quotation Process Flow:

1. Inquiry → Create Quotation (VA21) → Send to Customer → Wait for Approval.

3. Sales Order Management

• Definition: A Sales Order is created when the customer accepts the quotation. It formalizes the agreement between the company and the customer for product delivery.
• Purpose: Trigger the production or procurement of goods and ensure fulfillment.

Key Activities:

1. Create Sales Order: Based on the accepted quotation.
2. Pricing: Confirm product prices and apply any discounts.
3. Availability Check: Verify that the required products are in stock or plan production/procurement.
4. Partner Determination: Assign roles like Sold-to Party (customer), Ship-to Party, Bill-to Party, and Payer.

Transaction Code:

• VA01: Create Sales Order

Steps to Create a Sales Order:

1. Enter customer details (Sold-to Party).
2. Enter material and quantity details.
3. Verify pricing, availability, and delivery date.
4. Save the Sales Order.

Example:

• Sales Order for 500 laptops:
  • Customer: ABC Corp
  • Product: Laptop
  • Quantity: 500
  • Price: $1,000 per unit
  • Delivery Date: 30 days

System Output:

• The system generates a Sales Order Number (e.g., SO1001).
• Inventory and production planning are triggered to fulfill the order.

4. Outbound Delivery Processing

• Definition: The Outbound Delivery process involves preparing and shipping the ordered products to the customer.
• Purpose: Ensure timely delivery of goods while maintaining accurate inventory records.

Key Steps:

1. Picking: Select the goods from inventory to fulfill the sales order.
2. Packing: Pack the goods for shipment.
3. Post Goods Issue (PGI): Update inventory and record that goods have been shipped to the customer.

Transaction Code:

• VL01N: Create Outbound Delivery

Process Flow:

1. Picking:

   • Warehouse staff picks 500 laptops from stock.
   • Inventory is reduced temporarily during picking.

2. Packing:

   • The laptops are packed securely for delivery.

3. Post Goods Issue (PGI):

   • Once goods are shipped, SAP updates:
     • Inventory Levels: Reduces stock by 500 laptops.
     • Financial Accounting: Records goods movement (cost of goods sold).

Example Accounting Entry during PGI:

• Debit: Cost of Goods Sold (COGS) → $400,000
• Credit: Inventory → $400,000

5. Billing and Invoicing

• Definition: The Billing process generates an invoice for the delivered goods. This step enables revenue recognition in Financial Accounting (FI).
• Purpose: Send a bill to the customer for the delivered products/services and record the revenue.

Transaction Code:

• VF01: Create Billing Document

Steps in Billing:

1. The system generates a Billing Document based on the Sales Order and Outbound Delivery.
2. The invoice is sent to the customer for payment.
3. Revenue is recognized in Financial Accounting.

Example Accounting Entry for Billing:

• Debit: Accounts Receivable → $500,000 (Customer’s outstanding amount)
• Credit: Revenue → $500,000 (Recognized income).

Output:

• An Invoice Number (e.g., INV1001) is generated and sent to the customer.

6. Payment Collection

• Definition: The final step in the Lead to Cash process where customer payments are received and posted to clear outstanding accounts.
• Purpose: Settle open customer invoices and ensure accurate accounts receivable management.

Transaction Code:

• F-28: Post Incoming Payment

Steps in Payment Collection:

1. Customer makes the payment (e.g., bank transfer, check).
2. The payment is recorded in SAP against the open invoice.
3. The customer’s outstanding balance is cleared.

Example Accounting Entry for Payment:

• Debit: Bank Account → $500,000 (Cash inflow).
• Credit: Accounts Receivable → $500,000 (Clear outstanding balance).

Output:

• The invoice is marked as "Paid" in the system.

Summary of Key Steps in Lead to Cash

Step	Transaction Code	Purpose
Opportunity and Inquiry	-	Capture leads and inquiries
Quotation Management	VA21	Create and send quotations to customers
Sales Order Management	VA01	Formalize the sales agreement
Outbound Delivery	VL01N	Ship goods (Picking, Packing, PGI)
Billing and Invoicing	VF01	Generate invoices and recognize revenue
Payment Collection	F-28	Record customer payments and clear open items

6.2 Master Data in Lead to Cash

In the Lead to Cash process, Master Data plays a crucial role in ensuring the accuracy and efficiency of sales and distribution processes. Master Data is static data that does not change frequently and serves as the foundation for transaction processing.

There are three key types of Master Data in the Lead to Cash process:

1. Customer Master Data
2. Material Master Data
3. Pricing Conditions

1. Customer Master Data

Definition:
The Customer Master Data stores all the essential information about customers needed for sales, delivery, billing, and payment processes.

Purpose:

1. Avoid repeated data entry by storing customer details centrally.
2. Ensure accurate communication and processing of customer-related transactions.
3. Integrate customer data across SAP modules like SD (Sales and Distribution) and FI (Financial Accounting).

Structure of Customer Master Data

The Customer Master is divided into three main segments:

1. General Data:

   • Information applicable across the entire organization.
   • Examples:
     • Customer Name
     • Address
     • Contact Person
     • Phone and Email

2. Company Code Data:

   • Financial information related to Accounts Receivable.
   • Examples:
     • Reconciliation Account (G/L account for posting AR entries)
     • Payment Terms (e.g., Payment due in 30 days)
     • Dunning Procedure (rules for overdue payment reminders)

3. Sales Area Data:

   • Information specific to the sales organization.
   • Examples:
     • Sales Organization: Defines the region or business unit managing sales.
     • Distribution Channel: E.g., wholesale, retail, online.
     • Division: Product line or business segment.
     • Pricing: Discounts, taxes, and pricing conditions.

Transaction Codes for Customer Master Data:

• XD01: Create Customer Master (Centrally).
• XD02: Change Customer Master.
• XD03: Display Customer Master.

Example:

Field	Value
Customer Name	ABC Corporation
Address	123 Elm Street, NY, USA
Reconciliation Account	140000 (Accounts Receivable)
Payment Terms	30 Days Net
Sales Organization	North America Sales
Distribution Channel	Wholesale

2. Material Master Data

Definition:
The Material Master contains all the information related to products or services that a company sells, produces, or procures.

Purpose:

1. Centralized storage of material-specific data.
2. Enable accurate processing of sales, delivery, inventory, and billing.
3. Integrate material data across SAP modules: SD (Sales and Distribution), MM (Materials Management), and PP (Production Planning).

Structure of Material Master Data

Material Master Data is divided into different views based on the purpose:

1. Basic Data:

   • General product details.
   • Examples:
     • Material Number: Unique identifier (e.g., LAPTOP100).
     • Material Description: "Laptop 16GB RAM."

2. Sales Organization Data:

   • Sales-specific details of the material.
   • Examples:
     • Delivering Plant: The location from which the material is shipped.
     • Tax Classification: Tax rates applicable to the product.
     • Pricing Group: Determines pricing behavior.

3. MRP Data:

   • Planning details for production and procurement.
   • Examples:
     • MRP Type: Determines planning methods (e.g., MRP, reorder point).
     • Lot Size: Quantity to produce or purchase in one batch.

4. Accounting Data:

   • Financial information for inventory valuation.
   • Examples:
     • Valuation Class: Determines the G/L account for inventory postings.
     • Moving Average Price: Average cost of the material.

Transaction Codes for Material Master Data:

• MM01: Create Material Master.
• MM02: Change Material Master.
• MM03: Display Material Master.

Example:

Field	Value
Material Number	LAPTOP100
Material Description	Laptop 16GB RAM
Delivering Plant	1000 (North America DC)
Valuation Class	3000 (Finished Goods)
Tax Classification	Tax Exempt

3. Pricing Conditions

Definition:
Pricing Conditions in SAP define how product prices, discounts, surcharges, and taxes are calculated during sales processes.

Purpose:

1. Automate the determination of product pricing in sales orders and quotations.
2. Ensure flexible pricing through condition types and pricing procedures.
3. Manage complex pricing scenarios like discounts, freight, and taxes.

Key Elements of Pricing Conditions

1. Condition Types:

   • Represents different components of pricing.
   • Examples:
     • PR00: Base Price
     • K004: Material Discount
     • KF00: Freight Charges
     • MWST: Sales Tax

2. Pricing Procedure:

   • Defines the sequence of condition types during pricing.
   • Example of Pricing Flow:
     • PR00 → K004 → KF00 → MWST

3. Condition Records:

   • Store specific pricing details for materials and customers.
   • Example: Material LAPTOP100 for Customer ABC Corp has a price of $1,000/unit.

Transaction Codes for Pricing:

• VK11: Create Condition Records.
• VK12: Change Condition Records.
• VK13: Display Condition Records.

Example Pricing Setup:

Condition Type	Description	Amount	Unit
PR00	Base Price	$1,000	Per Unit
K004	Material Discount	$50	Per Unit
MWST	Sales Tax	10%

Summary of Master Data in Lead to Cash

Master Data	Purpose	Key Transaction Codes
Customer Master Data	Stores customer-specific information	XD01, XD02, XD03
Material Master Data	Defines product or service details	MM01, MM02, MM03
Pricing Conditions	Determines product prices, discounts, and taxes	VK11, VK12, VK13

6.3 Integration in Lead to Cash

The Lead to Cash process in SAP integrates seamlessly with other modules to ensure end-to-end visibility, operational efficiency, and accurate financial reporting. This integration connects sales, inventory, procurement, and accounting data into a unified system.

The following SAP modules play a key role in this integration:

1. FI/CO (Finance and Controlling)
2. MM (Materials Management)
3. SD (Sales and Distribution)

1. Integration with Finance (FI) and Controlling (CO)

The integration with FI/CO ensures that all financial impacts from the sales process are recorded in real time. This includes revenue recognition, accounts receivable management, and cost tracking.

Key Processes in FI/CO Integration

1. Revenue Recognition
   • When a Billing Document is created, revenue is recognized and posted to the General Ledger (G/L).
   • The system automatically creates accounting entries for the sales revenue.

Example Accounting Entry during Billing:

Account	Debit	Credit
Accounts Receivable (Customer)	$500,000
Sales Revenue		$500,000

2. Accounts Receivable (AR)
   • When a customer invoice is generated, the customer’s outstanding balance is updated in the Accounts Receivable ledger.
   • Once the payment is received, the balance is cleared.

Transaction Codes:

• VF01: Create Billing Document.
• F-28: Record Incoming Payment.

Example:

• Customer ABC Corp receives an invoice for $500,000.
• Payment is received, and SAP clears the open invoice.

Accounting Entry for Payment:

Account	Debit	Credit
Bank Account	$500,000
Accounts Receivable (Customer)		$500,000

3. Cost Tracking in CO
   • Cost of Goods Sold (COGS) is posted during the Post Goods Issue (PGI) step.
   • This allows for cost analysis and profitability reporting in Controlling.

Example Accounting Entry for PGI:

Account	Debit	Credit
Cost of Goods Sold (COGS)	$400,000
Inventory (Finished Goods)		$400,000

4. Profitability Analysis (CO-PA)
   • Revenue and cost data flow into Profitability Analysis (CO-PA) for detailed analysis.
   • Managers can analyze profitability by product, customer, region, or sales channel.

Example CO-PA Reporting:

Dimension	Revenue	COGS	Profit
Product: Laptop	$500,000	$400,000	$100,000

2. Integration with Materials Management (MM)

The integration with Materials Management (MM) ensures that the required goods are available for sales orders and that inventory levels are updated accurately.

Key Processes in MM Integration

1. Availability Check

   • During Sales Order Creation, SAP checks the availability of materials in inventory to confirm delivery dates.
   • If the stock is insufficient, a procurement proposal (e.g., Purchase Requisition) is triggered.

2. Goods Issue

   • During Outbound Delivery, materials are picked from inventory, and a Goods Issue is posted.
   • Inventory levels are reduced automatically.

Transaction Code:

• VL02N: Post Goods Issue.

Example Accounting Entry for Goods Issue:

Account	Debit	Credit
Cost of Goods Sold (COGS)	$400,000
Finished Goods Inventory		$400,000

3. Stock Updates
   • Real-time inventory updates ensure accurate stock visibility across the organization.

3. Core Role of Sales and Distribution (SD)

The Sales and Distribution (SD) module is the backbone of the Lead to Cash process. It manages all sales-related processes, including sales orders, deliveries, and billing.

Key SD Processes in Lead to Cash

1. Sales Order Management

   • The Sales Order links customer demand to inventory and production.
   • Integrates with MM (availability check) and FI (revenue posting).

2. Delivery Processing

   • Outbound Delivery ensures goods are shipped and inventory is updated.
   • Integrates with MM for Goods Issue and FI for COGS postings.

3. Billing and Invoicing

   • Billing Documents trigger revenue postings in FI.
   • Integrates with Accounts Receivable for managing payments.

End-to-End Integration Flow in Lead to Cash

1. Inquiry and Quotation
   • Customer requests a quote. (SD)
2. Sales Order
   • Sales Order is created. (SD)
   • System performs availability check. (MM)
3. Outbound Delivery
   • Goods are picked, packed, and shipped. (SD/MM)
   • Goods Issue is posted, reducing inventory and posting COGS. (MM/FI)
4. Billing
   • Billing Document is created. (SD/FI)
   • Revenue is recognized, and AR is updated. (FI/CO)
5. Payment
   • Customer pays the invoice. (FI)
   • AR is cleared, and the bank account is updated. (FI)

Summary of Integration in Lead to Cash

Module	Purpose	Key Activities
FI/CO (Finance)	Record financial impacts and track costs	Revenue posting, AR management, cost tracking
MM (Materials Management)	Manage material availability and inventory	Availability check, Goods Issue, inventory updates
SD (Sales and Distribution)	Manage the entire sales cycle	Sales orders, deliveries, billing

Key Benefits of Integration

1. End-to-End Visibility: Real-time updates on sales orders, inventory, and payments.
2. Accurate Financial Reporting: Automatic postings ensure timely revenue recognition and cost tracking.
3. Optimized Inventory: Integrated availability checks prevent stockouts and delays.
4. Efficiency: Automation of data flow eliminates manual errors and accelerates processing times.

Lead to Cash Processing (Additional Content)

1. Sales Order Types Overview

In SAP Sales and Distribution (SD), Sales Orders are created using predefined order types, each representing a different business process. Understanding order types helps users identify the sales process logic and system behavior.

Common Sales Order Types:

Order Type	Description
OR	Standard Order – Regular sales order used for delivering products to customers.
RE	Returns Order – Used for customer returns and refund processing.
SO	Rush Order – Immediate delivery after order entry.
CS	Credit Memo Request – Used to issue credit to the customer.

Transaction Code: VA01 (Create Sales Order)
When creating a sales order, users must select the appropriate order type, which influences document flow, pricing, and billing.

Why Order Types Matter:

• Determine delivery and billing relevance.
• Drive system behavior (e.g., RE triggers return delivery and credit memo).
• Control allowed item categories and schedule lines.

2. Pricing Procedure Basics

The Pricing Procedure in SAP defines how prices, discounts, surcharges, and taxes are calculated in a sales document.

Example: Pricing Procedure RVAA01

RVAA01 is the standard pricing procedure used for standard orders (OR). It includes several condition types processed in a logical sequence.

Step	Condition Type	Description	Stat	Req
10	PR00	Base Price		1
20	K004	Material Discount
30	KF00	Freight Charges
40	MWST	Sales Tax	X
50	Net Value	Total (System-calculated)	X

Key Fields in Pricing Procedure:

• Req (Requirement): Controls whether a condition is applied based on certain logic (e.g., pricing only for specific customers).
• Stat (Statistical): If checked, the condition does not affect the final price but is shown for information only (e.g., tax).

Why Pricing Procedure Matters:

• Ensures accurate and automated price determination.
• Allows flexible configuration based on customer, material, and order type.
• Integrated with condition records (VK11) for dynamic pricing.

3. Dunning Process (Accounts Receivable Follow-Up)

Dunning is a financial process in SAP Accounts Receivable (AR) used to remind customers of overdue payments.

Key Features of the Dunning Process:

1. Dunning Levels:

• Multiple levels (e.g., 1st, 2nd, 3rd reminder) with increasing severity.

2. Dunning Texts:

• Custom messages per level, explaining overdue amounts and consequences.

3. Interest Calculation (optional):

• SAP can calculate and charge interest on overdue payments.

Dunning Configuration:

• Managed via Dunning Procedure assigned to customer master data (XD02).
• Dunning run performed via Transaction Code: F150.

Example Dunning Flow:

1. Customer invoice is overdue by 15 days.
2. Dunning Level 1 is triggered; a polite reminder is sent.
3. After 30 days, Dunning Level 2 is reached with stronger wording.
4. After 45 days, Dunning Level 3 includes a warning of legal action or service suspension.

Why Dunning Is Important:

• Helps improve cash flow and reduce DSO (Days Sales Outstanding).
• Standard part of the Order-to-Cash lifecycle.
• Can be integrated with credit control to block future orders.