Introduction

Morevy takes your billing or payment activity, synced from Stripe or exported from any system as a file, and turns it into two things:

• A reconciled movement bridge. Starting recurring revenue, every classified change, ending recurring revenue. The legs add up, and Morevy says so when they do not.

• An explanation you can defend. Which customers drove each change, the source rows behind them, and what still needs your judgment.

You ask in plain language. You get back tables and figures, not a paragraph with numbers buried in it.

• Export your payments - What file to pull from your billing system, and what has to be in it.

• The three questions - What Morevy asks about your file before it will run anything.

• Run your first monthly review - Ask for a month and read what comes back.

• Cash vs recurring revenue - The one decision that changes every figure. Worth five minutes.

Who it is for

The person who has to explain the number.

Morevy is built for the hands-on finance owner at a recurring-revenue company: the person who reconciles customer movement each month and prepares the explanation someone else will question. That includes finance leads doing it in-house and fractional CFOs; today each client business runs as its own workspace.

What matters is not the industry. It is that revenue repeats, some of it is prepaid, and the billing export is the best record you have.

Note. On the accounting boundary. Morevy reports operational recurring revenue. It is not a general-ledger close, a revenue-recognition system, bookkeeping, tax or audit. Use it to explain movement; use your accounting system for accounts.

What makes it different

Morevy will not show you a number it cannot trace.

Every figure on screen is computed by an engine from the rows you uploaded. The assistant decides what to show and how to explain it, but it never authors a figure. AI drafts commentary after the calculations finish. If the engine has not produced something, nothing renders in its place.

That sounds like a technical detail. It is the reason you can put the number in front of someone else.

Note. Morevy refuses to run a close until you have confirmed which rows count as recurring revenue, and where column meanings are unconfirmed it narrows the close to cash collected rather than guessing at spreading. A confident wrong number is worse than no number, and a close that quietly counted a one-off sale as recurring revenue is the kind of mistake nobody catches for months.

What you get

Revenue movement

The starting balance, what came in, what left, the ending balance. The legs add up to the total, and Morevy says so when they do not.

Breakdowns

The same movement split by plan, status, location: any column with a short list of repeated values.

The customers behind a figure

Open any movement leg to see exactly who is in it. Balances and ratios are totals rather than lists.

Retention ratios

Gross and net revenue retention on the normalized recurring revenue basis. On cash collected they are withheld, with the reason shown, because collections alone cannot support them honestly.

Source evidence

Every figure traces back to the rows it came from and the answers you gave.

What Morevy does not claim

Morevy identifies the customers behind a movement. It does not infer why someone paid more, paid less, or stopped paying from billing activity alone. A payment file records what happened, not the commercial reason for it.

Where the data cannot establish intent, Morevy presents the case for review rather than assigning a confident label.