> For the complete documentation index, see [llms.txt](https://support.ordereazi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.ordereazi.com/sales-features/dashboard/invoices-vs-paid-widget.md).

# Invoices vs Paid Widget

## 💳 Invoices vs Paid Widget

The **Invoices vs Paid** widget visually compares the total value of invoices issued against the amount allocated (paid) over time. It uses a simple line graph to highlight trends in billing versus payments, helping teams track cash flow and identify discrepancies between invoicing and revenue collection.

### 🔍 What It Shows

* **Invoiced Total**: The cumulative amount invoiced for each date or period.
* **Allocated Total**: The corresponding amount received and allocated against those invoices.
* **Visual Gaps**: Any large gaps between the "Invoiced" and "Allocated" lines can indicate late or missing payments.

### 🌟 Purpose

This widget gives you a quick way to:

* Monitor how well your customers are paying over time.
* Identify potential collection issues or cash flow risks.
* Analyze billing performance vs actual revenue received.

{% hint style="info" %}
If you don’t see this widget on your dashboard and believe you should, contact your system administrator to update your user permissions.
{% 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://support.ordereazi.com/sales-features/dashboard/invoices-vs-paid-widget.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.