> 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/reading-the-revenue-movement.md).

# Reading the revenue movement

The movement table is the core of a close. It starts at last month's balance, applies everything that changed, and lands on this month's.

| Component  | Members | Amount      |
| ---------- | ------- | ----------- |
| Starting   | 204     | $40,018     |
| New        | 20      | +$4,016     |
| Returned   | 4       | +$826       |
| Growth     |         | +$1,644     |
| Reduction  |         | ($529)      |
| Lost       | 19      | ($4,508)    |
| **Ending** | **209** | **$41,467** |

## What each row means

|               |                                                                       |
| ------------- | --------------------------------------------------------------------- |
| **Starting**  | What you were earning from existing members at the end of last month. |
| **New**       | Members who joined this month.                                        |
| **Returned**  | Members who had lapsed and came back.                                 |
| **Growth**    | Existing members paying more than last month, usually an upgrade.     |
| **Reduction** | Existing members paying less. A downgrade, not a cancellation.        |
| **Lost**      | Members who left.                                                     |
| **Ending**    | Starting plus everything above.                                       |

Growth and Reduction have no member count because they move money, not people. The same member appears in neither New nor Lost.

## Reading the bars

The bar column is a bridge, not a bar chart. Each leg starts where the previous one finished, so the bars step down the page and you can see the legs close the gap between opening and closing without reading a single figure.

The scale runs from zero. That means a small leg looks small next to a large balance, which is honest: $4,016 really is about a tenth of a $40,018 book.

## Checking it adds up

The headline above the table already tells you whether it ties. If you want the detail, the reconciliation section shows each check:

* Ending balance ties — $41,467 computed vs $41,467 reported
* Starting plus movement equals ending

When every check passes it collapses to one line. When one fails it opens automatically, because then it is the most important thing on the page.

{% hint style="info" %}
Money is shown to the dollar. Because each row is rounded, the rows can add to a dollar or two either side of the total. Morevy says so underneath the table when it happens, rather than leaving you to wonder whether the column is broken.
{% endhint %}

## Going deeper

Click any amount to see the members behind it. Asking *who is in Lost for February* returns the actual names, what each was worth, and whether they account for the whole leg.

If the named members do not add up to the leg total, Morevy says that too, rather than presenting a partial list as complete.


---

# 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/reading-the-revenue-movement.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.