Skip to content
Bitta Apps

Chapter 5 of 8Page 3 of 4

Billing plans and revenue

Revenue recognition

Allocate a contract's price by standalone selling price, recognize total contract value and hardware per serial, and post contract assets and liabilities.

updated: applies-to: 1.3.5.0

Microsoft Subscription Billing recognizes revenue as it is billed: each invoice line is deferred over its billing period. That is not always right. A bundle that gives the hardware away, a three-year contract whose price goes up every year, or a discount that belongs to the whole contract all need the contract's total price divided across what it delivers, by standalone selling price, and recognized in its own pattern.

Revenue recognition in Bitta Subscriptions does that without replacing Microsoft's deferrals. Microsoft keeps deferring and releasing what it invoices. Bitta Subscriptions posts only the difference between the revenue an item should recognize (its allocated amount) and what billing recognizes (its contractual amount), against a contract asset or a contract liability account. Over a whole term the differences add up to zero.

Use it if your auditors ask for revenue by performance obligation: bundles with hardware, stepped prices, contract-level discounts, or hardware that should be recognized over the service.

Turn on Revenue Recognition

Revenue Recognition is a module of Subscription Features. Its switch is Revenue Allocation on the Bitta Subscriptions Setup page: turn it on there, in the assisted setup's Features step (Which features do you use?) or on the Subscription Features page, then reload the browser page. While it is off, the allocation pages, the revenue schedule, the standalone selling prices, the revenue reports and the revenue FactBox are hidden everywhere, including search, nothing is allocated or posted, and Microsoft's contract deferrals recognize revenue as billed. The data stays.

Before you start

