When a partner drives a conversion—like a sale—and the locking period for that action hasn’t yet passed, you can amend any incorrect action data by submitting a modification or reversal. This ensures the partner is paid out correctly when the locking period ends.
Actions are typically modified or reversed when customers return orders, make mistakes during checkout, or when items are out of stock.
You can submit modifications and reversals in bulk either via API, or through an FTP/SMTP server as outlined below. The template you need for FTP/SMTP submissions depends on whether you're tracking at the order or item level, as each requires different fields. If you're unsure which file to use, ask your CSM or contact support.
Use supported file formats — Your submission file must be in .CSV or .XML format.
Don’t add new data points — You can’t add new fields to a transaction, only update existing ones.
Understand deduplication handling — When multiple actions share the same Oid/OrderId, impact.com applies updates to the newest ActionId. To override this, specify the desired ActionId.
Use Amount correctly for reversals — To reverse an action, you can set Amount = 0. However, if the original Amount = 0, keeping it as 0 will register as a modification, and the action won’t be reversed.
For a complete list of fields you can use in FTP/SMTP batch processing, see Batch Modifications & Reversals Reference.
Identify the template file relevant to your use case.
See Batch Modifications & Reversals Reference for example template files.
Paste the template content in a spreadsheet application (e.g., Microsoft Excel) or text editor (e.g., Notepad).
Below the header row, start adding the amended action data.
If you are using a text editor, use commas to separate each data point.
If you are using a spreadsheet editor, add each data point in a separate cell.
Save the file with an identifiable name, such as:
Batch_Mods_Reversals_2025_02_12.csv
impact.com allows a maximum of 1,000 modifications per action. If you need to make further modifications thereafter, contact support.
From the top navigation bar, select
[User profile] → Settings.
On the right, under Tracking, select Event Types.
Select the name of the Event Type for which you want to submit batch modifications.
Next to Returns Processing, select
[Edit].
Select Automate returns processing (advanced).
Choose one of the following FTP or SMTP-related methods to submit your file:
Select Upload file to system FTP server.
Select Save.
Once you have received your FTP credentials via email, use an FTP client to connect to impact.com with the following info:

Once connected, upload your file to the main directory of the server.
If you have not received the FTP credentials email, contact the person who created your impact.com account. Alternatively, contact support.
Select Pull file from your own FTP server.
Enter the Server URL, Port, and Directory path to the batch modifications file on your FTP server. Enter the Username and Password that impact.com will use to connect to your FTP server.
Select Save and continue.
Upload your batch modifications file to the directory you specified above.
impact.com attempts to connect and download files from your FTP server every 24 hours, so your file may take up to 24 hours to be processed after upload.
Select Email file to system SMTP server, then copy your unique email address.
Using any email client, send an email to the unique address with your batch modifications file as an attachment.
Only include the unique email address for the event type in the To: field. If you need to send this file to others, include them in the CC: field.
You can leave the subject field and message body blank.
Once you've sent your .CSV or .XML file to impact.com, you can check back on its status to see if it was processed.
From the top navigation bar, select
[User profile] → Settings.
In the left column, scroll to the Technical section and select File Submissions.
Use the table to review recent file submissions that impact.com has received, including the current processing status.
Submitted files will appear within 10-15 minutes of being submitted, while general reporting updates can take 2+ hours.
Below are various issues you may encounter when reviewing file submissions and actions you can take to rectify them.
Issue
Action to take
Records column shows 0
Make sure the file extension is . CSV or .XML.
NO_CHANGEThere is no change made to the action. Please ensure you enter the final amount into the Amount column (e.g., enter 0 if you want to reverse actions).
BAD_DISPOSITIONThe reason code you provided is not valid. Please use one of the standard reason codes.
Alternatively, you can set up a custom disposition code.
ALREADY_LOCKEDThe action locking period has already passed. The action can no longer undergo modifications or reversals.
ActionTrackerld:ActionTrackerld value is invalidThis should correspond to the Event Type ID entered.
ACTION_NOT_FOUNDThe
OIDyou provided is incorrect. Please provide a correctOID.ALREADY_REVERSEDThe action has already been reversed.
ALREADY_APPROVEDThe action has already been approved.