> 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/accounting/bank-reconciliation/bank-rules/what-is-bank-reconcile-rule.md).

# What is Bank Reconcile Rule?

A Bank Reconciliation Rule simplifies the reconciliation process by automatically matching bank transactions based on specified criteria and generating corresponding journal entries. This reduces the manual effort involved in reconciling bank statements, ensuring accuracy and efficiency in financial management.

### Benefits of Bank Reconciliation Rule

1. **Automation:** Bank reconciliation rules automate the matching process, saving time and reducing manual errors.
2. **Accuracy:** By setting specific criteria for matching transactions, users can ensure a higher level of accuracy in the reconciliation process.
3. **Efficiency:** The ability to create and edit rules allows businesses to tailor the reconciliation process to their specific needs and requirements.
4. **Consistency:** The reconciliation rule ensures consistent application of reconciliation criteria across transactions.
5. **Transparency:** The use of bank reconciliation rules provides a clear audit trail for reconciling bank transactions, improving transparency and accountability.


---

# 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/accounting/bank-reconciliation/bank-rules/what-is-bank-reconcile-rule.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.