> 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/your-first-close.md).

# Your first close

Ask in plain language:

> close February

That is the whole command. No form, no date pickers.

## What you see while it runs

Morevy shows its work as a list of named steps, each one ticking over as it completes:

|                            |                             |
| -------------------------- | --------------------------- |
| Confirm run plan           | Net basis, source as mapped |
| Reconcile revenue identity | Ties at $41,467 net ending  |
| Movement and segments      | 209 members, Status lens    |

The steps are named for the work, not for what the assistant is doing. There is no "Thinking". This part is arithmetic, and the evidence that it happened is the reason to trust the figure underneath.

## It will stop and ask

Before the first close in a conversation, Morevy states its plan and waits:

> **Close February 2026 on these inputs?**
>
> Period: Feb 2026 · Source: payments\_export.csv · Basis: net recurring revenue
>
> \[Run it] \[Use cash basis instead] \[Pick a different month]

Confirm once and it is settled for the rest of the conversation. Morevy will not ask you the same question twice.

It stops again if it hits something only you can decide, such as a refund that could reduce either the month it was taken or the month of the original charge.

## What you get back

A headline figure, then the evidence for it:

> **Feb 2026** **$41,467** +$1,449 from the opening balance · the movement ties

Underneath that sits the revenue movement table, which is covered in Reading the revenue movement.

{% hint style="success" %}
**"The movement ties"** means the opening balance plus every leg equals the closing balance, checked by Morevy rather than asserted. If it does not tie, it says so and by how much, instead of quietly presenting a total that does not add up.
{% endhint %}

## Asking follow-ups

Once a close exists, ask anything about it in the same conversation:

* *Who churned in February and what did it cost?*
* *Why did revenue move?*
* *Break that down by location*
* *How does this compare to January?*

Each answer is a real computation against your file, not a summary of what is already on screen.


---

# 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/your-first-close.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.