Skip to content
Bitta Apps

Chapter 4 of 8Page 1 of 3

Prices and renewals

Price increases

Raise subscription prices by a fixed percent, a fixed amount, a price index such as CPI or in steps, with caps, on Microsoft's own Contract Price Update page.

updated: applies-to: 1.3.5.0

Escalation rules raise subscription prices on a schedule: by a fixed percent, by a fixed amount, by a price index such as the Consumer Price Index (CPI), or in steps. Floors, caps, a minimum and a maximum price keep the result in bounds. The proposals land on Microsoft's own Contract Price Update page, so the price history stays in Microsoft's archive.

Use it when your contracts promise a yearly uplift, an index-linked increase, or a price ramp (for example +5 % after year one, +4 % after year two, then CPI).

Before you start

  • Administrators maintain indexes and rules (Bitta Subscriptions - Admin).
  • Running Propose Escalations needs Bitta Subscriptions - User and a licensed seat.
  • On the Bitta Subscriptions Setup page: Escalation Mode (Proposal, the default, or Automatic) and Escalation Horizon (how far ahead to look; default one month).

To set up a price index

  1. Choose the search icon, enter Price Indexes, and then choose the related link.
  2. Add the index, for example US-CPI.
  3. Choose Values, and enter a value per month. Or let the values load themselves: set a Feed Source and a Feed Series ID on the index, and choose Import Index Values (Tiers and commitments).
Price Index Values page with one consumer price index value per month

To create an escalation rule

  1. Choose the search icon, enter Escalation Rules, and then choose New.

  2. On the General FastTab, enter a Code, a Description and the Method:

    Method New price
    Fixed Percent Old price + Uplift %
    Fixed Amount Old price + Uplift Amount, per unit or per line (Amount Basis)
    Index Old price x index value now / index value when the price was last set. Index Lag (Months) picks an earlier, published month
    Stepped The Steps FastTab: after a period (After, for example 12M), a Percent, a New Price, or Index
  3. Limits: Floor % and Cap % bound the percent (0 = no cap). Min. Price and Max. Price bound the result. The entry records which limit applied (Limited By).

  4. Schedule: First Escalation After (for example 1Y) and Frequency (for example 1Y). The schedule counts from the start of the subscription line. Holds and plan changes do not move it.

  5. The Summary field describes the rule in one line.

Escalation rule card with the Index method, a three-month lag and a five percent cap

To assign a rule

  • To a whole contract: on the customer contract, fill in Escalation Rule Code.
  • To one line (overrides the contract): on the subscription's lines, fill in Escalation Rule Code.

The Next Escalation Date shows when the line is due.

To propose and apply price increases

  1. On the customer contract, choose Propose Escalations (in the Pricing group). You can also run it from Escalation Entries or Microsoft's Contract Price Update page. The daily task runs it for every contract.
  2. Choose Contract Price Update. Each due line is a row with Old Price, New Price and our Escalation Note.
  3. Review the rows. Choose Microsoft's Perform Price Update to apply them, or Delete Line to drop one.

With Escalation Mode set to Automatic, the increases skip the review and become Microsoft planned price updates right away.

What happens in Microsoft Subscription Billing

  • Prices change only through Microsoft's Perform Price Update or its planned subscription lines. Microsoft decides whether the new price applies at once or after the current billed period, and archives the old price.
  • If the price applies inside a period already billed, Microsoft applies it from the next billing date and does not bill the billed period again. The escalation note says so.
  • Microsoft's own price update templates skip lines that have an escalation rule, so a line is never raised twice.
  • Escalation Entries log every proposal as Proposed, Planned, Applied or Dropped. A dropped proposal is proposed again on the next run.

Lines that are skipped

Skipped lines are logged once with a Skip Reason, for example: Index Value Missing, Escalation Rule Blocked, Excluded from Price Update, Planned Subscription Line Pending, Usage-Based Billing, No Step Due. Lines that a termination, plan change or hold ended are skipped silently.

Limits

  • Promotion lines and Bitta Subscriptions' adjustment lines are never escalated.
  • A rule in use cannot be deleted. Block it instead.
  • A missing index value stops the increase for that month; the Health Check lists it.

See also

Next step

Ready to try Bitta Subscriptions?