> 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/bill-passing/transactions/gl-posting-rejected-transactions-reversal.md).

# GL Posting Rejected Transactions – Reversal

**GL Posting Rejected Transactions – Reversal** is a transaction used to reverse General Ledger (GL) entries that were previously posted for transactions that have subsequently been rejected due to errors, discrepancies, incorrect data, or failed validations. This process ensures that the organisation's financial records remain accurate, balanced, and compliant with accounting standards.

## Steps to Perform GL Posting Rejected Transactions – Reversal

Step 1: Navigate to the **Transactions** menu in the **Bill Passing** module.

1. Click on **GL Posting Rejected Transactions – Reversal**.

* The **GL Posting Rejected Transactions – Reversal** screen will be displayed.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-693eb2e6440002931435910207bb250ef7ad06bf%2FScreenshot%20from%202026-06-04%2010-21-32.png?alt=media" alt=""><figcaption></figcaption></figure>

Step 2: Choose the required **Type** from the available options.

* The selected type will determine the category of rejected transactions to be displayed.

Step 3: Click the **Display** button.

* The system will retrieve and display the list of rejected transactions that are eligible for reversal.

Step 4: From the displayed list, select the rejected transaction that requires reversal.

Step 5: Click the **Save** button.

* The system will process the reversal and generate the necessary reversing entries in the General Ledger.


---

# 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/bill-passing/transactions/gl-posting-rejected-transactions-reversal.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.
