> 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/action-inquiries/review-action-inquiries.md).

# Review Action Inquiries

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

Some cashback and loyalty partners can submit *Action Inquiries* when they believe they weren't credited for an action they drove. You can review their inquiry and choose to accept, decline, or request more information from your partner. See [Action Inquiries Explained](/brand/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/action-inquiries/action-inquiries-explained.md) to learn more.

## Review an action inquiry

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 →** [**Inquiries**](https://app.impact.com/secure/advertiser/engage/actions/view-missing-action-enquiries-flow.ihtml).
   * Listed here, you'll see any action inquiries you've received from partners.
2. Hover your cursor over the inquiry you want to view, then select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FMLtRUwWz0pujlfmYWOgg%2FMoreVN.svg?alt=media\&token=03a3c355-a347-4207-baf7-c44fadf6d080) **\[More]** → **Review.**
   * The review page contains details about the inquiry, like the partner who submitted it, the date and time the action took place, and the expected payout.&#x20;
3. Scroll to the *Select Resolution* section and select one of the following options to process the inquiry:

{% tabs %}
{% tab title="Accept" %}

1. If you determine an action took place, **Accept** the action inquiry.
2. Complete the following fields:

<table data-header-hidden="false" data-header-sticky><thead><tr><th>Field</th><th>Instruction</th></tr></thead><tbody><tr><td>Transaction Date</td><td>Select the date when this transaction occurred. To understand when the action will lock and be paid out, see <a href="/brand/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/understand-the-action-life-cycle-and-finance.md#how-retroactive-locking-dates-are-calculated">Understand the Action Life Cycle &#x26; Finance</a>.</td></tr><tr><td>Event Type</td><td>Select the <a href="/brand/what-would-you-like-to-learn-about/platform-features/event-types/event-types-explained.md"><strong>Event Type</strong></a> to which this action is tied.</td></tr><tr><td>Transaction Details</td><td>Optionally, if you want to add item details like <em>SKU</em>, <em>Name</em>, <em>Quantity</em>, etc., select <img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FiZjM1xY8o3v1iR3Zaysd%2FToggle.svg?alt=media&amp;token=b1550d48-bba9-4e81-8604-bc12370c5caa" alt=""> <strong>[Toggle on]</strong> <strong>Specify details for this transaction</strong>.</td></tr><tr><td>Select Payout Option</td><td><p>Choose the payout the partner will receive for this action:</p><p>• <strong>Accept Expected Payout Amount</strong>: The payout the partner proposed in the inquiry.</p><p>• <strong>Specify Payout Amount</strong>: Set a custom payout amount for the action.</p><p>• <strong>Generate Payout Amount</strong>: Pay out based on the contract between you and the partner.</p></td></tr></tbody></table>
{% endtab %}

{% tab title="Decline" %}

1. If you determine an action didn't take place, **Decline** the action inquiry.&#x20;
   * The partner will be notified that they won't be credited for the action.&#x20;
2. Use the ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-c2cb550b55c51ea1eeff0acbd6f437a03b621a2c%2F60d033ae8a04c14498d5229c3c0160ac05feea7f605dbd770741793c900469f0.svg?alt=media) **\[Drop-down menu]** to select a reason that most closely relates to why you declined.&#x20;
3. Optionally, select **Other** and enter a custom reason in the *Notes* comment box.
   {% endtab %}

{% tab title="Need more information" %}

1. If you can't determine whether or not an action took place, select **Need more information**.

2. Include a comment in the *Notes* field so the partner knows what additional information you require to process the review.
   {% endtab %}
   {% endtabs %}

3. To finalize your decision for this action inquiry, select **Submit** and return to the previous page, or select **Submit and review next** to load the next inquiry.


---

# 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/action-inquiries/review-action-inquiries.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.