> For the complete documentation index, see [llms.txt](https://videos.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://videos.inforiver.com/reporting-matrix/expert-speak/formatting-financial-statements-in-power-bi-p-and-l.md).

# Formatting financial statements in Power BI - P\&L

With Inforiver’s user-friendly interface, you can - ​ 

a) Format and indent GL account headers​ 

b) Group column headers​ 

c) Insert calculated rows to show derivative KPIs such as Gross Margin % or Earnings Per Share (EPS) and more​ 

Other important feature highlights that you can leverage are number formatting, indenting & aligning accounts, customizing subtotals and totals​​, formatting of rows, columns, cells & values​ etc.

{% embed url="<https://lumel.wistia.com/medias/lgzyzl8ih3>" %}

> ## **Related resources**
>
> #### Feature highlights
>
> [Financial reports in Power BI](https://inforiver.com/financial-reports-powerbi/)
>
> #### Blogs
>
> [Build a P\&L / income statement report in Power BI in less than 5 minutes](https://inforiver.com/blog/financial-statements/financial-income-statement-reporting-table-matrix-power-bi/)
>
> [Achieve 20x productivity in P\&L/financial statement reporting in Power BI](https://inforiver.com/blog/financial-statements/financial-statement-power-bi/)
>
> [Best fonts for financial reporting](https://inforiver.com/blog/general/best-fonts-financial-reporting/)
>
> #### Demos <a href="#headline-27-3553" id="headline-27-3553"></a>
>
> [AMD financial statements](https://inforiver.com/demos/financial-statements-using-microsoft-power-bi-amd/)
>
> [Nike financial statements](https://inforiver.com/demos/financial-statements-using-microsoft-power-bi-nike/)
>
> [Apple financial statements](https://inforiver.com/demos/financial-statements-using-microsoft-power-bi-apple/)


---

# 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://videos.inforiver.com/reporting-matrix/expert-speak/formatting-financial-statements-in-power-bi-p-and-l.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.