# Analytics and dashboards

The dashboard shows current and historical metrics for the selected team. Use the layout to choose what should be visible, and use detail views to understand the data behind a number. Layout changes do not change subscriptions, invoices, or the underlying snapshots.

## Arrange the view

Choose **Edit layout**, drag widgets into the order you want, resize them, remove cards you do not use, and add them again from the widget picker. Your saved layout applies to your user in the selected team. Analytics began as a separate page and is now collected in dashboard widgets.

## Understand the numbers

### Revenue and customer insights from Alunta and your accounting system

When enabled for your team, the dashboard offers four widgets: **Revenue**, **Annual revenue**, **Invoiced customers**, and **Average invoicing per customer**. They can use accounting data, local Alunta data, or different sources for revenue and customers. A few months of data can already be useful; each card identifies its actual period. Connecting for these insights provides read access and does not itself enable outbound bookkeeping or historical invoice import.

Accounting revenue is the amount booked to your selected revenue accounts. Revenue calculated in Alunta allocates known deliveries over their service periods. It differs from invoicing and payments and does not prove that your accounting system has already posted the accruals. The current month and next three months show expected revenue from business known to Alunta. Unknown future usage and new sales are not guessed as zero.

An administrator can select automatic, Alunta, accounting, or a comparison with two historical bars per month in the source settings. The systems' figures are never added together. With both sources available, automatic uses accounting history until a confirmed Alunta start month; the first invoice alone does not establish full coverage. A changed accounting scope can require confirmation again. Annual revenue uses the same historical source selection and shows the current financial year through the latest completed month. A shorter covered period is identified on the card; a comparison requires equivalent coverage in the preceding year.

Both customer widgets use one source for their entire period. They count unique invoice recipients with a positive booked invoice; credit notes reduce net invoicing. Average net invoicing and customer shares use the same source and period. Customer shares distribute positive net customer amounts. A customer invoiced in three months counts once in the period's headline and may appear in all three monthly bars.

When several teams share accounting books, revenue must be restricted to the team's confirmed accounts. Product mappings and product groups can suggest accounts; suggestions do not prove historical or exclusive ownership. A shared account cannot automatically be divided between teams. Agreement-wide customer data is not presented as one team's customers; existing teams can instead use customers invoiced through Alunta, with that source identified. Customer identities are not merged between systems.

Accounting history refreshes periodically and may lag behind bookkeeping. Cards identify the data period and update time. Missing data and failed reads are marked unavailable or incomplete; a failed refresh can retain previously fetched figures with a warning. Source and account choices are shared team settings, while your personal dashboard layout is preserved.

### MRR and ARR

MRR is the monthly recurring run-rate, normalized across billing intervals, for the currently billable part of subscriptions. Pending MRR uses the same run-rate for subscriptions with a future start, active trial, or pause that are not billable yet; it only counts what is coming in. Committed MRR (below) also takes scheduled churn and scheduled changes into account. Usage-based subscriptions contribute no fixed MRR because their amount depends on consumption. Discounts without an end date are included in the run-rate, while time-limited discounts are intentionally excluded; the corresponding effective or discount-inclusive fields show the billed effect of a time-limited discount when available. ARR is derived from MRR. None of these numbers is the same as bank deposits or the total on a single invoice.

Historical snapshots are views of calculations on particular dates. A chart can therefore lack early dates, and a change to today's rules does not necessarily rewrite old history. Compare period, currency, and definition before concluding that a number is wrong. MRR breakdowns show subscriptions, customers, dates, and amounts behind a calculation; they are explanations, not invoice lists.

## Committed MRR: where MRR is heading

Pending MRR only shows what is coming in: subscriptions that start later, trials that end, and pauses that end. It is a gross inflow figure and does not subtract anything. To see the whole picture, the dashboard also shows **Committed MRR**, which is current MRR plus pending MRR, minus scheduled churn, plus or minus scheduled changes. It is the MRR you end up with once everything already agreed has happened.

- **Scheduled churn** is subscriptions with an end date (such as cancelled ones) that still bill until then. Each one is valued at its MRR on its last billable day, so a plan or quantity change scheduled before the end date is taken into account. The amount is always zero or negative.
- **Scheduled changes** are changes already registered on a subscription that will move its MRR: plan, billing interval, permanent price, number of licenses, tier and discounts without an end date. They can be positive or negative. A scheduled change that cannot be priced is left out and reported separately rather than counted as zero.
- **Not included:** temporary prices and discounts with an end date, in line with how MRR itself is calculated. Usage-based subscriptions contribute no fixed MRR. Committed MRR is not a forecast: it does not include new sales, cancellations nobody has registered yet, or usage.

A pause that starts later on a paying subscription takes its MRR out at the start and puts it back the day after the pause ends. It therefore nets to zero in Committed MRR and only shows in the month-by-month view. A pause that lasts until or past the end date counts as churn on the first day of the pause, because that is the day the subscription stops counting in MRR.

The widget formerly called Pending MRR is now called Committed MRR. It shows the figure with the pending, scheduled churn and scheduled changes lines under it, and each number with details opens the subscriptions behind it. The headline figure opens a month-by-month view of how MRR moves over the coming 12 months. The MRR widget shows scheduled churn next to pending MRR, so a cancellation that still bills until its end date is visible there too. Amounts in other currencies are converted at today's rate; an amount that cannot be converted is reported rather than counted as zero.

## Invoiced customers per month

The invoiced customers card counts how many distinct customers have at least one booked invoice with a positive net amount in each calendar month. Booked Alunta invoices and approved accounting history count; credit notes, zero or negative invoices and unbooked invoices do not, and a customer invoiced several times in a month counts once. The team's AI can answer questions such as "how many customers do we typically invoice per month?" with the `get_invoiced_customers_trend` tool, which returns the count per month without customer names (at most 366 days). The current month is partial, and a month with no known basis is unknown, not zero.

## Analysis across accounts

Analytics can show MRR, ARR, churn, active subscriptions, movements, and monthly overviews. Use period and currency choices consistently. If you have multiple accounts, select accounts in the combined overview and open an individual account for detail. Only accounts you can access are included, and a combined number should be compared using the same period and conversion rule as the individual dashboards.

## Common questions

**Why is the chart empty?** Snapshots may not exist yet, or the period may predate activation. Try a period with data and check the currency.

**Why does MRR differ from an invoice?** MRR is a monthly run-rate normalized across intervals; an invoice may include one-off amounts, multiple periods, consumption, or a different date. Time-limited discounts appear in the effective fields when you need their billed effect.

**Why is a subscription missing?** Check whether it is in trial, paused, has a future start, or is included in Pending MRR. A subscription with an end date is still in MRR until that date and shows as scheduled churn in Committed MRR.

**Can I use the dashboard to correct data?** No. It shows and explains metrics. Correct subscriptions, usage, or invoices in the relevant workflow.