> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/bevica-select/faqs/reconcile-aged-receivables-and-payables-to-the-general-ledger.md).

# Reconcile aged receivables and payables to the general ledger

Run aged AR/AP reports and reconcile totals back to the customer and vendor control accounts.

Aged reports are only useful if they reconcile to the G/L. This check catches posting and setup issues early.

### What you are reconciling

* **Aged Accounts Receivable** total ↔ **Customer control account** balance.
* **Aged Accounts Payable** total ↔ **Vendor control account** balance.

### Reconcile aged receivables

1. Run **Aged Accounts Receivable** as at your reconciliation date.
2. Note the report total.
3. Open **Chart of Accounts**.
4. Filter to your customer control account (commonly `2310`).
5. Set a **Date Filter** up to the same date (for example, `..31/01/26`).
6. Compare the **Balance at Date** to the aged report total.

### Reconcile aged payables

1. Run **Aged Accounts Payable** as at the same date.
2. Note the report total.
3. In **Chart of Accounts**, filter to your vendor control account (commonly `5410`).
4. Set the same **Date Filter**.
5. Compare the **Balance at Date** to the aged report total.

### If it doesn’t match

Common causes:

* Direct postings to the control accounts.
* Incorrect posting groups on customers/vendors.
* Date filters not aligned (posting date vs document/due date).
* Foreign currency revaluation timing.

Next checks:

* Run **Customer Trial Balance** / **Vendor Trial Balance** for the same date.
* Drill down from the control account to see which entries make up the balance.


---

# 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://kb.bevica.com/bevica-select/faqs/reconcile-aged-receivables-and-payables-to-the-general-ledger.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.