> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/reports/sales/ar-aging-report.md).

# AR Aging Report

An Accounts Receivable Aging Report is a detailed summary of unpaid customer invoices and unused Credit Memos. It categorizes the receivables based on the length of time an invoice has been outstanding and credits have not been utilized, helping businesses identify invoices that are overdue for payment. The categories are broken down into these intervals.

* 1-30 days
* &#x20;31-60 days
* 61-90 days, and
* More than 90 days.&#x20;

This report is crucial for managing cash flow, assessing financial health, and determining the effectiveness of a company's credit and collection functions.

The report typically encompasses vital details such as customer names, invoice numbers, and credit memos. This report also reflects the total amount receivable after deducting the credit amount.

There are two types of AR Aging Reports available in Xoro:

* AR Aging Summary
* AR Aging Detail

In addition to the standard **AR Aging Summary** Report, Xoro also provides the **AR Aging Summary (With Deposits)** Report. These reports include unused customer deposits along with outstanding invoices, allowing users to evaluate the total outstanding receivables after considering deposits already available on the customer's account. This helps businesses understand both the amount still to be collected and the deposits that can be applied against existing receivables.


---

# 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.xorosoft.com/xoroerp-1/reports/sales/ar-aging-report.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.
