> 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-ledger/integrate-with-xyb-ledger/set-up-transaction-workflows/create-and-manage-postings.md).

# View & Manage Postings

Postings are detailed records that capture the impact of movements on wallet balances, providing transparency and accountability for every transaction. They are the final step in a financial operation, ensuring that all changes to wallet balances - both reserved and final - are accurately documented. Postings can also be configured (or created) to align with specific transaction requirements and ledger rules.

***

### Posting Logic

* **Adjust Reserved Balances:**\
  When a movement is initiated, postings first modify the reserved balances of the involved wallets. This ensures that funds are allocated for the transaction, preventing double spending or overdrafts.
* **Commit Final Balances:**\
  Once the movement is finalized, postings update the final balances of the wallets. This step permanently reflects the completed transaction in the ledger.

#### **Steps to Retrieve Postings**

Retrieving postings allows you to monitor and audit transactions effectively. Follow these steps:

1. **Retrieve All Postings for a Wallet:**\
   Use the following command to fetch postings for a specific wallet:

   ```bash
   luca read-postings /chart/company/revenue/default/USD
   ```
2. **Filter Postings by Attributes or Time Range:**\
   Use filtering options to focus on postings related to a specific period, amount, or metadata attributes.

***

#### **Finalizing Postings**

Once a movement is finalized, its postings are committed to the ledger. This process ensures that all balances are updated and immutable.

**Example:**

* **Credit:** `/chart/company/revenue/default/USD`
* **Debit:** `/group/customers/customer123/default/USD`

In this example:

* Funds are credited to the company’s revenue account.
* The corresponding debit reflects a reduction in the customer’s wallet balance.

***

#### **Best Practices for Postings Configuration**

* **Define Clear Chart and Wallet Structures:**\
  Ensure that your chart of accounts and wallet configurations align with your business use cases.
* **Automate Posting Creation:**\
  Use predefined rules or automated scripts to generate postings for recurring transactions, reducing manual effort.
* **Audit Regularly:**\
  Retrieve and review postings to ensure compliance with financial policies and to identify any discrepancies.

***

By understanding how to configure, retrieve, and finalize postings, you can ensure accurate tracking of all financial transactions. 


---

# 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-ledger/integrate-with-xyb-ledger/set-up-transaction-workflows/create-and-manage-postings.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.