> For the complete documentation index, see [llms.txt](https://docs.zirodelta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zirodelta.com/modules/settlement-engine.md).

# Settlement Engine

The Settlement Engine moves balances and settles them, end to end: payouts, transfers between parties, and money scheduled to move at a certain time.

## What it is designed to do

* **Payouts** from the Yield Engine's pool to the people who own shares in it.
* **Transfers between parties** inside an app, such as from buyers to sellers.
* **Scheduled and just-in-time transfers,** such as moving only today's spending into a spending balance. See [Money that waits in the right place](/use-cases/just-in-time-balances.md).
* **Repayment from payouts,** so an advance from the [Credit Engine](/modules/credit-engine.md) is repaid automatically before the rest of the payout is released.

## Safety

Payouts from the pool are batched and need a co-signature from a key held off-server. A compromised server alone cannot release pool funds.

## Status

In development. Vault payouts are built and switched off.


---

# 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.zirodelta.com/modules/settlement-engine.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.