> For the complete documentation index, see [llms.txt](https://track360.gitbook.io/track360/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://track360.gitbook.io/track360/section-9-finance-and-payouts/editor/9.4-payment-execution.md). # 9.4 Payment Execution * The **Payments Execution** section is used only by administrators with the capability to carry out approved payments * Navigate by the **left Sidebar Menu** and click on the **Finance > Payment Execution** * Encompass **monthly or weekly payments, ad-hoc payments**, and **CSV payments** that have been imported through CSV files * **Export Payment Details** right top button, which enables you to export payment information for offline review or documentation. All sections have this option
### **Monthly/Weekly Payments** * **Monthly/Weekly Payments** allows to process through the platform affiliate/IB payouts either individually (one by one) or in bulk by uploading a CSV file * Used the **Filter** section to handle payments by: * **Period**: Decide whether payments are scheduled on a monthly or weekly basis. * **Date**: Indicate which week or month you wish to filter payments for. * **Business Unit**: Sort payments according to the relevant business unit. * **Search Employee**: Find payments linked to a certain employee. * **Search Affiliate**: Look for payments associated with a certain affiliate * **Refresh Rows** icon lets you reset the filters. * **Download all payments still pending** icon lets you download all of the payments that are still pending execution. * **Warring advertising** (red triangle) icon provides statistics on incomplete payment cycles. And by pressing again you can hide it.
* The list of monthly/weekly scheduled payments **(approved by Commission Approvals section**) specifies: * **Payment Type**: States the type of payment (e.g., Regular Payment). * **Affiliate ID and Name**: Who is set to receive the payment. * **Created On**: This indicates the date and time when the payment was initiated. * **Status**: Reflects the current status of the payment (e.g., Executed) * **Amount:** Specifies the total sum in a certain currency * **Period**: This outlines the payment schedule (e.g., Monthly) * **Invoice**: Includes details related to the associated invoice * **Reference**: This displays a blank space for you to enter the references * **Comments**: There is an empty space here for you to add notes
* Find listed all payments **already approved** on the **Commission Approvals** section. Use the left checkbox to select the desired payment: * If the selected payment is a **Payment pending for execution** will be in **white** * If the **Execute Payment** button (at the bottom) is generated on the selected payment, the row will be changed to **green** * If the **Cancel Payments** button (at the bottom) is generated on the selected payment, the row will be changed to **red** * Click on a desired affiliate, and the **Affiliate Interface** will popup with several details pertinent to the chosen affiliate balance. * **Actions** tab detailed the historical actions and notes related with the specified payment
* Find the description of the other tabs of the affiliate balance, [here in section 9.2 Affiliate Interface Management](/track360/section-9-finance-and-payouts/editor/9.2-managing-payments.md#affiliate-interface-management) ### A**dHoc Payments (Payouts on a no regular basis)**
* AdHoc Payments refers to payments out of cycle transactions: * **Credit Adjustment**: Adds funds to an affiliate’s balance. * **Manual Payment**: Immediate payment, bypassing normal execution * The section list the AdHoc Payments with details as: * **Payment Type**: Type of payment for AdHoc payment * **Affiliate ID** and **Name**: Who is receiving the payment * **Created On**: Indicated date the payment is created on * **Status**: Denotes the present state of the payment (e.g., PendingExecution) * **Amount**: The whole sum that needs to be paid * **Period**: Shows whether the payment is associated with a certain time frame * **Invoice**: All relevant invoice data * **Reference**: Payment tracking transaction references * **Comments**: Extra information or background information * Find listed all payments **already approved** with the status Pending of Execution ### **Import from CSV** * Administrators can use a **CSV file to import payment records** in this section * Select a **Time Frame** for the payments to be imported (e.g., Monthly) * **Choose File** to select the corresponding CSV file with the payment information * Once uploaded, click on **Process File** to process them for execution
* In order for a **CSV file to be valid**, it needs to contain these fields: * Affiliate ID * Amount * Accounting Date (YYYY-MM-DD) * Execution Date (YYYY-MM-DD) * Reference * Comment ### **Payment Method** * Follow the step-by-step instructions in[ section 5 of Payments Methods](/track360/section-5-settings/editor-1/5.2-configuration-settings.md#payment-methods) to overview the available options.Is possible to integrate with Payment solutions to automate it --- # 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: ``` GET https://track360.gitbook.io/track360/section-9-finance-and-payouts/editor/9.4-payment-execution.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.