> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/rebates/rules/monthly-rebates.md).

# Monthly rebates

Of the many variations of calculating rebates, a primary differentiator is the period of calculation and payout. This page explains how to calculate and pay or receive rebates in monthly periods.

With the **Amounts per** > **Month** option, the rule validation period (from start to end date) can be of any length greater than one month. However, the calculation period can’t be more than 12 months, regardless of when your year starts.

With monthly rebates:

* The cumulative total resets to zero every month.
* The cumulative total is calculated for the transactions from the *start of the calendar month* up to the *start of the calculation period*. Then, the transactions in the calculation period are added to that cumulative total and put into brackets accordingly. This ensures the calculation starts in the correct bracket.

## Setup <a href="#setup" id="setup"></a>

In the [rule setup](/rebates/rules.md) **Brackets** section, select **Amounts per** > **Month**.

## Example <a href="#example" id="example"></a>

Suppose the rule starts in January and it uses the **Percentage of Value** calculation method, the **Value** bracket basis, and has three brackets. The calculation results depend on the calculation period.

### **(A) Full months**

If the calculation period is from June 1 to July 31 (two full months), the results are split into two month periods. As the calculation started at the start of the calendar month, there's no cumulative total to factor in, so the rebate for each month is calculated as usual, based on the brackets that are hit in that period.

<div align="left"><figure><img src="https://content.gitbook.com/content/MbR0klD6u5c0D9XeXtY3/blobs/kKO9lmmhesz0CnQ2yeec/image.png" alt=""><figcaption></figcaption></figure></div>

### **(B) Partial months**

If the calculation period is from June 21 to July 31 (partial period), there is a cumulative total to factor in. Therefore, the partial period from June 21 until the end of June is already in the 5% bracket.<br>

<figure><img src="https://content.gitbook.com/content/MbR0klD6u5c0D9XeXtY3/blobs/oCTWZMJpbgnOBjswhxOH/image.png" alt=""><figcaption></figcaption></figure>


---

# 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.phocassoftware.com/rebates/rules/monthly-rebates.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.