> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/store-manager/configure-pos-and-store-manager/store-financials/gl-accounts.md).

# GL accounts

This topic describes how to configure general ledger (GL) accounts for register batches.

In RMH, you can export transaction data from closed register batches to an XML file, which can be imported into third party accounting apps. Before you can export (post) closed batches, you must assign debit and credit accounts (from the store's Chart of Accounts) to the types of transaction data collected by RMH.

{% hint style="warning" %}
**Warning!** The account numbers entered in the **Debit Account** and **Credit Account** columns must match the numbers used in the accounting app. If the numbers do not match, transaction data from RMH may not be successfully imported into the accounting app. If you add new tender types, item taxes, or departments in Store Manager, you must update the account assignment table with the appropriate debit and credit accounts.
{% endhint %}

1. Click **File** | **Configuration**.
2. Click the **GL Accounts** tab.
3. Click the **Batch GL Accounts** tab.
4. In the **Debit Account** column, enter the relevant debit account.
5. In the **Credit Account** column, enter the relevant credit account.
6. Click **Save And Close**.


---

# 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.rmhpos.com/store-manager/configure-pos-and-store-manager/store-financials/gl-accounts.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.