> 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/bill-passing-post-to-gl.md).
# Bill Passing Post To GL
**Bill Passing Post to GL** is a transaction used to post approved and passed purchase bills to the **General Ledger (GL)**. This process creates the necessary accounting entries to record expenses, liabilities, taxes, and other financial impacts in the organisation's accounting records. Posting to the General Ledger ensures that all approved purchase transactions are accurately reflected in the financial statements.
## Steps to Perform Bill Passing Post to GL
Step 1: Open the Bill Passing Post to GL Screen
1. Navigate to the **Transactions** menu in the **Bill Passing** module.
2. Click on **Bill Passing Post to GL**.
* The **Bill Passing Post to GL** screen will be displayed.
Step 2: Click the **Post** button.
* The system will process the selected bill passing transactions and generate the corresponding General Ledger entries.
* After the posting process is completed, the system will display a confirmation message indicating that the transaction has been successfully posted.
---
# 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/bill-passing-post-to-gl.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.
