> 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/breaking-a-close-down.md).

# Breaking a close down

A close tells you revenue moved. A breakdown tells you where.

Ask in the same conversation:

> break that down by location

You get the same movement table, once per value of that column:

| Location  | Starting    | New         | Lost         | Net         | Ending      |
| --------- | ----------- | ----------- | ------------ | ----------- | ----------- |
| Downtown  | $28,140     | +$2,910     | ($2,006)     | +$1,204     | $29,344     |
| Eastside  | $11,878     | +$1,106     | ($2,502)     | ($1,145)    | $10,733     |
| **Total** | **$40,018** | **+$4,016** | **($4,508)** | **+$1,449** | **$41,467** |

The rows still add to the same total. A breakdown is the same arithmetic sliced differently, not a second calculation that might disagree.

## What you can break down by

Any column in your file with a manageable number of distinct values. In a typical payment export that means:

* **Plan** or product type
* **Location**, for multi-site businesses
* **Staff member**, if your system records who the account belongs to
* **Payment status**, which separates completed payments from refunds and disputes

Morevy shows you which columns are available. If a column has hundreds of distinct values, it is a poor lens and Morevy will say so rather than render a table with 300 rows.

## Reading a segment table

Two things are worth knowing.

**Colour only appears when the column has both directions in it.** If every segment lost revenue this month, nothing is green, and the table does not draw a midline that nothing crosses. A wall of red tells you less than a plain column of figures.

**An "others" row rolls up the tail.** When a column has a long tail of small values, the largest are listed and the rest are summed into one row, so the total still ties.

## Using it well

The useful question is rarely "how did each location do". It is "is the number I am worried about concentrated or spread".

A $4,508 loss spread evenly across every plan is a pricing or seasonality story. The same $4,508 sitting almost entirely in one location or one product is an operational story. Same total, entirely different week ahead.

{% hint style="info" %}
Breakdowns are computed from the same rows and the same answers as the close above them. If you change a filter, both are marked stale together, and neither silently updates while you are looking at it.
{% endhint %}


---

# 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/breaking-a-close-down.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.