BLOG
SAP CPQ
SAP CPQ (Configure, Price, Quote) is SAP's cloud solution that helps sellers configure complex products and services, price them according to company rules, and produce quotes and proposals, with approval workflows for discounts and exceptions. It connects to SAP S/4HANA master data and existing variant configuration models. For US finance and SAP teams, CPQ matters because the deal structure created in the quote, including its bundles, discounts, terms, and dates, becomes the raw material for revenue recognition under ASC 606. A quote designed only for selling can create work for revenue accounting months later.
All
Revenue Recognition
Leasing
Billing & Order-to-Cash
AI in SAP Finance
Regulatory Updates
Comparisons
RAR Support & AMS
SAP RAR
SAP BRIM
SAP CLM
SAP RE-FX
SAP FI-CA
SAP Margin Analysis (CO-PA)
SAP CPQ
SAP Asset Accounting (FI-AA)
SAP Group Reporting
SAP SD
SAP Service Management
SAP Subscription Billing
SAP S/4HANA Finance
SAP CPQ
From Quote to Revenue: How SAP CPQ Data Flows into SAP RAR
SAP CPQ does not post to SAP RAR directly. Here is how quote data reaches revenue accounting via S/4HANA orders, and where ASC 606 decisions are made.
Read article →
SAP CPQ
Designing Bundles in CPQ with ASC 606 in Mind
How to design SAP CPQ bundles so that order items and SAP RAR performance obligations reflect the ASC 606 distinct analysis.
Read article →
SAP CPQ
Discounts in the Quote: How They Drive Revenue Allocation
Why a discount granted in SAP CPQ rarely stays where the seller put it, and how SAP RAR allocates it under ASC 606 using standalone selling prices.
Read article →
What You'll Find Here
This category follows the path from quote to revenue. CPQ does not post revenue. Once a customer accepts a quote, it becomes a sales order, a solution order, or a subscription order in SAP S/4HANA, and that operational order is what SAP Revenue Accounting and Reporting (RAR) consumes. The articles explain what RAR needs from the quote, how CPQ bundles should be translated into order items so that performance obligations reflect the distinct analysis, and why a discount entered on one line rarely stays there once the transaction price is allocated.
Further articles cover how CPQ pricing data can serve as input for standalone selling prices, how renewals and upsells trigger contract modifications, quoting equipment leases and services in one deal, approval workflows for non-standard deal terms, and multi-year deals with ramp pricing.
Quote Price vs. Standalone Selling Price
One theme runs through the whole category: the CPQ price book is not the standalone selling price. Under ASC 606, the best evidence of a standalone selling price is the observable price when a good or service is sold separately; a list price shall not be presumed to be the standalone selling price. CPQ prices define what the customer pays, while standalone selling prices are accounting estimates maintained separately for RAR. Keeping these responsibilities apart, with different owners and approvals, is what makes allocation results explainable to auditors.
Key Questions We Cover
• Which CPQ lines should become separate order items, and which are display-only groupings?
• Which attributes must the quote carry so RAR rules can determine performance obligations?
• How do header discounts, free items, and rebates affect allocation?
• Where can automated checks flag gaps in the quote-to-revenue chain before close?
Start Here
• From Quote to Revenue: How SAP CPQ Data Flows into SAP RAR
• Designing Bundles in CPQ with ASC 606 in Mind
• Discounts in the Quote: How They Drive Revenue Allocation
Connecting SAP CPQ to revenue accounting? Talk to our experts
Ready to Make Your SAP Finance Landscape Agentic?
Whether you are implementing SAP RAR, modernizing revenue processes, or exploring agentic finance operations, Revident helps you move from strategy to execution.