> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/xyb-platform-1/xyb-ledger/ledger-operation-in-xyb-console/postings-and-balances-in-xyb-console.md).

# Postings and Balances in XYB Console

The **Ledger Postings and Balances** views in Console give teams a visual and intuitive way to explore and monitor ledger activity. This interface is designed for **finance, operations, and support teams** who need to:

* Track balances across charts, accounts, and wallets
* Review historical ledger activity
* Manually record transfer funds between wallets
* Investigate or audit specific transactions

The UI is ideal when you need clarity, transparency, and real-time access to the ledger without writing scripts or working directly with APIs.

***

The Console is the go-to place to access the **outcomes** of ledger operations: committed transactions, updated balances, and transaction metadata. It’s purpose-built for:

| **Use Case**                     | **Console UI Covers**                                                |
| -------------------------------- | -------------------------------------------------------------------- |
| Balance monitoring               | See chart/account/wallet structures and current balance state        |
| Transaction lookup and history   | Search postings, filter by wallet, time, or metadata                 |
| Manual interventions             | Create one-off wallet transfer recordings directly in the UI         |
| Transparency and auditability    | View posting details, track debit/credit sides, tags, and attributes |
| Operations and support workflows | Quickly resolve issues by viewing exact wallet and transaction data  |

{% hint style="info" %}

***

> **Note:**\
> The Console UI is designed for monitoring balances, viewing postings, and performing manual transactions. Instruction creation, movement orchestration, and automation workflows are handled through the CLI and APIs, which are purpose-built for programmatic and multi-step operations. Learn more about [instructions and movements.](/xyb-platform-1/xyb-ledger/integrate-with-xyb-ledger/set-up-transaction-workflows/create-and-manage-instructions.md)
> {% endhint %}


---

# 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://docs.xyb.co/xyb-platform-1/xyb-ledger/ledger-operation-in-xyb-console/postings-and-balances-in-xyb-console.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.