A Unified Framework Covering Allocation-Driven (Option A) and Billing-Driven (Option B) Models
Executive Summary
In multi-performance-obligation (multi-POB) contracts, differences between pricing, allocation, and billing inevitably produce variances that must be explained, tracked, and reconciled. These variances are often labeled as carve-in or carve-out, but the same terminology is frequently used to describe two fundamentally different accounting constructs, leading to confusion.
This whitepaper clarifies that:
- Option (A) uses carve-in and carve-out as a pricing and discount construct arising at allocation time (ASC 606 Step 4).
- Option (B) uses carve-in and carve-out as a billing-triggered liability rebalancing construct, applied post-allocation (ASC 606 Step 5 mechanics).
Using a simple, table-based numeric illustration, this paper demonstrates how carve status is determined, when carve amounts are real accounting entries versus analytical variances, and how both models coexist coherently—particularly in systems such as Oracle RMCS.
The Root of the Confusion
The confusion around carve logic does not stem from incorrect formulas.
It stems from applying the same terminology to different stages of the revenue lifecycle.
| Dimension | Option (A) | Option (B) |
|---|---|---|
| Accounting Stage | Allocation (ASC 606 Step 4) | Billing & Recognition (Step 5 mechanics) |
| Compared Amounts | Selling Amount vs Allocated Revenue | Billing Amount vs Allocated Revenue |
| Nature of Carve | Pricing / Discount | Liability Rebalancing |
| Purpose | Establish economic consideration | Align deferred revenue over time |
Both use subtraction.
Only one defines economic value.
Option (A): Allocation-Driven Carve (Pricing & Discount Model)
Conceptual Foundation
Option (A) treats carve-in and carve-out as a pricing outcome of relative SSP allocation.
Once the transaction price is allocated, selling amounts lose independent economic meaning.
Core principle
Allocation defines value.
Selling amount is merely presentation.
Defining Formula (Allocation Stage)
Allocation Carve = Selling Amount − Allocated Revenue
Interpretation
- Carve-Out
Selling Amount > Allocated Revenue
→ Excess represents an implicit discount carved out of the POB - Carve-In
Selling Amount < Allocated Revenue
→ Discount is absorbed into the POB - No Carve
Selling Amount = Allocated Revenue
Key Characteristics
- Occurs at contract inception
- Drives contract discount accounting
- Structural, not timing-based
- Persists regardless of billing pattern
This is the carve logic reflected in allocation tables such as VRM_CONTR_CARVEOUT_HDRS.
Option (B): Billing-Driven Carve (Liability Rebalancing Model)
Conceptual Foundation
Option (B) treats carve-in and carve-out as a post-allocation liability alignment mechanism.
It does not redefine pricing and does not change allocation.
Core principle
Allocation defines entitlement.
Billing defines enforceable liability.
Defining Formula (Post-Allocation)
Billing Variance = Gross Cumulative Billing − Allocated Revenue
Interpretation
- Carve-Out (Liability Reduction)
Billing > Allocated Revenue - Carve-In (Liability Increase)
Billing < Allocated Revenue and Billing ≥ 0 - No Carve
Billing ≤ 0 or Billing = Allocated Revenue
Key Characteristics
- Triggered by billing events or plan completion
- Temporary and timing-driven
- Explains deferred revenue placement
- Essential for rollforward and GL reconciliation
This model governs how billing mismatches are managed over time, not how value is priced.
Unified Table-Based Illustration (Constant Allocated Revenue)
To eliminate ambiguity, both options can be illustrated numerically using the same table—the difference lies in how the result is interpreted.
Assumptions
- Allocated Revenue (AR): $4,000 (constant)
- Gross Cumulative Billing (GB) varies
Illustration Table
| Case | Gross Cumulative Billing (GB) | Allocated Revenue (AR) | GB vs AR | Carve Status | Carve-Out Amount | Carve-In Amount | Explanation |
|---|---|---|---|---|---|---|---|
| 1 | 8,000 | 4,000 | GB > AR | Carve-Out | 4,000 | 0 | Billing exceeds allocation; excess must be removed from liability |
| 2 | 4,000 | 4,000 | GB = AR | No Carve | 0 | 0 | Billing matches allocation exactly |
| 3 | 2,000 | 4,000 | GB < AR (≥0) | Carve-In | 0 | 2,000 | Allocation exceeds billing; liability must be increased |
| 4 | 0 | 4,000 | GB < AR (≥0) | Carve-In | 0 | 4,000 | No billing yet; full allocation deferred |
| 5 | –2,000 | 4,000 | GB < 0 | No Carve | 0 | 0 | Credit/reversal activity, not pricing or discount |
How the Same Table Serves Two Models
| Aspect | Option (A) Interpretation | Option (B) Interpretation |
|---|---|---|
| Purpose | Pricing economics | Liability timing |
| Carve Meaning | Discount allocation | Deferred revenue alignment |
| Negative Billing | Not applicable | Explicitly excluded |
| Accounting Impact | Structural | Event-driven |
Same math. Different intent.
Audit-Safe Design Rule (Recommended)
To avoid misclassification:
Carve Status Determination Rule
- If Selling Amount > Allocated Revenue → Allocation Carve-Out (Option A)
- If Billing > Allocated Revenue → Liability Carve-Out (Option B)
- If Billing < 0 → No Carve (credit activity)
- Never mix selling-based carve with billing-based carve in the same measure
Conclusion
Carve-in and carve-out are not ambiguous concepts—they are precise constructs used at different stages of revenue accounting.
- Option (A) explains price
- Option (B) explains timing
When these are separated cleanly:
- Carve logic becomes intuitive
- Rollforwards reconcile cleanly
- GL explanations become audit-ready
- System behavior aligns with ASC 606
Allocation carves price.
Billing rebalances liability.
If you can explain your carve logic using a table like the one above—and state which option you are using—you are aligned with both RMCS system behavior and revenue accounting principles.
Additional Notes:
Why Ignoring Negative Billing Breaks Carve Accuracy
Below is a clear, structured explanation that resolves the confusion and shows why negative billing must be considered in carve calculations, while still keeping carve classification correct.
The Core Problem You Identified
If negative billing is excluded from Carve-In / Carve-Out calculations, then total contract-level billing cannot be accurately allocated to POBs using relative SSP.
This statement is 100% correct.
Here is why.
Two Different Concepts That Often Get Mixed Up
1️⃣ Carve Classification (Status Flag)
This answers:
Is this a discount scenario or not?
- Carve-In / Carve-Out / No Carve
- Driven by business meaning
- Negative billing is NOT a discount
2️⃣ Billing Allocation Mathematics
This answers:
How much billing must be allocated to each POB?
- Must always use total cumulative billing
- Negative billing must be included
- Otherwise totals will not reconcile
👉 Negative billing affects allocation math, but not carve classification.
Why Negative Billing MUST Be Included in Allocation
Revenue Rule (ASC 606 / RMCS)
Transaction price allocation must be based on net contract consideration, not selective billing values.
If a contract has:
- Invoices
- Credits
- Rebills
Then net billing = sum of all billing, including negatives.
If you ignore negative billing:
- Allocated billing ≠ actual billing
- Contract asset/liability will be misstated
- Rollforward and GL reconciliation will break
Correct Design Approach (This Solves the Issue)
Step 1: Use Net Cumulative Billing for Allocation
Net Cumulative Billing
= Σ (positive billings + negative billings)
This value must be allocated to POBs using relative SSP.
Step 2: Determine Carve Status Separately
Carve status answers whether a discount exists, not how billing is allocated.
| Condition | Carve Status |
|---|---|
| Net Billing > Allocated Revenue | Carve-Out |
| Net Billing < Allocated Revenue AND Net Billing ≥ 0 | Carve-In |
| Net Billing < 0 | No Carve |
✔ Negative billing is included
✔ But it does not automatically create a discount
Example to Make This Concrete
Contract Setup
| Item | Amount |
|---|---|
| Allocated Revenue | 4,000 |
| Gross Billing | 8,000 |
| Credit Memo | –6,000 |
| Net Billing | 2,000 |
Allocation Impact
- Net Billing 2,000 must be allocated to POBs using SSP
- Ignoring the –6,000 credit would falsely allocate 8,000
Carve Outcome
Net Billing (2,000) < Allocated Revenue (4,000)
⇒ Carve-In = 2,000
Correct
Reconciled
Audit-safe
What Goes Wrong If You Ignore Negative Billing
| Area | Impact |
|---|---|
| SSP Allocation | Incorrect |
| POB-Level Billing | Overstated |
| Contract Asset | Incorrect |
| Deferred Revenue | Incorrect |
| Rollforward Report | Does not tie |
| GL Reconciliation | Breaks |
This is exactly the failure mode you identified.
Final Rule Set (Use This in Your FSD)
Design Principle:
All billing amounts, including negative billings (credits/reversals), must be included in cumulative billing for SSP allocation purposes.Carve classification, however, must be determined independently based on whether net billing represents a pricing discount. Negative billing alone does not indicate a discount and therefore does not trigger Carve-In or Carve-Out status.
One-Line Summary (For Stakeholders)
Negative billing must be included for accurate allocation, but it must not be misclassified as a discount.
Enterprise Resource Planning and Integrations BlogSpot 