> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/general-ledger/general-ledger-module/gl-masters/transaction-validation.md).
# Transaction Validation
**Transaction Validation** is the process of verifying that a financial transaction complies with predefined business rules, controls, and data requirements before it is saved, posted, or processed in the accounting system.
This feature helps ensure that all transactions are accurate, complete, authorised, and compliant with organisational policies and regulatory standards. Transaction Validation also allows administrators to control which accounts can or cannot be used for specific transaction types and debit/credit entries.
## Steps to Configure Transaction Validation
Step 1: Navigate to the **General Ledger** module.
1. Click **Masters 1** from the menu.
2. Select **Transaction Validation** from the list.
* The Transaction Validation screen will be displayed.
Step 2: Click the **Open** button.
1. Select the required **Transaction Type** based on user requirements.
Step 3: Choose whether the validation applies to **Debit** or **Credit.**
* Once selected, the corresponding configuration screen will be displayed.
Step 4: Click the **Add** button.
1. Click the **Search** icon to view the list of available accounts.
2. Select the required account name(s).
Step 5: Click the **Add** button  under the **Not Allow** section.
1. Select the account(s) that should be restricted.
Step 6: Verify that the restrictions and permissions are configured correctly.
1. Click the **Save** button.
* The Transaction Validation rules will be saved and applied to the selected transaction type.
---
# 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://help.rbsgo.com/general-ledger/general-ledger-module/gl-masters/transaction-validation.md?ask=&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.
