> 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/user-guide/commitment-attribution.md).

# How Does Commitment Discount Attribution Work

## Attribution Concept

This touches on a concept called "Attribution" in Archera, which handles which RIs & SPs are applied to which resources within your account, along with associated costs & savings.

## AWS Default Attribution Strategy

AWS has a default attribution strategy where all commitments are applied against all resources based on what gets the highest discount, and for resources that get the same discount, attribution is handled in an arbitrary manner.

This behavior applies both to:

* Commitments purchased natively through AWS Cost Explorer
* Commitments purchased through Archera (even if they were purchased for a particular segment)

## Archera's Default Attribution

Archera, by default, employs the AWS default attribution strategy. We do this because the default attribution strategy aligns with what will be shown on your AWS bill and usage report.

Using a different attribution strategy could lead to discrepancies between AWS and Archera in terms of the precise cost of each resource.

## Custom Attribution for Enterprise Customers

For customers seeking an alternative chargeback model distinct from the AWS default — featuring a custom attribution strategy — we offer the capability to support custom attributions for any Reserved Instance (RI) or Savings Plan (SP) through our Custom Reporting Functionality.

This feature is employed by our enterprise customers for:

* In-depth analysis of COGS
* Margin analysis
* Business Unit (BU) showback/chargeback
* Other customized functionalities

## Related Resources

* [Billing and GRIs](/help-center/billing/billing-and-gris.md)
* [How Does Commitment Discount Attribution Work in Archera?](/help-center/billing/discount-attribution.md)
* [Product Overview](/help-center/getting-started/product-overview.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/user-guide/commitment-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.