# Reporting Plock's reporting section provides insights into your subscription business. All metrics are computed from your subscription data — the numbers you see are derived from the subscriptions, scheduled changes, and dates you configure in the platform. ## Revenue metrics ### MRR (Monthly Recurring Revenue) The recurring revenue actually being billed in a given month. MRR is based on what is happening in billing right now: * A subscription contributes to MRR from its **start date** (the billing cycle anchor) * MRR changes when a **scheduled change takes effect** and billing updates accordingly * MRR decreases when a subscription reaches its **end date** and stops billing A subscription with a future start date does not count toward MRR until billing begins. ### CMRR (Contracted MRR) The recurring revenue you are contracted for, based on your subscription data — including known future changes. CMRR differs from MRR in *when* it recognises revenue: * A subscription contributes to CMRR from its **Signed date**. If no Signed date is set, Plock falls back to the subscription's creation date. * CMRR uses the **final contracted price** rather than any ramp-up pricing. If a subscription starts at 500/mo for three months and then goes to 1,000/mo, CMRR reflects 1,000 from the Signed date. * Scheduled changes affect CMRR from the date the change was created (or its Signed date, if set), not the date the change takes effect. **Example**: You create a subscription today with a start date next month. MRR is unchanged today — billing hasn't started. CMRR increases today because the subscription exists with a Signed date. **Indexation and CMRR**: If a subscription has price indexation configured, CMRR looks up to 24 months ahead and includes future indexation events in its calculation. The CARR indexation mode setting (under Settings > Reporting) controls whether this look-ahead is included or excluded — useful when indexation is automatic but not contractually guaranteed. ### Committed ARR MRR multiplied by 12. The annualised value of fixed recurring revenue currently being billed. This is what many people simply call "ARR" — in Plock it is called Committed ARR to distinguish it from usage-based revenue (see below). ### Contracted ARR (CARR) CMRR multiplied by 12. The annualised value of contracted revenue. CARR typically appears before Committed ARR — reflecting subscriptions from their Signed date rather than their billing start date. This makes CARR a leading indicator: it shows revenue you are contracted for but may not yet be billing. ### Usage ARR Usage fees (from metered products) multiplied by 12. This captures the annualised value of usage-based revenue, separate from fixed recurring fees. ### Run-Rate ARR Committed ARR + Usage ARR. The total annualised revenue combining both fixed recurring and usage-based charges. This gives the most complete picture of current revenue for businesses that have both fixed and usage-based billing. ### A note on ARR naming Plock distinguishes between Committed ARR (fixed recurring revenue) and Usage ARR (usage-based revenue) because businesses with both types of billing need to track them separately. Run-Rate ARR combines the two. If your business only has fixed recurring revenue (no usage-based billing), Committed ARR and Run-Rate ARR will be the same number. In that case, "ARR" and "Committed ARR" mean the same thing — Plock uses the longer name to stay consistent across all types of businesses. ## How MRR and CMRR timing works in practice The difference between MRR and CMRR comes down to which dates Plock reads from your subscriptions: \| What happened | MRR uses | CMRR uses | |-|-| | New subscription | Start date (billing cycle anchor) | Signed date (or creation date) | | Scheduled change (upsell, downsell) | Date the change takes effect | Date the change was created or its Signed date | | Subscription ended | End date (billing stops) | Notice of end date | ### CMRR churn timing and "Notice of end date" Just as CMRR uses the **Signed date** to know when revenue was contracted, it uses the **Notice of end date** to know when revenue is leaving. This is the date you became aware of the cancellation — not necessarily the date billing actually stops. If no Notice of end date is explicitly set, Plock derives it automatically from the subscription's history by finding when the end date was first recorded. **Example**: A subscription has an end date of August 1, but the cancellation was communicated in March. CMRR churn appears in March — the month the cancellation became known — rather than August when billing actually stops. This gives an earlier signal that revenue is leaving. ## Movement metrics Movement metrics show how revenue changed from one month to the next. They are available for both MRR and CMRR: * **New**: Revenue from accounts that had zero recurring revenue last month and now have some. The account is new to your revenue base. * **Expansion**: Revenue increase from accounts that already had recurring revenue last month. This includes upsells, price increases, or discounts ending. * **Contraction**: Revenue decrease from accounts that still have recurring revenue, but less than last month. This includes downsells, price reductions, or new discounts. * **Churn**: Revenue lost from accounts whose recurring revenue dropped to zero. The account no longer has any active subscriptions contributing revenue. Movements are detected by comparing each account's total recurring revenue between two consecutive months. An account is classified into exactly one movement category per month based on what changed. These metrics can be filtered by account and subscription in the drill-down view. ## Retention metrics ### NRR % (Net Revenue Retention) What percentage of last month's revenue was retained or grown from existing accounts — excluding revenue from new accounts. Above 100% means your existing accounts are generating more revenue than the previous month (expansion outweighs contraction and churn). ### NRR (LTM) % Net revenue retention calculated over the last twelve months rather than month-to-month. ### GRR % (Gross Revenue Retention) Revenue retained from existing accounts, excluding expansion — always 100% or below. GRR isolates pure retention: how much revenue you kept without expansion masking losses. ## Usage metrics Usage fees are monthly usage-based charges from metered products, tracked separately from fixed recurring fees (MRR). When annualised (× 12), they become Usage ARR — which combined with Committed ARR gives Run-Rate ARR. ## Cash flow (Total Billings) Total billings is the total invoiced amount in a specific month. This differs from MRR — for example, an annual prepayment creates a large billing event in one month, but only 1/12 of that amount counts as monthly recurring revenue. Use billings data to understand cash flow separately from revenue recognition. ## Available reports Plock provides the following exportable reports: | Report | What it covers | | --------------------------- | ------------------------------------------------ | | Snapshots | Usage data with product/plan details and revenue | | MRR | Monthly recurring revenue over time | | Revenue | Revenue breakdown by type | | New Billings | New billing activity | | Projection | Revenue projections for the current period | | Account Balance | Account-level balances | | MRR per account per month | Account-level MRR over a 13-month period | | CMRR per account per month | Account-level CMRR over a 13-month period | | Usage per account per month | Usage metrics per account over time | | SaaS Metrics | MRR, churn, expansion, NRR, and other KPIs | | Expected Cash Collection | Forward-looking cash flow forecast | | Projected MRR per account | Forward-looking MRR per account | | Projected CMRR per account | Forward-looking CMRR per account | Reports are exported as CSV and can be delivered via email or to a cloud drive. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.plock.io/plock-overview/guides/reporting.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.