SAP SE – Annual report – 31 December 2018
Section A – Customers (extract 1)
This section discusses disclosures related to contracts with our customers. These include but are not limited to explanations of how we recognize revenue, revenue breakdowns, and information about our trade receivables and customer-related obligations. Furthermore, in this section we disclose the most significant differences to prior-year figures resulting from the application of IFRS 15 ‘Revenue from Contracts with Customers’ (see Note (A.5)).
Classes of Revenue
We derive our revenue from fees charged to our customers for the use of our hosted cloud offerings, for licenses to our on-premise software products, and for standardized and premium support services, consulting, customer-specific software developments, training, and other services.
Cloud and software revenue, as presented in our Consolidated Income Statements, is the sum of our cloud subscriptions and support revenue, our software license revenue, and our software support revenue.
- Revenue from cloud subscriptions and support represents fees earned from providing customers with any of the following:
- Software as a Service (SaaS), that is, a right to use software functionality (including standard functionalities and custom cloud applications and extensions) in a cloud-based infrastructure hosted by SAP or third parties engaged by SAP, where the customer does not have the right to terminate the hosting contract and take possession of the software to either run it on its own IT infrastructure or to engage a third-party provider unrelated to SAP to host and manage the software; SaaS also includes transaction and agent fees for transactions that customers of our network business execute on our cloud-based transaction platforms.
- Platform as a Service (PaaS), that is, access to a cloud-based infrastructure to develop, run, and manage applications
- Infrastructure as a Service (IaaS), that is, hosting and related application management services for software hosted by SAP or third parties engaged by SAP, where the customer has the right to take possession of the software
- Premium cloud subscription support beyond the regular support that is embedded in the basic cloud subscription fees
- Software license revenue represents fees earned from the sale or license of software to customers for use on the customer’s premises, in other words, where the customer has the right to take possession of the software for installation on the customer’s premises or on hardware of third-party hosting providers unrelated to SAP (on-premise software). Software license revenue includes revenue from both the sale of our standard software products and customer-specific on-premise-software development agreements.
- Software support revenue represents fees earned from providing customers with standardized support services that comprise unspecified future software updates, upgrades, and enhancements as well as technical product support services for on-premise software products.
Services revenue primarily represents fees earned from professional consulting services, premium support services, training services, and messaging services.
Accounting Policies, Judgments, and Estimates
Identification of Contract
We frequently enter into multiple contracts with the same customer that we treat, for accounting purposes, as one contract if the contracts are entered into at or near the same time and are economically interrelated. We do not combine contracts with closing days more than three months apart because we do not consider them being entered into near the same time. Judgment is required in evaluating whether various contracts are interrelated, which includes considerations as to whether they were negotiated as a package with a single commercial objective, whether the amount of consideration on one contract is dependent on the performance of the other contract, or if some or all goods in the contracts are a single performance obligation. New arrangements with existing customers can be either a new contract or the modification of prior contracts with the customer. Our respective judgment in making this determination considers whether there is a connection between the new arrangement and the pre-existing contracts, whether the goods and services under the new arrangement are highly interrelated with the goods and services sold under prior contracts, and how the goods and services under the new arrangement are priced. In determining whether a change in transaction price represents a contract modification or a change in variable consideration, we examine whether the change in price results from changing the contract or from applying unchanged existing contract provisions.
Identification of Performance Obligations
Our customer contracts often include various products and services. Typically, the products and services outlined in the Classes of Revenue section qualify as separate performance obligations and the portion of the contractual fee allocated to them is recognized separately. Judgment is required, however, in determining whether a good or service is considered a separate performance obligation. In particular for our professional services and implementation activities, judgment is required to evaluate whether such services significantly integrate, customize, or modify the on-premise software or cloud service to which they relate. In this context, we consider the nature of the services and their volume relative to the volume of the on-premise software or cloud service to which they relate. In general, the implementation services for our cloud services go beyond pure setup activities and qualify as separate performance obligations. Similarly, our on-premise implementation services and our custom development services typically qualify as separate performance obligations. Non-distinct goods and services are combined into one distinct bundle of goods and services (combined performance obligation).
When selling goods or services, we frequently grant customers options to acquire additional goods or services (for example, renewals of renewable offerings, or additional volumes of purchased software). We apply judgment in determining whether such options provide a material right to the customer that the customer would not receive without entering into that contract (material right options). In this judgment, we consider whether the options entitle the customer to a discount that exceeds the discount granted for the respective goods or services sold together with the option.
Determination of Transaction Price
We apply judgment in determining the amount to which we expect to be entitled in exchange for transferring promised goods or services to a customer. This includes estimates as to whether and to what extent subsequent concessions or payments may be granted to customers and whether the customer is expected to pay the contractual fees. In this judgment, we consider our history both with the respective customer and more broadly.
Our typical cloud services do not provide the customer with a software license because the customer does not have the right to terminate the hosting contract and take possession of the software. Consequently, cloud fees that are based on transaction volumes are considered in the transaction price based on estimates rather than being accounted for as sales-based license royalties.
Only very rarely do our contracts include significant financing components. We do not account for financing components if the period between when SAP transfers the promised goods or services to the customer and when the customer pays for those goods or services is one year or less.
Allocation of Transaction Price
We have established a hierarchy to identify the standalone selling prices (SSPs) that we use to allocate the transaction price of a customer contract to the performance obligations in the contract.
- Where standalone selling prices for an offering are observable and reasonably consistent across customers (that is, not highly variable), our SSP estimates are derived from our respective pricing history. Typically, our standardized support offerings and our professional service offerings follow this approach.
- Where sales prices for an offering are not directly observable or highly variable across customers, we use estimation techniques. For renewable offerings with highly variable pricing, these techniques consider the individual contract’s expected renewal price as far as this price is substantive. Typically, our cloud subscription offerings follow this approach. For non-renewable offerings, these estimations follow a cost-plus-margin approach.
- For offerings that lack renewals, have highly variable pricing, and lack substantial direct costs to estimate based on a cost-plus-margin approach, we allocate the transaction price by applying a residual approach. We use this technique in particular for our standard on-premise software offerings.
Judgment is required when estimating SSPs. To judge whether the historical pricing of our goods and services is highly variable, we have established thresholds of pricing variability. For judging whether contractual renewal prices are substantive, we have established floor prices that we use as SSPs whenever the contractual renewal prices are below these floor prices. In judging whether contracts are expected to renew at their contractual renewal prices, we rely on our respective renewal history. The SSPs of material right options depend on the probability of option exercise. In estimating these probabilities, we apply judgment considering historical exercise patterns.
We review the stand-alone selling prices periodically or whenever facts and circumstances change to ensure the most objective input parameters available are used.
Recognition of Revenue
Cloud subscription and support revenue is recognized over time as the services are performed. Where our performance obligation is the grant of a right to continuously access and use a cloud offering for a certain term, revenue is recognized based on time elapsed and thus ratably over this term.
Software revenue is recognized at a point in time or over time depending on whether we deliver standard software or customer-specific software:
- Licenses for our standard on-premise software products are typically delivered by providing the customer with access to download the software. The license period starts when such access is granted. We recognize revenue for these on-premise licenses at the point in time when the customer has access to and thus control over the software. In judging whether our on-premise software offerings grant customers a right to use, rather than a right to access, our intellectual property, we have considered the usefulness of our software without subsequent updates to it.
- Typically, our customer-specific on-premise-software development agreements:
- Are for software developed for specific needs of individual customers and therefore it does not have any alternative use for us
- Provide us with an enforceable right to payment for performance completed to date
For such development agreements, we recognize revenue over time as the software development progresses. Judgment is required in identifying an appropriate method to measure the progress toward complete satisfaction of such performance obligations. We typically measure progress of our development agreements based on the direct costs incurred to date in developing the software as a percentage of the total reasonably estimated direct costs to fully complete the development work (percentage-of-completion method). This method of measuring progress faithfully depicts the transfer of the development services to the customer, as substantially all of these costs are cost of the staff or third parties performing the development work. In estimating the total cost to fully complete the development work, we consider our history with similar projects.
Support revenue is typically recognized based on time elapsed and thus ratably over the term of the support arrangement. Under our standardized support services, our performance obligation is to stand ready to provide technical product support and unspecified updates, upgrades, and enhancements on a when-and-if-available basis. Our customers simultaneously receive and consume the benefits of these support services as we perform.
Service revenue is typically recognized over time. Where we stand ready to provide the service (such as access to learning content), we recognize revenue based on time elapsed and thus ratably over the service period. Consumption-based services (such as separately identifiable consulting services and premium support services, messaging services, and classroom training services) are recognized over time as the services are utilized, typically following the percentage-of-completion method or ratably. When using the percentage-of-completion method, we typically measure the progress toward complete satisfaction of the performance obligation in the same way and with the same reasoning and judgment as we do for customer-specific on-premise software development agreements. We apply judgment in determining whether a service qualifies as a stand-ready service or as a consumption-based service.
Revenue for combined performance obligations is recognized over the longest period of all promises in the combined performance obligation.
Judgment is also required to determine whether revenue is to be recognized at a point in time or over time. For performance obligations satisfied over time, we need to measure progress using the method that best reflects SAP’s performance. When using cost incurred as a measure of progress for recognizing revenue over time, we apply judgment in estimating the total cost to satisfy the performance obligation.
All of the judgments and estimates mentioned above can significantly impact the timing and amount of revenue to be recognized.
We recognize trade receivables for performance obligations satisfied over time gradually as the performance obligation is satisfied and in full once the invoice is due. Judgment is required in determining whether a right to consideration is unconditional and thus qualifies as a receivable.
Contract liabilities primarily reflect invoices due or payments received in advance of revenue recognition.
Typically, we invoice fees for on-premise standard software on contract closure and software delivery. Periodic fixed fees for cloud subscription services, software support services, and other multi-period agreements are typically invoiced yearly or quarterly in advance. Such fee prepayments account for the majority of our contract liability balance. Fees based on actual transaction volumes for cloud subscriptions and fees charged for non-periodical services are invoiced as the services are delivered. While payment terms and conditions vary by contract type and region, our terms typically require payment within 30 to 60 days.
The amounts for revenue by region in the following tables are based on the location of customers. The regions in the following table are EMEA (Europe, Middle East, and Africa), Americas (North America and Latin America), and APJ (Asia Pacific Japan).
For information about the breakdown of revenue by segment and segment revenue by region, see Note (C.1).
Remaining Performance Obligations
Amounts of a customer contract’s transaction price that are allocated to the remaining performance obligations represent contracted revenue that has not yet been recognized. They include amounts recognized as contract liabilities and amounts that are contracted but not yet due.
The transaction price allocated to performance obligations that are unsatisfied or partially unsatisfied as at December 31, 2018, is €31.3 billion. This amount mostly comprises obligations to provide software support or cloud subscriptions and support, as the respective contracts typically have durations of one or multiple years.
The majority of this amount is expected to be recognized as revenue over the next 12 months following the respective balance sheet date. This estimation is judgmental, as it needs to consider estimates of possible future contract modifications. The amount of transaction price allocated to the remaining performance obligations, and changes in this amount over time, are impacted by, among others:
- Currency fluctuations
- The contract period of our cloud and support contracts remaining at the balance sheet date and thus by the timing of contract renewals
Performance Obligations Satisfied in Previous Years
Revenue recognized in the reporting period for performance obligations satisfied in earlier periods was €132 million, mainly resulting from changes in estimates related to percentage-of-completion-based contracts and changes in estimates of variable considerations.
Contract liabilities as at December 31, 2018, were €3.1 billion (January 1, 2018: €3.5 billion).
Increases in contract liabilities mainly result from billing and invoices becoming due (€7.0 billion). Decreases in contract liabilities mainly result from satisfying performance obligations (€7.5 billion). The Callidus acquisition contributed to the increase in the contract liabilities balance (for more information, see Note (D.1)).
The amount of revenue recognized in the reporting period that was included in the contract liability balance as at January 1, 2018, was €3.2 billion.
Section A – Customers (extract 2)
(A.3) Capitalized Cost from Contracts with Customers
Accounting Policies, Judgments, and Estimates
Incremental Costs of Obtaining Customer Contracts
Capitalized costs from customer contracts are classified as nonfinancial assets in our statement of financial position.
The capitalized assets for the incremental costs of obtaining a customer contract primarily consist of sales commissions earned by our sales force. Judgment is required in determining the amounts to be capitalized, particularly where the commissions are based on cumulative targets and where commissions relate to multiple performance obligations in one customer contract. We capitalize such cumulative target commissions for all customer contracts that count towards the cumulative target but only if nothing other than obtaining customer contracts can contribute to achieving the cumulative target. Commissions for contracts with multiple performance obligations or probable renewals thereof are allocated to these performance obligations and probable renewals relative to the standalone selling price.
Typically, we either do not pay sales commissions for customer contract renewals or such commissions are not commensurate with the commissions paid for new contracts. Thus, the commissions paid for renewable new contracts also relate to expected renewals of these contracts. Consequently, we amortize sales commissions paid for new customer contracts on a straight-line basis over the expected contract life including probable contract renewals. Judgment is required in estimating these contract lives. In exercising this judgment, we consider our respective renewal history adjusted for indications that the renewal history is not fully indicative of future renewals. The amortization periods range from 18 months to eight years depending on the type of offering. Amortization of the capitalized costs of obtaining customer contracts is classified as sales and marketing expense.
We expense incremental costs of obtaining a customer contract as incurred if we expect an amortization period of one year or less.
Costs to Fulfill Customer Contracts
Capitalized costs incurred to fulfill customer contracts mainly consist of direct costs for custom cloud development contracts as far as these costs are not in scope of other standards than IFRS 15. These costs are amortized after completion of the development on a straight-line basis over the expected life of the cloud subscription contract and including expected renewals. Judgment is required in evaluating whether costs are direct or indirect and in estimating contract lives. Derived from our respective history, the amortization period is typically six years.
Amortization of capitalized costs to fulfill contracts for custom cloud applications and extensions is included in the cost of cloud subscriptions and support.
As at December 31, 2017, before application of IFRS 15, capitalized contract costs were €696 million, of which €199 million were current and €497 million were non-current.
Amortization expenses in 2018 for the costs of obtaining customer contracts and for the costs of fulfilling customer contracts were €231 million and €50 million respectively.
(A.4) Customer-Related Provisions
Accounting Policies, Judgments, and Estimates
Customer-related provisions mainly include expected contract losses. We adjust these provisions as further information becomes available and as circumstances change. Non-current provisions are measured at the present value of their expected settlement amounts as at the reporting date.
Furthermore, these provisions also include obligations resulting from customer-related litigation and claims. We are currently confronted with various claims and legal proceedings, including claims that relate to customers demanding indemnification for proceedings initiated against them based on their use of SAP software, and occasionally claims that relate to customers being dissatisfied with the products and services that we have delivered to them. The obligations arising from customer-related litigation and claims comprise cases in which we indemnify our customers against liabilities arising from a claim that our products infringe a third party’s patent, copyright, trade secret, or other proprietary rights.
Due to uncertainties relating to these matters, provisions are based on the best information available. Significant judgment is required in the determination of whether a provision is to be recorded and what the appropriate amount for such provision should be. Notably, judgment is required in the following:
- Determining whether an obligation exists
- Determining the probability of outflow of economic benefits
- Determining whether the amount of an obligation is reliably estimable
- Estimating the amount of the expenditure required to settle the present obligation
At the end of each reporting period, we reassess the potential obligations related to our pending claims and litigation and adjust our respective provisions to reflect the current best estimate. In addition, we monitor and evaluate new information that we receive after the end of the respective reporting period but before the Consolidated Financial Statements are authorized for issue to determine whether this provides additional information regarding conditions that existed at the end of the reporting period. Changes to the estimates and assumptions underlying our accounting for legal contingencies, and outcomes that differ from these estimates and assumptions, could require material adjustments to the carrying amounts of the respective provisions recorded and additional provisions. The expected timing or amounts of any outflows of economic benefits resulting from these lawsuits and claims is uncertain and not estimable, as they generally depend on the duration of the legal proceedings and settlement negotiations required to resolve the litigation and claims and the unpredictability of the outcomes of legal disputes in several jurisdictions.
Contingent liabilities exist in respect of customer-related litigation and claims for which no provision has been recognized. It is not practicable to estimate the financial impact of these contingent liabilities due to the uncertainties around these lawsuits and claims as outlined above.
(A.5) Adoption of IFRS 15
Effective January 1, 2018, we started to apply IFRS 15 ‘Revenue from Contracts with Customers’ retrospectively, using the cumulative catch-up approach and the practical expedient to apply the new standard only to contracts that were not completed as of January 1, 2018. This practical expedient affected both the transition adjustment amount recognized in retained earnings and our revenues and expenses.
On adopting IFRS 15, SAP changed several of its accounting policies. Under the cumulative catch-up approach, prior years (including the prior-period numbers presented in the primary financial statements) are not restated to conform to the new policies.
The impacts of the policy change in 2018 were as follows:
- Software license and support revenues experienced a benefit of €170 million, with most of the difference resulting from:
- Exercise of customer software purchase options granted in prior years, which result in software revenue
- Revised recognition patterns for on-premise software subscription contracts, which combine the delivery of software and support service and the obligation to deliver, in the future, unspecified software products
- Revised recognition patterns for contracts that combine customer-specific on-premise software development agreements and the sale of standard on-premise software
- Together with other offsetting effects, this resulted in a benefit of €158 million on total revenue.
- Operating expenses benefitted, in cost of sales and marketing, in the amount of €239 million from higher capitalization of sales commissions net of higher amortization of amounts capitalized.
- The abovementioned revenue and expense effects, together with other insignificant effects, resulted in a net positive impact on operating profit of approximately €399 million.
As at December 31, 2018, balance sheet items are affected by the application of IFRS 15 as compared to our pre-IFRS 15 accounting policies as follows:
- Non-current and current other non-financial assets were higher by €336 million and €64 million respectively (January 1, 2018: higher by €132 million and €26 million respectively) due to the higher capitalization of sales commissions.
- Trade and other receivables and contract liabilities were lower by €132 million and €188 million respectively (January 1, 2018: higher by €560 million and €650 million respectively), resulting from changes in the timing of and amounts recognized as contract balances.
- Provisions were lower by €4 million (January 1, 2018: lower by €25 million), reflecting lower provisions for onerous customer contracts.
- Intangible assets were higher by €37 million (January 1, 2018: higher by €14 million), due to the capitalization of costs for certain custom on-premise software development arrangements.