> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/readme/set-action-locking-and-payment-scheduling-periods.md).

# Set Action Locking & Payment Scheduling Periods

A template term's *action locking period* is the time between when an action is tracked by impact.com and when it locks (or can no longer be updated). During this period, you should perform any necessary action modifications or reversals, since the action can't be updated once this period has passed.

A template term's *payment scheduling period* is the amount of time between when an action locks and when the partner is paid out for driving the action. During this period, you should ensure that your account has enough funds to cover both the amount recorded on the Statement of Invoices (SOI) and any impact.com invoices.

### Configure your locking period

You can define when an order becomes final and can no longer be reversed by using a fixed *days* locking period or a dynamic `month + day` locking period.

{% tabs %}
{% tab title="Days-only locking" %}
If you configure your locking period using days only, the maximum value is 90 days.
{% endtab %}

{% tab title="Dynamic month-based locking" %}
Use a `Month + Day` configuration when you need a locking period that adjusts dynamically based on the calendar month. Unlike a fixed day count, month-based locking calculates the exact duration relative to the month in which the order occurs.

If you set up a 1-month + 15-day locking period, the platform calculates the total duration by looking at the specific month:

| If the month is...                | The lock duration will be... |
| --------------------------------- | ---------------------------- |
| Feb (Standard)                    | 43 Days (28 + 15)            |
| Feb (Leap Year)                   | 44 Days (29 + 15)            |
| Apr, Jun, Sep, Nov                | 45 Days (30 + 15)            |
| Jan, Mar, May, Jul, Aug, Oct, Dec | 46 Days (31 + 15)            |
| {% endtab %}                      |                              |
| {% endtabs %}                     |                              |

1. From the top navigation bar, select ![](/files/xS6bxmV4GXmCOUBUoAMq) **\[User profile] →** [**Settings**](https://app.impact.com/secure/advertiser/account-settings-flow.ihtml?execution=e6s1).
2. In the left column, under *General*, select **Template Term Rules**.
3. In the *Rule Enforcement* section, select the ![](/files/pJsLBrBDVoHbzf2iiL1a) **\[Unchecked box]** below **Application of the rules**.
4. In the *Template Term* section, ![](/files/OoA2qxPalfCYKZvmxuU6) **\[Toggle on]** **Action Locking** and configure the setting as needed.
   * For example, you can configure this setting as follows: `Actions are locked 0 months and 47 days after the end of the month`.
5. Next, ![](/files/OoA2qxPalfCYKZvmxuU6) **\[Toggle on]** **Payment Scheduling** and configure the setting as needed.
   * For example, you can configure this setting as follows: `Actions are paid 0 months and 20 days after the end of the month they lock`.
6. Select **Save**.

{% hint style="info" %}
**Example**: If you configured your action locking and payment scheduling periods as shown above, and your partners drove actions during the month of January, all actions will lock on March 19. Come March 20, you'll receive an SOI from impact.com tallying up all partner invoices. At this point, you should begin the process to fund your account sufficiently to cover these invoices *and* your impact.com invoice. Finally, your account will be debited on April 20 so that your partners can be paid.
{% endhint %}


---

# 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://help.impact.com/brand/what-would-you-like-to-learn-about/readme/set-action-locking-and-payment-scheduling-periods.md?ask=<question>&goal=<endgoal>
```

`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.