Docs
Current MRR (Monthly Recurring Revenue) refers to the subscription's MRR that is available at the moment. MRR refers to the subscription's recurring revenue for a given period.
Ensure that you use the subscription's MRR metric when you want to view historical information. Selecting Current MRR metric will display the current recurring revenue (in View underlying data) no matter which date is selected.
Listed below are the custom fields available in RevenueStory:
Resource |
Custom Field |
Type |
---|---|---|
Customer |
Business Type |
String |
Business Vertical |
String |
|
Acquisition Cost |
Long |
|
Acquisition Channel |
String |
|
Sales Agent |
String |
|
Customer Type |
String |
|
Acquisition Mode |
String |
|
Account Manager |
String |
|
Customer Success Agent |
String |
|
Solution Partner |
String |
|
Freemium Blacklist Reason |
String |
|
Unique Customer Handle |
String |
|
Product Usage |
Long |
|
Subscription |
Product Usage |
Long |
Sales Agent |
String |
|
Solution Partner |
String |
|
Acquisition Cost |
Long |
|
Cancel Reason |
String |
|
Plan |
Plan Group |
String |
Addon |
Addon Group |
String |
By default, all the custom fields listed in the previous question are available in RevenueStory. However, you need to map these fields with the corresponding fields in Chargebee for us to fetch the information from your site. If you have them enabled, but don't have them mapped to RevenueStory, we can't provide you the relevant data based on grouping by that custom field.
Please contact support to map the custom fields. Once the fields are mapped, all your reports related to custom fields would be available to you.
Please note that reporting on custom fields is only available as part of Revenue Story Premium. To know more about custom fields, please click here.
Here is a comparison of the Standard and Premium Plan in RevenueStory:
S.no |
Feature |
Standard |
Premium |
1 |
Report builder |
Allows the creation of up to five reports. |
No limit on the number of reports. |
2 |
Allows access to information from nine data sources. |
Allows access to all the data sources available in Standard + additional 9 Premium data sources . |
|
3 |
Email Scheduling |
Allows three email schedules (per user). |
Supports unlimited email schedules. |
4 |
Dashboard Sharing |
Does not allow sharing of dashboard templates. |
Supports unlimited dashboard sharing. |
5 |
Custom fields |
No custom fields support for metrics/reports. |
Custom field supported for pre-built reports and data segmentation. |
6 |
Custom Fields - Filter & Group by Support |
Does not support reporting on custom fields |
Supports reporting on custom fields |
7 |
Site consolidation |
Does not support consolidated reporting. |
Supports consolidated reporting. |
8 |
Alerts |
Supports only one alert per site. |
Supports unlimited alerts for key metrics. |
9 |
Goals |
No support for goals. |
Supports unlimited goals for key metrics. |
10 |
Premium reports |
- |
A specially curated list of premium reports. (45+) |
You can analyze the data by Plan or Addon using the Monthly Component History and Yearly Component History and Product Type in Visual reports.
Classic reports are reports that are available in Chargebee. Chargebee offers different types of reports that are broadly grouped under subscriptions, accounting, revenue recovery and transactions.Learn more
What is Monthly Recurring Revenue (MRR) and how is it calculated in Chargebee?
Committed Monthly Recurring Revenue(CMRR) is the Monthly Recurring Revenue (MRR) that we can expect to get in the future from activations, scheduled changes, and cancellations on subscriptions in addition to the current MRR. Based on this, CMRR can be higher or lesser than the current MRR. Also, CMRR is similar to MRR as it calculates the normalized monthly recurring revenue that one can expect to earn from subscriptions.
Expected revenue is an invoiced revenue that you can expect to receive from your customers, by end of the day or month. The composition of your expected revenue metric is dependent on your site-level settings. This could include Payments, refunds, revenue from pending renewals, revenue from expected trial conversions, and revenue from overdue invoices. Expected revenue is not the normalized monthly revenue but the overall revenue that is expected by the period's end (day or month). The daily expected revenue includes invoices in dunning.
In Chargebee expected revenue is available in two variants.
Expected revenue this day - Using this metric you can understand the revenue that you expect to receive by the end of the day.
The daily expected revenue is calculated as received revenue (default) + upcoming renewals (default) + trial and future subscriptions with cards (optional) + invoices in dunning (optional) + monthly revenue calculations (optional).
Expected revenue this month - Using this metric you could understand the revenue that you expect to receive by the end of the month.
The monthly expected revenue is calculated as received revenue (default) + upcoming renewals (default) + trial and future subscriptions with cards (optional) + monthly revenue calculations (optional)
For example, if you have a quarterly plan with an amount of $300 from a subscription, which is expected to be activated in the current month, CMRR will be $100 whereas expected revenue will be $300 from the subscription.
Generally Accepted Accounting Principles (GAAP) is a traditional accounting methodology that refers to a common set of accounting principles and standards issued by the Financial Accounting Standards Board (FASB). GAAP metrics do not consider delayed profitability into account. These metrics rely on the sales that have already been made.
However, with the SaaS business, things are different. To begin with, Monthly Recurring Revenue (MRR) is not a reportable GAAP revenue. The revenue is not calculated based on past sales, but current and predicted subscriptions. In simple terms, MRR is a predictable measure and not a recognized revenue. MRR calculates an expected revenue number to clarify where your company's performance is headed and indicates what you can expect based on the existing customers, sales, upgrades, churn, and so on.
Several metrics have been adopted across the SaaS industries to keep track of their business performance. Metrics such as Monthly Recurring Revenue (MRR), Annual Recurring Revenue (ARR), Committed Monthly Recurring Revenue (CMRR), Churn, and so on have become standard when measuring the performance of a SaaS company.
MRR Retention Cohort is a metric that shows how you've been retaining the MRR earned from a cohort of subscribers activated in a month, over the subsequent 12 month period. A retention rate greater than 100% is great news.
Let's understand this with a few examples:
Example 1:
A bunch of customers activated in a month (say Jan 2017) with an initial MRR of $1000 are growing to $5000 MRR in Dec 2017. Your retention rate for Dec 2017 is increased to 500% in this case.
Example 2:
If you had $1000 MRR at the beginning of a month and lost $100 MRR due to churn, but still gained $200 MRR from product upgrades in the same month, the MRR Retention Rate for that month would be 110%.
Cohorts are good indicators of both Lead quality (when you traverse growth row by row) and the impact of your product and engagement activities (when you traverse by columns). Also, look at your MRR cohort in conjunction with the Subscription Retention Cohort to see how many customers in the original cohort have been retained after 12 months. One big customer could be pulling the entire cohort forward, or one churn could cause a huge drop. If you see a sudden up or down in percentage, you need to look at the subscription retention cohort to see if this is a trend or a one-off caused by few customers.
MRR retention cohort is an OOTB report available under Reports Explorer which provides a monthly view of the cohort retention rates for the last 24 months. If your requirements are to create a customized MRR retention cohort, this can be achieved using a report builder.
To build a custom MRR retention cohort in Report builder follow these steps.
Click RevenueStory > Report Builder.
Select Summary Report.
Select Subscription activation date from Subscription resource in the row grouping. Default grouping is year and month.
Select MRR change date from Monthly subscription history resources in the column grouping. Default grouping is year and month.
Select MRR in the values. Default aggregation is Sum.
You will be getting the MRR trends of subscriptions cohortized by activation month and year. The customer can choose a filter to get data as per his requirements.
Note
Apply filters by selecting the last date of the previous month and not of the month for which the cohort analysis is needed. The underlying data can be obtained by selecting the build as a detailed report option on the summary page. e.g. for cohort analysis starting from January 2021, we should select the activation date as "is after" 31 Dec 2020 and not 1 Jan 2021.
RevenueStory imports the same logic from the Chargebee for exchange rates. Transactions made in the additional currencies will be converted to the base currency using the exchange rates that you configure in them, for reporting purposes. Learn more.
If you choose Auto as the Exchange Rate Type, RevenueStory uses the exchange rates available with currency layer and Open Exchange Rates.
Here's how RevenueStory picks exchange rates:
If today is 4th August 2016,
The previous day's (3rd August 2016) closing rates will be synced with RevenueStory from the exchange rate sources.
The synced rates will be used for transactions occurring from 00:30 UTC onward.
For transactions occurring before 00:30 UTC, RevenueStory will use the closing rates from 2nd August.
If RevenueStory fails to sync with the exchange rate sources on 4th August 2016, the last available exchange rates will be used.
For transactions dated before 2011, the closest available exchange rate for 2011 will be used for conversion.
The Lifetime Value (LTV) is a metric that provides the financial worth of a subscription during its lifetime, to the business. In other words, it is the average revenue that a subscription generates until it cancels.
Lifetime Value = Paid subscription lifetime * Average Revenue per paid subscription (ARPS)
Average Revenue per paid subscription is calculated as the ratio of MRR for the month and total active paid subscription for the month.
Average Revenue per Paid Subscription (ARPPS) = Total MRR / Total Active Paid Subscriptions
Paid subscription lifetime is calculated as the inverse of the average churn rate for the last three months
Paid subscription lifetime = 1/Avg(Churn rate current month + Churn rate previous month + Churn rate the month previous to the previous month)
Example
Consider the duration of three months from January to March.
At the end of January, the total active paid customers were 600, and the churn for January was 10. The churn rate % is calculated as (10/600)*100 = 1.75.
At the end of February, the total active paid customers were 590, and the churn for February was 20. The churn rate % is calculated as (20/590)*100 = 3.5.
The same procedure applies to the upcoming months.
If you take the inverse of the average of the last three months' churn percentage, you would be able to get the Lifetime of a subscription.
If you multiply the lifetime with the average revenue per paid subscription, you will arrive at the lifetime value of a subscription.
Note The "lifetime value" metrics in Revenuestory do not have the "View Underlying Data" option. This is because it is merely a projection of how many months into the future the subscription would exist. However, you can download the entire report using the Download Report option:
Once the time zone is altered, the data displayed in the Dashboard will vary accordingly and align to the new time zone.
However, the change in alignment will leave a time gap or time overlap depending on the new time zone you choose.
Time Overlap: Time overlap is when the new time zone is shifted from UTC to a time zone that falls before UTC. i.e., New time zone = UTC+[hh]:[mm]. Like IST, which is UTC+05:30 hours.
Say you change the time zone of your Chargebee site from UTC to IST in January. This will ideally mean that all the transactions that had gone through in the last 5.30 hrs in December will now also belong to January, which will leave the metrics with an overlap.
To handle this data overlap, Chargebee will not shift the data to the current month since the data was added in last month already.
Time Gap: Time gap is when the new time zone is shifted from UTC to a time zone that falls after UTC. i.e., New time zone = UTC-[hh]:[mm]. Like PST, which is UTC-07:00 hours.
Say you change the time zone of your Chargebee site from UTC to PST in January. This will ideally mean that all the transactions that had gone through in the first 7 hours of UTC time in January will now belong nowhere, leaving an unaccounted 7 hours of data in Chargebee metrics.
To handle this data gap, Chargebee will add the data in the gap to current month's data. In this case, it will be added to the data of the 1st of January.