> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/billing/discount-attribution.md).

# How Does Discount Attribution Work?

Discount attribution plays out in various scenarios.

## Multi-Account Setup

The first scenario occurs in a multi-account setup. During a purchase plan, Archera allows you to choose whether to acquire commitments in the master payer account or distribute them across the individual covered accounts. Opt for the option that aligns best with your specific use case.

## Individual Savings Vehicle Attribution

The second scenario involves attributing individual savings vehicles to specific pieces of infrastructure. In this case, Archera can utilize the existing attribution from AWS, Azure, or GCP — or we can customize the attribution to fit your needs.

This is particularly useful when you want to apply specific savings vehicles to particular infrastructure components. For example, you might want to apply a Compute Savings Plan to all Windows-based infrastructure and utilize Guaranteed Commitments for the Linux portion.

Feel free to reach out to us to explore the possibilities of custom attribution at <support@archera.ai>.

## Related Resources

* [How does Archera Attribute Commitment Costs & Savings?](/help-center/user-guide/commitment-attribution.md)
* [Billing and GRIs](/help-center/billing/billing-and-gris.md)
* [Why is my dashboard a day or two behind?](/help-center/user-guide/dashboard-day-behind.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.archera.ai/help-center/billing/discount-attribution.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.