system for a new product. This is sensible because high
growth rates measuring growth from an insignificant base
level are usually not sustainable in the long run. The burn-
in period for a constituent may be longer than two years
whenever there is known, or suspected to be, significant
account migration from other systems even after this
time. Note, however, that Zuora does not have perfect
information about these events, and some migration
of accounts from another billing platform may not be
excluded (however, any extreme outliers will be removed
as an outlier, as described below.)
CALCULATION PERIOD
As will be described in more detail below, revenue for
the SEI is measured in a one-year rolling window. The
purpose of the one-year window is to remove the impact
of seasonality. After the burn-in period, the next year
of system activity for a constituent is used to establish
the baseline for the measurement of future growth. As
a result, a typical tenant using the Zuora service is first
used as an index constituent when their one-quarter
growth is calculated two years and one quarter after they
went live on Zuora system.
REMOVAL OF INDEX CONSTITUENTS
Decommissioning of tenants and the causes are tracked
in the Zuora CRM system. System activity for a tenant
is suspended from the SEI report calculation beginning
in whatever quarter their decommissioning is noted,
and whenever the reason is other than business failure.
Business failure decommissionings are allowed to remain
in the SEI report throughout the decommissioning as this
reflects organic contraction on the tenant activity, while
voluntarily decommissioning tenants are removed as
that is a case of non-organic change in the activity. Note
that this may fail to exclude migration of accounts from
the Zuora system that preceded the acknowledgment of
decommissioning; such migration off the Zuora system
would appear as negative growth and may influence the
SEI data calculation (however, any extreme points will be
removed as an outlier, as described below).
POST-LIVE INVOICE CONVERSION
The migration of accounts and invoices from another
billing system to Zuora usually occurs before or
immediately after a tenant goes live on the platform.
Occasionally, however, a company converts accounts
and invoices to the system at a later date. Whenever
such a conversion is known to occur, the corresponding
quarter(s) of system activity will be removed from the SEI
calculation for those companies. The data points for those
companies will be filled as necessary with the average
of the quarters before and after the conversion. Note
that Zuora does not always have complete information
about these events and it is possible that some post-live
revenue conversion may go into the index calculation and
would appear as growth (however, any extreme points will
be removed as an outlier, as described below).
MULTI-TENANT AND MULTI-ENTITY
In cases where a single parent company operates either
multiple entities or multiple tenants in the Zuora system,
the system activity for each entity or tenant is treated
as if it were a separate constituent for purposes of SEI
report calculations. A separate tenant is the specific case
of multiple entities operating with fully separate product
catalogs, databases, etc. The base date for beginning the
burn-in period on a tenant or child entity is the later of
the customer go-live date or the earliest date for which
system activity for the tenant or entity is first processed.
CALCULATING CONSTITUENT GROWTH
Once a tenant on the Zuora service becomes an index
constituent, its activity is calculated every quarter with a
one-year rolling window. Many subscription businesses’
activities are subject to seasonality, although the precise
nature of the seasonal effect varies significantly. Using a
one-year window for SEI calculations removes the effect of
seasonality. This means that if the SEI data increases (or
decreases) over any quarter, it is because that quarter was
better (or worse) than the same quarter one year prior;
not the quarter immediately preceding it. The activity
measure for SEI data calculation is the one-year prior
total of Invoice Item amounts generated from recurring
and usage Rate Plan Charge objects in the Zuora billing
business object model. One-time charges are excluded
from the calculation, as the SEI is intended to reflect the
growth in recurring activity. Whether Invoice Items are
for recurring, usage, or one-time activity is given by the
Rate Plan Charge object linked to the Invoice Items in the
object model. Note also that any activity a constituent
makes that is outside the Zuora system is ignored by the
SEI calculation. A consequence of this is in cases where
a division of a large corporation uses Zuora for a single
product line; that constituent is treated as if it were a small
company, independent of the larger organization.
15