> 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/getting-started/the-three-questions.md).

# The three questions

Before any calculation, Morevy confirms three things about your file. Your answers are recorded in the audit trail alongside the figures they produced.

```mermaid
flowchart TD
    A["Upload"] --> B["1   Column mapping"]
    B --> C["2   Revenue classification"]
    C --> D["3   Reporting basis"]
    D --> E["Ready to close"]
    C -.->|"unconfirmed"| F["Close does not proceed"]
```

{% stepper %}
{% step %}

### Column mapping

Morevy proposes a mapping and you confirm it.

It examines your headers and the values beneath them to identify which column holds the customer, the date and the amount. The proposal is usually correct and requires only confirmation. Where it is not, you correct it, and the mapping is saved against that file.
{% endstep %}

{% step %}

### Revenue classification

This determines what every subsequent figure represents.

A payment export typically contains more than subscriptions: trials, one-off purchases, retail, late fees, account credits and refunds. Without classification, a recurring revenue total silently includes items that are not recurring revenue.

Morevy presents each distinct value with **both its row count and its value**, because a row count alone is insufficient to judge materiality:

| Plan              | Rows  | Value    |
| ----------------- | ----- | -------- |
| Monthly Unlimited | 2,400 | $480,000 |
| Quarterly Plan    | 400   | $240,000 |
| Trial             | 50    | $1,500   |
| Retail            | 120   | $3,600   |

*Illustrative figures.*

{% hint style="warning" %}
**The close does not proceed until this is confirmed.** This is not a dismissible warning.

A close that classifies retail as recurring revenue is incorrect in a way that is unlikely to be detected, and every subsequent decision inherits the error.
{% endhint %}
{% endstep %}

{% step %}

### Reporting basis

A customer pays $600 in January for a three month plan. The business may recognise $600 in January, or $200 in each of three months.

Both are valid and they answer different questions. You select the basis, and every close states which one it reflects.

See [Cash vs recurring revenue](/docs/how-the-numbers-work/cash-vs-recurring-revenue.md).
{% endstep %}
{% endstepper %}

## Revising your answers

All three are saved against the file and reused in subsequent periods.

Revising one after figures have been produced marks those figures as computed under superseded settings and offers to recompute. Displayed figures are not silently revised.


---

# 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/getting-started/the-three-questions.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.