> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/financial-statements/managing-statements/customize-a-financial-statement/customize-headings-and-spacers.md).

# Add headings and spacers

{% hint style="info" %}
User permission: Manage Custom Statements
{% endhint %}

Headings and spacers are purely visual elements that make it easier for users to consume the information in the statement.

* **Headings** allow you to include additional information in the financial statement. For example, you might want to add a descriptive heading to display underneath the financial statement name or split the statement into sections with clear headers.
* **Spacers** allow you to add some formatting to the financial statement by inserting white space between the items.

On the **Edit statement** tab of the **Manage statements** screen, click the **Add** button where you want to insert the new item, then select **Heading** or **Spacer**.

Alternatively, click an item's menu button (three dots), then select **Insert row above** or **Insert row below**, and select **Heading** or **Spacer**.

If you added a heading, enter the text you want to display.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.phocassoftware.com/financial-statements/managing-statements/customize-a-financial-statement/customize-headings-and-spacers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.