> 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-posted-transactions-reversal.md).

# GL Posting Posted Transactions – Reversal

**GL Posting Posted Transactions – Reversal** is a transaction used to reverse General Ledger (GL) entries for transactions that have already been posted and finalised in the accounting system. This process is typically performed when corrections, adjustments, or modifications are required after posting.

## Steps to Perform GL Posting Posted Transactions – Reversal

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

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

* The **GL Posting Posted 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-fef02eb312a273e7f40461fce8eb86ad58b11805%2FScreenshot%20from%202026-06-04%2010-35-23.png?alt=media" alt=""><figcaption></figcaption></figure>

Step 2: The system will display a list of transactions that have already been posted to the General Ledger.

Step 3: From the list of posted transactions, select the transaction that needs to be reversed.

Step 4: Click the **Reverse** button.

* The system will process the reversal and create 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-posted-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.