Standalone Selling Price (SSP): Methods and Common Mistakes

When a contract contains more than one performance obligation, the transaction price must be allocated between them. Under ASC 606 and IFRS 15, this allocation is based on relative standalone selling prices (SSP). It sounds simple. In practice, SSP is one of the most frequent sources of audit findings, manual adjustments, and system complexity.

What Is the Standalone Selling Price?

The SSP is the price at which a company would sell a promised good or service separately to a customer. The best evidence is an observable price: the price charged when the same good or service is sold separately in similar circumstances to similar customers.

A list price is not automatically the SSP. If products are regularly sold at significant discounts, the list price may not reflect what customers actually pay.

Estimation Methods

When an observable price is not available, the SSP must be estimated. The standards give three examples of suitable approaches – the list is not exhaustive:

1. Adjusted Market Assessment Approach

Evaluate the market and estimate what customers would be willing to pay. This can include competitor prices for similar products, adjusted for the company's own cost and margin.

2. Expected Cost Plus a Margin Approach

Forecast the expected costs of satisfying the performance obligation and add an appropriate margin. This is common for services, installation, or maintenance where costs are well understood.

3. Residual Approach

Determine the SSP as the total transaction price less the observable SSPs of the other goods or services in the contract. The residual approach is only permitted in limited circumstances – when the selling price is highly variable or uncertain, for example because the company sells the same item to different customers for a broad range of amounts, or has not yet established a price.

Companies may combine methods within one contract. Whatever method is chosen, it should maximize the use of observable inputs and be applied consistently.

Point Estimates and Ranges

Many companies, especially under US GAAP, use an SSP range rather than a single value. If the contractual price of an item falls within the range, it can be used as the SSP. If it falls outside, a point within the range is used – often the boundary or the midpoint, depending on the accounting policy.

This approach reduces unnecessary reallocations, but it requires a clear, documented policy and regular updates of the ranges.

Common Mistakes

Using List Prices Without Validation

List prices are easy to access in SAP, but they often do not reflect actual selling behavior. Using them as SSP can systematically shift revenue between performance obligations.

No Owner for SSP Data

SSP is accounting data, but it is maintained in a system. If neither finance nor IT clearly owns it, values become outdated. Annual or even more frequent reviews should be part of the close calendar.

Overusing the Residual Approach

The residual approach is convenient, but its use is restricted. Applying it as a default method is likely to be challenged by auditors.

Ignoring Hidden Performance Obligations

Service-type warranties included free of charge, training, or material rights also need an SSP. If they are not modeled, the allocation is incomplete.

Insufficient Granularity

A single SSP for a product may not be appropriate if prices differ significantly by region, customer segment, or sales channel. On the other hand, overly granular SSP tables become difficult to maintain. Finding the right level is a design decision.

No Audit Trail

Auditors want to understand how an SSP was derived and when it changed. Without documentation and versioning, every audit becomes a reconstruction exercise.

SSP in SAP RAR

SAP Revenue Accounting and Reporting determines SSPs automatically when performance obligations are created. Typical options include:

• condition tables or rule-based determination (e.g., via BRF+) by product, region, or customer group,

• SSP tolerances or ranges to avoid unnecessary reallocations,

• residual allocation for specific performance obligations,

• manual adjustments where needed, with traceability.

The technical setup is usually not the hard part. The challenge is defining the right determination logic, connecting it to a reliable data source, and establishing a maintenance process that finance can own.

Related Articles

• The 5-Step Model of IFRS 15 / ASC 606 Explained for SAP Teams

• Discounts in the Quote: How They Drive Revenue Allocation

• Designing Bundles in CPQ with ASC 606 in Mind

The Bottom Line

SSP determination is where accounting judgment meets master data management. A clear policy, consistent methods, defined ownership, and a system design that supports traceability are the foundation for an allocation that holds up in every audit.

Need support with SSP design or SAP RAR allocation? Talk to our experts.