On the Bitta Subscriptions Setup page, group Revenue Recognition:

  • Revenue Allocation: turn it on. While it is off, nothing of this page runs, and Microsoft's straight-line contract deferrals recognize revenue as billed. You can turn it off at any time.
  • The defaults that new allocations get (you can change them per allocation while it is a draft):
    • Allocation Method: Relative standalone selling price, or None (own price). With None, each item keeps its own price and only its recognition pattern changes (for hardware deferral or total contract value without prices).
    • Allocation Scope: Contract (the whole contract shares one price) or Bundle (each bundle shares one price; everything else stands alone).
    • Recognition Method: Follow billing, or Total contract value (straight-line).
    • Hardware Recognition: At delivery, or Over the contract (per serial number).
  • Missing Standalone Price: Use the line price (the item's unit price for hardware), or Refuse the allocation with a list of the missing prices.
  • Contract Asset Account: revenue recognized ahead of billing.
  • Contract Liability Account: billing ahead of allocated revenue, beyond Microsoft's deferrals.
  • Revenue Allocation Nos.: the message offers Create number series (BAA-REVALL) if it is blank. The number is also the document number of the G/L entries.
  • Revenue Source Code: the message offers Create source code (BAAREVREC) if it is blank.
  • Revenue Jnl. Template and Revenue Jnl. Batch: only when the general ledger setup makes the journal template mandatory.

Each obligation's revenue account is Microsoft's Cust. Sub. Contract Account of its general posting setup, or the Sales Account for hardware.

Allocating, calculating and activating need Bitta Subscriptions - User and a licensed seat. Post Revenue Schedule and Create Revenue Allocations need a usable license only, so they can run in the job queue.

To set up standalone selling prices

  1. Search for Standalone Selling Prices, or choose Standalone Selling Prices on an item card.
  2. Add a line per item: the plan, add-on, hardware item or one-time charge item, a Starting Date, the Price Basis (Per month for plans and add-ons, One time for hardware and charges) and the Standalone Price (LCY) per unit.

A price stays valid until the next starting date of the same item.

To allocate a contract's revenue

  1. On a customer contract, choose Revenue, then Allocate Revenue. A Draft revenue allocation opens. If the contract already has an open allocation, that one opens instead.
  2. Check the Start Date and End Date. For a contract that already runs, the start is the first day of the work date's month: earlier months are not restated. Lines without an end date are allocated up to the end date.
  3. Check the Method group, and the Performance Obligations: one per subscription line, one-time charge and invoiced device. Each shows its Type (Recurring, One-time charge, Hardware or Price adjustment), Standalone Price (LCY), Allocation %, Contractual Amount (LCY), Allocated Amount (LCY) and Adjustment Amount (LCY).
  4. Change what you need, then choose Calculate.
  5. Choose Activate.

To allocate many contracts at once, search for Create Revenue Allocations. It creates the allocation of every contract in the filter that has none for its current term. Turn on Activate to activate them at once, or leave the drafts for review.

The Revenue Allocation FactBox on the contract shows the Allocation No., Allocation Status, transaction price, posted and scheduled adjustments and Posted Through.

What counts as an obligation

  • Every customer subscription line on the contract that is invoiced through the contract. Usage-based lines are left out: Microsoft recognizes them as billed.
  • One-time charges, recognized on their charge date.
  • Every device in the device register whose hardware was invoiced, one obligation per serial number, delivered on its shipment date.
  • Discounts, credits and promotions are Price adjustment lines. They change the price; they deliver nothing of their own.

How revenue is recognized

Obligation Follow billing Total contract value (straight-line)
Recurring In proportion to what is billed Straight-line by days over the term
One-time charge In the month of the charge The same
Hardware, At delivery In the month of delivery The same
Hardware, Over the contract (per serial number) Straight-line from delivery to the end of the device's service The same

Total contract value. With stepped prices known up front, for example +5 % a year from an escalation rule with a fixed percent, a fixed amount or steps, the increases are projected into the contract value. The early years are then recognized above billing and the late years below. See Price increases.

Hardware per serial number. When a device is Returned or Transferred, its obligation stops on the device's end date (Stopped Date). If the customer kept the device (no credit memo), the rest of its allocated amount is recognized then. If it was refunded, what it recognized is reversed. A swapped device keeps its obligation.

Post the revenue schedule

The Revenue Schedule Entries (from the allocation, the contract or the role center) list per obligation and month the contractual, allocated and adjustment amounts, and whether the row is Posted.

  1. Search for Post Revenue Schedule. Or choose it on an allocation.
  2. Enter the Posting Date and the Post Until Date, usually the last day of the month you close.
  3. Choose OK.

Each active allocation posts its due rows: the adjustment to the revenue account against Contract Asset, and one reclassification so that the contract asset holds a positive net position and the contract liability a negative one. The G/L entries carry the allocation number as document number, the revenue source code, the obligation's dimensions and Microsoft's contract number. Find Entries on a schedule row shows everything for the allocation number and date.

Schedule Post Revenue Schedule in the job queue to run each month after Microsoft's Contract Deferrals Release. An allocation that fails is listed in the result, and the others still post.

When the contract changes

An applied amendment, a hold, a termination (and reopening it) and an applied price increase set Recalculation Needed on the allocation, with Recalculate From and the Recalculation Reason. New lines, charges and devices are found by the next posting run. The next Post Revenue Schedule, or Calculate on the allocation, allocates the rest of the price again from that month. Posted months never change.

An allocation covers one term. When its last month is posted it becomes Closed; Create Revenue Allocations starts the next term from the day after.

Reports

  • Revenue Allocation Schedule: how each contract's price is allocated to its obligations.
  • Revenue Waterfall: the allocated revenue by month for the next 12 months and later.
  • Contract Asset and Liability: the net position of every contract at a date (deferred revenue, allocation adjustments and unbilled revenue), split into contract asset and contract liability.
  • Deferred Revenue Rollforward: how deferred revenue and the allocation position moved in a period.

They are on the Revenue Allocations page, the role center (Reports, Finance) and the Report Center.

What happens in Microsoft Subscription Billing

  • Microsoft's invoices, contract deferrals and Contract Deferrals Release work exactly as before. Bitta Subscriptions writes only its own G/L entries, through a general journal.
  • Uninstalling the app or turning Revenue Allocation off leaves Microsoft's straight-line deferrals as they are.
  • Revenue recognition runs on locked contracts and never needs approval (Approvals and the contract lock). An approved change re-allocates when it is applied.

Limits

  • Amounts are in local currency. Exchange differences are not allocated.
  • The contractual amount of a month is Bitta Subscriptions' day-based estimate of what Microsoft bills, so a cent per month can differ. The adjustments still add up to zero.
  • Price index increases and index steps are not projected, because they are not known up front. When one is applied, the allocation recalculates from then.
  • With Create Contract Deferrals off on a contract, Microsoft recognizes the whole invoice at once, so quarterly or yearly billing shows timing differences until the period ends.
  • Hardware sold as Microsoft's "Sales with Subscription" items (one subscription per serial number) is not an obligation. Only devices in the device register are.

See also

Next step

Ready to try Bitta Subscriptions?