Skip to content

Main content

Revenue Waterfall One Category Change Tool

Sequential price-volume bridge applies quantity change at prior price, then price change at current quantity.

Loading tool…

Description

Decompose revenue change into quantity and price effects.

Business accounting and analytics distinguish gross, net, allocated, recognized and forecast amounts. Currency, period, eligibility and interaction-allocation conventions determine a reported contribution; reconciling one term does not verify revenue, payment rights or future commercial outcomes.

Decompose revenue change into quantity and price effects.

When to use this tool

Use Revenue Waterfall One Category Change when reconciling the stated business amount, share, bridge or forecast convention.

How to use the tool and how it works

  1. Enter priorQuantity, currentQuantity, priorPrice, currentPrice. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read quantityEffect, priceEffect, totalChange. Use the output convention below.

Decompose revenue change into quantity and price effects. Require nonnegative quantities/prices; quantityEffect = (newQ-oldQ)*oldPrice, priceEffect = newQ*(newPrice-oldPrice), totalChange = newQ*newPrice-oldQ*oldPrice.1

Input fieldMeaning and unitsAccepted input
priorQuantityPrior QuantityRequired. Finite number; minimum 0.
currentQuantityCurrent QuantityRequired. Finite number; minimum 0.
priorPricePrior PriceRequired. Finite number; minimum 0.
currentPriceCurrent PriceRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
quantityEffectQuantity EffectRequired. Finite number.
priceEffectPrice EffectRequired. Finite number.
totalChangeTotal ChangeRequired. Finite number.
json
{
  "input": {
    "priorQuantity": 100,
    "currentQuantity": 120,
    "priorPrice": 10,
    "currentPrice": 12
  },
  "output": {
    "quantityEffect": 200,
    "priceEffect": 240,
    "totalChange": 440
  }
}

Limitations and assumptions

  • This allocates the interaction to priceEffect; summing an extra cross term would double-count it, and no causal price effect is inferred.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use complete verified accounts and governing commercial terms, and apply the appropriate accounting and financial judgment for actual reporting, payment or investment decisions.

References

  1. Calculation and input contract: business-analytics/revenue-waterfall-one-category-change — tool.io

Similar or alternative tools