> 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/platform-features/actions-and-payouts/understand-the-action-life-cycle-and-finance.md).

# Understand the Action Life Cycle & Finance

<a href="https://pxa.impact.com/student/activity/1087855?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=tra-250&#x26;utm_campaign=help-center" class="button primary">Take the PXA course</a>

An action is a customer outcome (such as a sale, or a lead) that's been tracked by impact.com and credited to one or more of your partners. Actions follow a “life cycle”—they begin as new, pending actions, and usually end as locked actions, at which point they trigger a scheduled payout to the partner who drove the action.

The action life cycle incurs financial implications at certain points. Your impact.com account funding needs to be up-to-date and prepared for any payout obligations arising from locked actions.

## Action life cycle overview

After a conversion occurs, here's what happens:

```mermaid
flowchart TD
    A["`**Conversion**`"] --> B["`**Pending action**
Estimated payout viewable`"]
    B --> R["`**Action reversed**
No payout due`"]
    B --> C["`**Action locks**
Payout due on scheduled clearing date`"]
    C --> I["`**Action reported on invoice or PRF**
Account is funded (or pre-funded)`"]
    C --> D["`**Scheduled clearing date**
Payout sent to partner`"]

    classDef base fill:#ffffff,stroke:#f86a73,stroke-width:1px,stroke-dasharray:2 2,color:#000000
    classDef estimated fill:#ffffff,stroke:#f86a73,stroke-width:1px,stroke-dasharray:2 2,color:#f1c232
    classDef due fill:#ffffff,stroke:#f86a73,stroke-width:1px,stroke-dasharray:2 2,color:#cc0000
    classDef funded fill:#ffffff,stroke:#f86a73,stroke-width:1px,stroke-dasharray:2 2,color:#38761d
    classDef sent fill:#ffffff,stroke:#f86a73,stroke-width:1px,stroke-dasharray:2 2,color:#14b1f7
    class A,R base
    class B estimated
    class C due
    class I funded
    class D sent
    linkStyle default stroke:#000000,stroke-width:1px,stroke-dasharray:2 2
```

* After a conversion event is tracked and credited to a partner, the action becomes *pending* on impact.com.
* Pending actions can be modified or reversed within the locking period. After the locking date passes, they become *locked actions*, which are considered *approved*.
* The commission amount due on *locked* actions is final, and is delivered on the s*cheduled clearing date*.
* Once the clearing date passes, the action will appear on the next partner invoice (usually on the 2nd of the month, unless a [custom GAAP month](/brand/what-would-you-like-to-learn-about/platform-features/finance/finance-documents/custom-gaap-month-scenarios.md) is used).

## How retroactive locking dates are calculated

When you [submit conversion data retroactively](/brand/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/submit-conversion-data/submit-conversion-data-via-ftp-or-email.md), impact.com uses the `EventDate` in your batch file to calculate what the action's locking date would have been. What happens next depends on whether that date has already passed.

```mermaid
flowchart TD
    S(["Retroactive conversion submitted"]) --> L["Locking date calculated from the EventDate in your batch file"]
    L --> Q{"Has that locking date already passed?"}
    Q -- "No" --> N("Normal schedule: locking and clearing dates are based on the EventDate in your batch file")
    Q -- "Yes" --> Y("Adjusted schedule: locking and clearing dates are based on when you submitted the data, so the action isn't scheduled to lock or clear in the past")

    classDef start fill:#ffffff,stroke:#f86a73,stroke-width:1px,stroke-dasharray:2 2,color:#000000
    classDef step fill:#ffffff,stroke:#f86a73,stroke-width:1px,stroke-dasharray:2 2,color:#000000
    classDef question fill:#fff8e1,stroke:#f1c232,stroke-width:2px,color:#000000
    classDef normal fill:#eaf3e6,stroke:#38761d,stroke-width:2px,color:#1e4410
    classDef adjusted fill:#e6f6fe,stroke:#14b1f7,stroke-width:2px,color:#0b4f70
    class S start
    class L step
    class Q question
    class N normal
    class Y adjusted
    linkStyle 0,1 stroke:#000000,stroke-width:1px,stroke-dasharray:2 2
    linkStyle 2 stroke:#38761d,stroke-width:2px
    linkStyle 3 stroke:#14b1f7,stroke-width:2px
```

In both cases, payout rates, adjustments, and payout group rules and the event date shown in reports come from the `EventDate` in your batch file, not the submission date.

## Action status & finance

Below are the different statuses an action can appear with in the [Action Listing report](/brand/what-would-you-like-to-learn-about/platform-features/multi-program-reports/performance-reports-for-brands/advanced-action-listing-report.md), along with the correlating finance implication.

| Action status     | Financial implication                                                                                                                                                                                                                                                         |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pending           | **Action Cost estimated:** When an action is pending, it can still be modified (or reversed). Pending actions have an estimated *Action Cost* column in the Action Listing report. If the action does not change before it locks, this will be the commission to the partner. |
| Approved / Locked | **Action Cost due on Scheduled Clearing Date:** When an action is locked, the Action Cost amount becomes due. This will be used to pay the credited partner for generating the action.                                                                                        |
| Reversed          | **Action Cost voided:** When an action is reversed, the action cost is voided and no commission is due.                                                                                                                                                                       |

## View an action's details

An action's detail modal shows details about a specific action.

1. From the left navigation menu, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage]** → **Transactions → Pending Payouts →** [**Actions**](https://app.impact.com/secure/advertiser/engage/actions/open/pending-actions-flow.ihtml).
2. On the *Pending Payouts* screen, select the **linked Action ID** to open the modal.
   * Below is a list of the most important data points to keep in mind when viewing action details:

| Data point              | Description                                                                                                                                                                                                |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Payout                  | The commission amount the partner will receive for the action if it locks (equal to the Action Cost).                                                                                                      |
| Locking Date            | The date and time when the action will lock and the partner commission will become due.                                                                                                                    |
| Scheduled Clearing Date | The date and time when impact.com will clear the funds from your account to pay the partner for the action. **If your account has insufficient funds, the payment will be considered&#x20;*****Overdue***. |

## Action lifecycle FAQs

<details>

<summary>If I approve an action before the locking date, can it still be modified?</summary>

Yes. Approving an action during the locking period marks it as valid, but the action still locks on its scheduled locking date. Until that date arrives, you can still modify or reverse the action (for example, if a customer returns a purchase).

</details>

<details>

<summary>Can the action review window be changed?</summary>

impact.com's locking period is a review window during which you can correct any incorrect action data or reverse actions that are invalid for payout under your contract with a partner. impact.com recommends the default locking period of *27 days after the end of the month they're tracked*, but you can change this to suit the needs of your program. For more details, see [Set Action Locking & Payment Scheduling Periods](/brand/what-would-you-like-to-learn-about/getting-started/set-action-locking-and-payment-scheduling-periods.md).

</details>

<details>

<summary>What if my account funds won't cover all locked actions?</summary>

Locked actions that can't be paid out due to insufficient funds will not be cancelled. Instead, they will be marked as *Overdue* until you cover any outstanding payouts. [Learn how overdue payouts are settled](/brand/what-would-you-like-to-learn-about/platform-features/finance/finance-explained-for-brands.md) after subsequent funding, and stay ahead of your funding obligations with a good [funding strategy](/brand/what-would-you-like-to-learn-about/platform-features/finance/add-funds-to-your-funding-account/guide-to-funding-strategies-for-brands.md).

</details>


---

# 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://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/understand-the-action-life-cycle-and-finance.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.
