> For the complete documentation index, see [llms.txt](https://docs.udara360.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.udara360.io/core-features/postings/single-batch-gl/single-gl-only.md).

# Single GL (Only)

The Single GL Page allows users to view and manage individual GL (General Ledger) posting entries within the core banking application. This page provides a comprehensive breakdown of each GL transaction.

### Accessing the Single GL Page

1. Log into the core banking application using your authorized credentials.
2. From the dashboard, navigate to the "**Postings**" section.
3. Click on **Single/Batch.**
4. Click the "**GL Posting**" option to access the **Single GL Page**.

## Create a New Single GL Entry

1. Click on the "**Post**" button at the top page.
2. Select the appropriate accounts in the "**GL to Debit**" and "**GL to Credit**" sections.
3. Verify the "GL **to Debit Account Number**" and "GL to Credit Account Number" are correct.
4. Select and fill in the **Branch, SortCode, and Amount Instrument No** for GL Credit/Debit.
5. Enter the "Amount" and "Narration" (description) for the posting.
6. Click the "**Post**" button to submit your decision.

<figure><img src="/files/uzIjtVbkoKD9dYfcwu0c" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.udara360.io/core-features/postings/single-batch-gl/single-gl-only.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.