Search docs
Getting started
Running a monthly review
How the numbers work
Docs
/
Running a monthly review
When Morevy stops to ask
The decisions only you can make, and how to change your mind.
Some questions have no correct answer that Morevy can work out from your file. When it hits one, it stops and asks rather than picking for you.
What a decision looks like
Which date should the close read?
The file carries two date columns that disagree: Created and Paid At. February's total is $41,467 on one and $40,912 on the other.
[Use Paid At] [Use Created] [Why does this matter?]
The run pauses there. Nothing is computed past that point until you answer, because everything after it depends on the answer.
The kinds of question it asks
Which rows count as recurring revenue
Asked once per file. The close will not run without it.
Which column carries the date
When two date columns disagree, the choice changes which month each payment lands in.
An unmatched batch
A group of payments that does not line up with any prior subscription.
An inferred plan length
When a plan name suggests a duration Morevy is not confident about.
Mixed currencies
Flagged on the read of the file, with the consequence stated: a total across currencies is a number with no meaning. Splitting the export by currency is the fix.
Before the first close, it states its plan
Rather than asking five questions in a row, Morevy makes its assumptions explicit once and lets you correct any of them:
Close February 2026 on these inputs?
Period: Feb 2026 · Source: payments_export.csv · Basis: Normalized recurring revenue · Revenue scope: 2 of 4 values counted · Durations: from plan names · Segment lens: Plan
[Run it] [Use cash basis instead] [Pick a different month]
Confirm once and it is settled for that conversation. Morevy will not ask you the same thing again unless an input actually changes. Being asked a settled question twice is a fast way to stop trusting a tool.
An unanswered question stays open
A decision you do not answer does not resolve itself. The card stays open, the run waits, and the thread names what it is waiting on. Nothing is dismissed silently, and nothing becomes a default that nobody chose.
Changing an answer
Answers are not final. Open a settled decision and pick a different option, and Morevy asks for a recompute on the new answer.
What it does not do is quietly rewrite the old one. The original stays in the conversation, the new run is a new version, and the movement table that follows tells you what moved between them and why.
Note. This is the difference between a tool you can correct and a tool you have to start over with. A close is a record, and a record you can be wrong in is more useful than one that pretends you never were.
Where your answers are kept
Every answer is saved against the file and shown as source evidence under the figures it affected. Next month, the same questions are already answered, and the close runs without stopping.
Built by and with finance teams
Better decisions start with better context
Join Waitlist