> For the complete documentation index, see [llms.txt](https://docs.morevy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.morevy.ai/docs/running-a-close/when-morevy-stops-to-ask.md).

# When Morevy stops to ask

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

> **Should the March refund reduce February or March?**
>
> A $209 refund was issued in March against a charge taken in February.
>
> \[Reduce February] \[Reduce March] \[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 membership revenue** | Asked once per file. The close will not run without it.                |
| **Cash or recurring revenue**              | Asked once per file. Changes every figure.                             |
| **Refund timing**                          | Which month absorbs a refund issued against an earlier charge.         |
| **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.    |

## 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: net recurring revenue · 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.

## 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.

{% hint style="info" %}
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.
{% endhint %}

## Where your answers are kept

Every answer is saved against the file and shown in the audit trail under the figures it affected. Next month, the same questions are already answered, and the close runs without stopping.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.morevy.ai/docs/running-a-close/when-morevy-stops-to-ask.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.