> For the complete documentation index, see [llms.txt](https://docs.cloud-halo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloud-halo.io/finops/savings-ledger.md). # Savings ledger The savings ledger helps teams track whether optimisation work has produced measurable results. ## How savings are created Savings entries are created from resolved recommendations. After a recommendation is marked resolved, Cloud Halo can compare later spend with the earlier baseline for the related subscription, service, resource group, tag, or resource. ## Savings statuses Savings can be reviewed as: * Pending: the action was taken, but there is not enough later spend data yet * Confirmed: later spend supports the expected saving * Disputed: the saving needs review because spend did not move as expected or the baseline is no longer representative ## What to review Open the savings ledger and review: * Recommendation title * Related subscription or cost dimension * Estimated savings * Measured savings * Status * Resolution date * Notes and supporting context ## Good practice Review the ledger during monthly cost reviews. Confirm entries that match actual outcomes, dispute entries that need more context, and use notes to explain major business changes such as migrations, launches, or seasonal workloads. For MSPs, use the ledger as evidence for client service reviews and monthly executive reports. The ledger is designed to make confirmed, pending, and disputed savings easy to review without relying on spreadsheets. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cloud-halo.io/finops/savings-ledger.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.