> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/components/component-library/self-service-components/component-change-summary.md). # Component: Change Summary **Available from:** Release 112 **Purpose**: Displays a cost breakdown associated with a subscription change in the Update Subscription flow. The Change Summary component shows customers a clear breakdown of charges or credits when they upgrade or amend their subscription. It ensures transparency and mirrors the acquisition checkout experience. {% hint style="warning" %} The Change Summary should not be used for acquisition flows, as it relies on Zuora preview dependencies. {% endhint %} ### Behaviour The component lists the product names returned by Zuora. When a change is made before the end of term, the component highlights whether amounts are owed or reimbursed. Owed amounts are shown as a **prorated** **credit**. When a change is made at term end, the component will not be shown. All owed amounts are displayed as positive numbers, while reimbursed amounts appear as negative. {% embed url="" %} *Change summary component, with Text component used as the heading* --- # 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.limio.com/components/component-library/self-service-components/component-change-summary.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.