Why subscription metrics are so often wrong
Every SaaS finance team has lived through this. The MRR number in the billing system disagrees with the one in the board deck. Churn looks different depending on who calculated it. Expansion revenue is counted twice in one month and missed the next. Revenue recognition is a monthly spreadsheet exercise that nobody wants to inherit.
The cause is that subscription metrics depend on classifying every revenue movement correctly: new, expansion, contraction, churn, reactivation. Billing systems are built to collect money, not to classify it, and accounting systems record revenue, not customer lifecycle. The logic has to be built deliberately, at invoice level, and then kept consistent.
What our subscription analytics service covers
We build subscription analytics from the ground up, starting with invoice and contract data and ending with the reporting your board and investors expect.
- MRR and ARR reporting with a full movement bridge: opening, new, expansion, contraction, churn, reactivation, closing
- Customer and revenue churn, gross and net, calculated consistently and explained
- Net revenue retention and gross revenue retention by cohort, segment, plan and acquisition channel
- Cohort analysis showing how each customer vintage behaves over time
- Customer lifetime value, customer acquisition cost and payback period, reconciled to actual spend
- Revenue recognition automation under IFRS 15 and FRS 102: deferred revenue schedules generated from invoice data rather than maintained by hand
- Investor and board reporting packs with the SaaS metrics a diligence process will test
- Churn and retention forecasting built from lifecycle data, so the forecast reflects how customers actually behave
Invoice-level revenue recognition
Most subscription businesses recognise revenue in a spreadsheet that takes each invoice and spreads it over the service period. It works until there are a few hundred invoices a month, mid-term upgrades, credit notes and multi-year contracts, at which point it becomes a monthly risk.
We automate this. Every invoice line is matched to its service period and recognition schedule, deferred revenue is calculated by period, and the output reconciles to both the billing system and the ledger. This is the same logic that sits at the core of our patent-pending Revenue Intelligence platform, and for many clients a consultancy engagement is the first step towards running it on the platform.
Forecasting churn and retention
A SaaS forecast is only as good as its churn assumption, and a single blended churn rate hides more than it shows. Enterprise customers on annual contracts churn differently from monthly SMB customers. Customers in their second year behave differently from those in their first month.
We build retention forecasts from lifecycle classification: each customer is placed in a stage based on tenure, plan, usage and payment history, and the forecast applies retention curves by stage and segment. The result is an MRR forecast that explains itself, and a view of where retention risk is concentrated before it turns into churn.
Preparing for investors and diligence
When a funding round or a sale is on the horizon, the subscription metrics come under scrutiny. Diligence teams rebuild MRR from invoice data and compare it with what the business has been reporting. Discrepancies cost credibility, and sometimes valuation.
We prepare businesses for this by building the metrics the way a diligence team would, from the source data, with every definition documented and every movement traceable to an invoice. If someone is going to rebuild your MRR from invoices, it is far better that you did it first.
Who this is for
SaaS and subscription businesses from around £1m ARR upwards, where the volume of invoices has outgrown the spreadsheet and the questions from the board have outgrown the billing system's reports. Also finance teams in subscription-adjacent businesses, such as memberships, managed services and software with recurring maintenance, where the same metrics apply.
If you cannot currently produce an MRR bridge that reconciles to your ledger, start here.
Good questions, straight answers
What is the difference between MRR and recognised revenue?
MRR is a normalised measure of the recurring revenue under contract at a point in time, used to track growth and churn. Recognised revenue is what the accounts report for a period under IFRS 15 or FRS 102. They should reconcile, but they are not the same number, and confusing them is one of the most common errors in SaaS reporting.
Can you automate revenue recognition from Stripe or Xero data?
Yes. We build recognition schedules from invoice-level data in billing systems such as Stripe, Chargebee and Recurly, or directly from invoices in Xero and QuickBooks, and produce the deferred revenue movements your accountant needs each month.
How does this relate to the Profitcura Revenue Intelligence platform?
The platform productises the same invoice-level recognition, lifecycle classification and retention forecasting logic we have built for clients. A consultancy engagement is often the first step: we build the metrics for your business, and where the platform fits you can move onto it as a pilot customer.
Sectors where this work lands
- SaaS and subscription businesses
SaaS FP&A, MRR and churn analytics, revenue recognition automation and investor reporting for subscription businesses from first funding round to exit.
- Accountancy practices
Automated bookkeeping and document processing, client reporting dashboards and the advisory tooling that lets a practice sell insight rather than hours.