Carve-Out Adjustments as a Pricing and Discount Mechanism

A Whitepaper on Treatment in Multi-POB Revenue Contracts

Executive Summary

In complex customer contracts containing multiple performance obligations (POBs), billing structures frequently diverge from the underlying economic value of each obligation.

Option (A) represents a class of carve adjustments that arise during allocation, where the difference between selling (or invoiced) amounts and allocated transaction price is treated as a pricing-driven redistribution across POBs. Under this model, carve-out and carve-in amounts are structural pricing outcomes, economically equivalent to discounts embedded within a bundled arrangement.

These adjustments are not post-hoc corrections, billing reconciliations, or end-of-contract true-ups. Instead, they are a direct mathematical consequence of applying relative SSP allocation at contract inception, ensuring that each POB reflects its proportionate share of the transaction price regardless of how billing or line pricing is presented.

Option (B), by contrast, addresses a different problem: billing patterns rarely align with allocated revenue over time, creating challenges in deferred revenue placement and rollforward reconciliation. In that model, carve-in and carve-out are liability balancing constructs, not pricing mechanisms.

This whitepaper explains Option (A) as a pricing and discount mechanism, demonstrates how carve amounts arise in complex contracts, and clarifies how this approach differs fundamentally from Option (B), which is driven by billing-versus-allocation variance rather than economic pricing.

Introduction: The Economic Problem Behind Carve-Outs

Modern revenue standards require entities to allocate the transaction price to individual POBs based on relative standalone selling prices (SSPs). However, customers are rarely billed in proportion to SSPs. Instead, billing and line pricing are driven by commercial strategies such as:

• Front-loaded billing for cash flow
• Deep discounts on anchor products
• Zero-dollar or nominally priced add-ons
• Promotional bundling

This creates an unavoidable tension:

Billing reflects deal mechanics, while allocation reflects economic substance.

Option (A) resolves this tension by interpreting carve-out adjustments as embedded pricing effects, functionally equivalent to discounts, rather than as accounting corrections applied after the fact.

Option (A): Conceptual Foundation

Under Option (A):

• The transaction price is fixed at contract inception
• Allocation to each POB is determined upfront using relative SSP
• Any difference between a line’s selling (or invoiced) amount and its allocated revenue is treated as a pricing variance

In practical terms:

• If a line is over-stated relative to its allocation, the excess is carved out
• If a line is under-stated or zero-priced, value is implicitly carved in from other lines

Critically, this is not a timing issue and not a billing reconciliation.
It is a structural pricing outcome that exists from day one of the contract.

Why Option (A) Is Economically a Discount

From an accounting and economic perspective, Option (A) behaves exactly like a discount mechanism:

• The customer pays one transaction price for a bundled set of obligations
• Individual line prices lose independent economic meaning
• Value is redistributed across POBs based on SSP ratios

Even when discounts are not explicitly modeled as a separate line item, the carve-out produces the same result:

• Certain POBs subsidize others
• The bundle, not the invoice line, is the unit of account for pricing

This interpretation aligns with how finance teams explain bundled arrangements to auditors and regulators:

“The line price is not the economic price.””

Complex Contract Example (Multiple POBs)

Contract Structure

POB	Description	SSP
POB-1	Software License	120,000
POB-2	Implementation Services	60,000
POB-3	Support (3 years)	30,000
Total SSP		210,000

Transaction Price (Negotiated)

• Total contract consideration: 150,000

Relative Allocation

POB	Allocation %	Allocated Revenue
POB-1	57.14%	85,710
POB-2	28.57%	42,855
POB-3	14.29%	21,435

Billing Pattern (Commercial Reality)

POB	Invoiced Amount
POB-1	150,000
POB-2	0
POB-3	0

Carve Result (Option A – Allocation-Time Pricing Effect)ption A)

POB	Invoiced	Allocated	Carve Amount
POB-1	150,000	85,710	-64,290
POB-2	0	42,855	+42,855
POB-3	0	21,435	+21,435

Interpretation:

• POB-1 carries a deep implicit discount
• POB-2 and POB-3 receive economic value without billing
• The carve-out is simply the mathematical expression of bundled pricing
• No end-of-contract correction is required. The allocation is correct from inception.

How Oracle RMCS Allocates the Carve (Option A)

Within Oracle RMCS, Option (A) behavior is operationalized as follows:

• Allocation is locked at contract inception
• Billing is tracked independently of allocation
• Carve amounts arise naturally as selling amount – allocated amount
• Deferred revenue balances reflect allocated consideration, not invoice shape
• Revenue recognition consumes allocated balances, not billed amounts

Importantly:

• Carve amounts are recomputed continuously
• They are not event-driven
• They do not wait until contract completion

This reinforces that Option (A) carve behavior is structural, not corrective..

Why Option (A) Does Not Wait Until the End of the Contract

A common misconception is that carve-outs represent “final settlement” adjustments. Under Option (A), this is incorrect because:

• Allocation defines the economic liability from day one
• Deferred revenue must reflect economic obligation, not invoice design
• Waiting until contract end would misstate interim liabilities and margins

Therefore, Option (A) adjustments are embedded continuously within standard revenue processing.sing.

Relationship to Option (B)

Option (B) addresses a different accounting question.

• Option (A):
  • Pricing-driven
  • Selling vs. allocated consideration
  • Discount economics
  • Allocation-time construct
• Option (B):
  • Billing-driven
  • Billing vs. allocated revenue
  • Liability placement and rollforward equilibrium
  • Post-allocation analytical construct

While Option (B) may be appropriate for rollforward reporting and GL reconciliation, it is conceptually distinct and should not be conflated with the pricing logic of Option (A).

Conclusion

Option (A) represents the cleanest economic interpretation of carve-out adjustments in multi-POB contracts. It recognizes that:

• Line-level billing is often artificial
• The transaction price is the true economic anchor
• Allocation—not invoicing—defines revenue entitlement

Under this model, carve-outs are not anomalies to be corrected, but expected outcomes of bundled pricing strategies. Oracle RMCS embeds this logic directly into its allocation and revenue consumption framework, ensuring that financial statements consistently reflect the true economics of the customer contract.

In short: Option (A) is discount accounting—whether explicitly labeled or not.