> For the complete documentation index, see [llms.txt](https://docs.eiva.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eiva.money/the-ledger.md). # The ledger The ledger is the public record of what the vaults have done, one row per transfer. Each row shows the direction, the transfer type, the invoice it relates to where there is one (by reference, sector and payer type, never by payer name), the vault, the amount in USDC, the sterling amount where a conversion happened, the date and time, and the on-chain transaction. The transfer types are deposit, invoice funded, invoice settled, reserve, interest paid, instant withdrawal, standard withdrawal, redemption, sleeve refill, and transfers to and from the idle venue. Invoices that have been funded and not yet settled are listed separately with how long each has been out, so you can see what's outstanding at any moment. You can filter by vault, transfer type, sector and date, search by reference or transaction, and export every matching row as CSV. The ledger is at \[ledger URL: Alpha]. --- # 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.eiva.money/the-ledger.md?ask=&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.