> 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/executing-manual-transaction-recording-in-console.md).

# Executing Manual Transaction Recording in Console

The Console UI allows you to record transactions manually by creating direct postings between wallets. This is useful for operations teams handling adjustments, corrections, internal transfers, or ad hoc value movements that are not part of automated flows.

***

#### **What Manual Transactions Do**

A manual transaction records a value transfer between two wallets by creating a pair of postings:

* **Debit**: Value is removed from the source wallet
* **Credit**: Value is added to the destination wallet

The ledger updates balances immediately based on the specified value date.

***

#### **Use Cases**

* Adjusting balances due to manual corrections
* Issuing top-ups or internal allocations
* Moving funds between platform-owned accounts
* Testing wallet behavior or ledger setup
* Creating historical transactions using a custom value date

***

#### **Steps to Execute a Manual Transaction**

1. Go to **Ledger > Postings** in the Console.
2. Click **+ New transaction**.\
   ![](https://2842134550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FakJn6TxWIBAbZwLlYoVP%2Fuploads%2FnZrKurrTde98QtfY3CBI%2Fimage.png?alt=media\&token=46b9ed82-b860-42ea-b847-c22077eff0f8)
3. Fill in the transaction form:
   * **From**: Source wallet&#x20;
   * **To**: Destination wallet
   * **Amount**: Value to transfer
   * **Currency**: Auto-selected based on wallets
   * **Value date**: Effective date/time for the transaction
4. (Optional) Add **tags** and **attributes**:
   * Tags: Simple labels like `manual`, `adjustment`
   * Attributes: Key-value pairs for structured metadata (`reason:reconciliation`, `source:admin`)
5. Click **Continue**.
6. Review the transfer details.\
   ![](https://2842134550-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FakJn6TxWIBAbZwLlYoVP%2Fuploads%2F6nrZgVS6PtsFuw4mfNGv%2Fimage.png?alt=media\&token=de4f90bb-47b3-4bac-be21-6250ae4c1e23)&#x20;
7. Enter a brief explanation for why the transaction is being made in the **Reason or description** field.
8. Click **Execute**. Once submitted, the transaction is committed, and the associated postings can be viewed under **Ledger > Postings**.

***

#### **Notes**

* Wallet currency, decimal places, and accounting type are fixed - they must match for compatible transfers.
* The transaction takes effect as of the **value date**, not necessarily the creation time.
* Once submitted, manual transactions **cannot be reversed.** Create a counter-posting if you need to correct.

***

#### **Where to Review the Results**

After execution:

* Go to **Ledger > Postings**
* Filter by wallet, time, or attributes
* Click into a posting to view both sides and associated metadata


---

# 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/executing-manual-transaction-recording-in-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.
