> 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/integrate-with-xyb-ledger/ledger-setup-and-configuration.md).

# Ledger Onboarding Process

Once your infrastructure is provisioned, you’ll receive access to your dedicated Ledger environment. From there, follow these steps to configure your system and begin posting transactions.

#### 1. Access Your Ledger Environment

Connect to your environment using the provided credentials and CLI tool. You’ll verify the endpoint, check health status, and ensure connectivity.\
\
[**Learn more about Accessing the Environment**](/xyb-platform-1/xyb-ledger/integrate-with-xyb-ledger/ledger-setup-and-configuration/access-your-ledger-environment.md)

#### 2. Set Up Authentication

Ledger uses JWT-based authentication. You’ll need to generate a key pair, register your service (agent), and sign each request with your private key.<br>

[**Learn more about Authentication**](broken://pages/8SQbjsYyYEWahm9hhn4a)

#### 4. Create and Assign Roles

Define roles that control what actions users or services can perform. Assign these roles to agents to enforce secure and limited access.<br>

[**Learn more about roles.**](/xyb-platform-1/xyb-ledger/integrate-with-xyb-ledger/ledger-setup-and-configuration/editor.md)

#### 5. Set Up Messaging Channels

Choose between Kafka or HTTP channels to send and receive ledger events. Configure request/response topics or endpoints based on your system's integration.<br>

#### 6. Set Up Charts, Accounts, and Wallets

Create the foundational structure for your financial system. Charts define categories, accounts track balances, and wallets handle currencies and transactions.<br>

[**Learn more about setting up chart structure.**](/xyb-platform-1/xyb-ledger/integrate-with-xyb-ledger/understanding-the-ledger-structure-charts-accounts-wallets/set-up-your-chart-structure.md)

#### 7. Configure Rules and Rulebooks

Apply business logic to transactions using rules. These might enforce conditions like currency matching, balance limits, or transaction types.<br>

[**Learn more about implementing rules.**](/xyb-platform-1/xyb-ledger/integrate-with-xyb-ledger/understanding-the-ledger-structure-charts-accounts-wallets/create-and-manage-rules.md)

#### 8. Post Transactions and Create Workflows

Initiate instructions, manage movements, and post final balances. This is where the ledger records and processes actual financial events.<br>

[**Learn more about setting up transaction workflows.**](/xyb-platform-1/xyb-ledger/integrate-with-xyb-ledger/set-up-transaction-workflows.md)


---

# 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/integrate-with-xyb-ledger/ledger-setup-and-configuration.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.