BLOG
Revenue Recognition
Revenue recognition is the set of accounting rules that decides when a company records revenue and how much. In the US, that is ASC 606; internationally, IFRS 15. Both were developed jointly by the FASB and the IASB and share the same core principle: revenue reflects the transfer of promised goods or services to customers, in the amount of consideration the company expects to be entitled to. For US finance and SAP teams, this matters because the rules no longer follow the invoice. Bundles, discounts, contract changes, and usage-based pricing all have to be translated into data, configuration, and controls that hold up in an audit.
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
Revenue Recognition
Revenue Recognition for GPU and Compute Capacity Contracts
Reserved capacity, usage fees, minimum commitments, and embedded leases – how ASC 606 and ASC 842 apply to GPU and compute capacity contracts, and how to implement them in SAP.
Read article →
Revenue Recognition
The 5-Step Model of IFRS 15 / ASC 606 Explained for SAP Teams
How the five steps of ASC 606 and IFRS 15 translate into SAP processes, data and system design – a practical guide for finance and IT teams.
Read article →
Revenue Recognition
Standalone Selling Price (SSP): Methods and Common Mistakes
How to determine standalone selling prices under ASC 606 and IFRS 15, which estimation methods are allowed, and the mistakes that cause problems in SAP RAR.
Read article →
Revenue Recognition
Contract Modifications: Prospective vs. Cumulative Catch-up
How ASC 606 and IFRS 15 classify contract modifications, when to apply prospective or cumulative catch-up treatment, and what this means for SAP RAR.
Read article →
What You'll Find Here
Our revenue recognition articles connect accounting policy with SAP system design. They start with the five-step model – identifying the contract and its performance obligations, determining and allocating the transaction price, and recognizing revenue as obligations are satisfied – and then go deeper into the topics that cause the most judgment and the most rework in practice:
• how to determine and maintain standalone selling prices,
• how to classify contract modifications,
• how variable consideration, material rights, and significant financing components affect the transaction price,
• when a company reports revenue gross or net,
• what auditors look for in contract assets and liabilities,
• and how practical expedients, licenses, bill-and-hold arrangements, and compute capacity contracts are handled.
Key Questions We Cover
• Which promises in a contract are distinct performance obligations – including the ones that never appear on an invoice?
• How should a discount be allocated across a bundle?
• When does a contract change trigger prospective treatment, and when a cumulative catch-up?
• Which estimates need to be made, who owns them, and how do updates flow into the books?
How This Connects to SAP
In SAP, ASC 606 and IFRS 15 are typically implemented with SAP Revenue Accounting and Reporting (RAR). Source documents become revenue accounting items, are combined into revenue accounting contracts, and are processed by performance obligation, allocation, and fulfillment. The accounting judgment comes first; the system design follows it. Our articles explain both sides and show where they meet.
At Revident, we work along a clear method – Discover. Engineer. Validate. Operate. – and apply Agentic Finance with human-governed automation: AI agents take on analysis, testing, and documentation, while experienced specialists make the accounting decisions.
Start Here
• The 5-Step Model of IFRS 15 / ASC 606 Explained for SAP Teams
• Standalone Selling Price (SSP): Methods and Common Mistakes
• Contract Modifications: Prospective vs. Cumulative Catch-up
Questions about ASC 606 in your SAP landscape? 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.