> For the complete documentation index, see [llms.txt](https://docs.drivepoint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivepoint.io/data-integrations/financials-datamart/financial-statements.md).

# Financial Statements

Your income statement, balance sheet, and chart of accounts, pulled directly from your ERP and mapped to Drivepoint categories.

### Use it to:

* Review P\&L performance by account and period
* Check balance sheet positions over time
* See which Drivepoint category each GL account maps to
* Identify unmapped accounts and gauge how much dollar volume they represent

### Income statement

| Metric              | What it tells you                               | Notes                                                                |
| ------------------- | ----------------------------------------------- | -------------------------------------------------------------------- |
| Net change          | Revenue or expense amount for the period        | Positive = inflow for revenue accounts, outflow for expense accounts |
| Drivepoint category | The mapped SmartModel category for each account | Unmapped accounts show as blank                                      |
| Account name        | The original GL account name from your ERP      |                                                                      |
| Period              | Month the amounts apply to                      | First and last day of each period                                    |

### Balance sheet

| Metric         | What it tells you                                     | Notes                              |
| -------------- | ----------------------------------------------------- | ---------------------------------- |
| Ending balance | Account balance at period end                         | Cumulative, not a period change    |
| Net change     | Movement in the account during the period             | Useful for spotting unusual swings |
| Statement type | Whether the account is an asset, liability, or equity |                                    |

### Chart of accounts

| Metric              | What it tells you                               | Notes                                                                 |
| ------------------- | ----------------------------------------------- | --------------------------------------------------------------------- |
| Account ID and name | Every GL account in your ERP                    |                                                                       |
| Drivepoint category | What each account maps to in your SmartModel    | Blank if unmapped                                                     |
| Sign convention     | Whether Drivepoint flips the sign for reporting | Some accounts (revenue, liabilities) follow opposite-sign conventions |

### Mapping coverage

| Metric                       | What it tells you                                                       | Notes                                                                                              |
| ---------------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| Mapped vs. unmapped accounts | How many GL accounts have a Drivepoint category assigned                | By count and by dollar value                                                                       |
| Dollar-weighted coverage     | What percentage of your total GL activity flows through mapped accounts | A few high-volume unmapped accounts can mean low effective coverage even with most accounts mapped |

{% hint style="info" %}
**Mapping coverage is weighted by dollar value, not just account count.** An unmapped account that carries $1M in activity matters more than ten unmapped accounts with $100 each. Use coverage to prioritize which accounts to map next.
{% 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.drivepoint.io/data-integrations/financials-datamart/financial-statements.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.