Scope and limitations

Morevy analyses recurring revenue from payment history. The boundaries below are worth understanding before you rely on it.

Data source

Morevy works from your billing activity. Stripe can be connected directly with a restricted, read-only key, and Morevy pulls the payment history itself. Every other system comes in as an exported file, and its figures reflect the file as at its upload date; refreshing means exporting again.

The file route for other systems is deliberate. Where a billing system exposes no complete read interface, a partial synchronisation produces figures that are wrong in ways that are difficult to detect, so those systems come in as an export you can inspect.

Financial scope

Morevy reports on recurring revenue. It is not an accounting system. It does not produce statutory accounts, lender packs or tax filings, and it does not address costs, payroll or any line below revenue.

Use it for revenue analysis. Use your accounting system for accounts.

Retention ratios

Gross and net revenue retention are computed on the normalized recurring revenue basis, and on a file whose metric column already states recurring revenue per month (a close labelled "as stated").

On a cash basis these ratios have no valid definition, because a customer who prepays several periods registers as a total loss in every period that follows. Morevy reports them as unavailable, naming the basis that would support them, rather than presenting an approximation under a recognised name.

Outbound communication

Morevy names the customers behind each movement and drafts commentary for your review. It does not contact them. No message is sent from the product to a customer.

Revenue structures not yet modelled

Consumption-based bundles

Prepaid credit or class packs are not recognised in proportion to consumption.

Third-party marketplaces

Revenue collected by an aggregator rather than your own billing may not appear in the export.

Multiple currencies

Mixed currencies in one file are flagged on the read for you to act on, and never combined at an assumed rate. A file you do not reject is summed as it stands, so keep each export to one currency. Detection relies on the export carrying a currency column.

Usage-based charges

Variable charges are recognised where they cleared rather than modelled as a rate.

Customers behind a figure

The close is a reconciled financial statement, and the customers Morevy names behind a movement leg are engine figures, not estimates. What Morevy does not do is rank customers by attention or predict who will leave. Context that does not appear in a payment file will often be decisive, and that judgement stays with you.