> 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/invoices-and-revenue.md).

# Invoices & Revenue

Invoice headers and line-item detail from QuickBooks, with product and customer breakdowns for revenue analysis.

### Use it to:

* See which products and customers drive your top line
* Check AR aging and find overdue invoices
* Drill into line-item detail to understand product mix
* Track invoice status (paid, open, overdue) and days outstanding

### Invoice metrics

| Metric        | What it tells you                   | Notes                               |
| ------------- | ----------------------------------- | ----------------------------------- |
| Total amount  | Invoice total in your base currency |                                     |
| Balance       | Amount still outstanding            | Zero means fully paid               |
| Due date      | When payment is expected            | Compare to today for aging          |
| Days past due | How overdue the invoice is          | Only meaningful for unpaid invoices |
| Customer      | Who the invoice was sent to         |                                     |
| Status        | Open, paid, or voided               |                                     |

### Invoice line detail

| Metric            | What it tells you                         | Notes                                                                              |
| ----------------- | ----------------------------------------- | ---------------------------------------------------------------------------------- |
| Product / service | The item on each line                     |                                                                                    |
| Quantity          | Units sold on this line                   | Units vary by item (cases vs. eaches). Do not sum across items without normalizing |
| Unit price        | Price per unit on this line               |                                                                                    |
| Line amount       | Total for this line                       |                                                                                    |
| Revenue line flag | Whether this line is a sales revenue line | TRUE only for 41xxx sales account families                                         |
| Account family    | The account number prefix grouping        | Useful for filtering by revenue type or expense category                           |

{% hint style="info" %}
**Revenue line scope.** The revenue flag covers core sales (41xxx account families). If you need a broader revenue definition that includes allowances or adjustments, filter by account family directly rather than relying on the flag.
{% endhint %}

{% hint style="warning" %}
**QuickBooks only.** Invoice data comes from QuickBooks Online. If your company uses NetSuite, this page will not have data. Your financial statements and general ledger are still available.
{% 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/invoices-and-revenue.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.