Please note: the Final Outcomes Settings has been renamed to Entity Feedback.
Navigate to the Entity Feedback section by going to Settings > Entity Feedback. This page allows you to review all your Entity Feedback, download our standardized templates, upload Entity Feedback via CSV or manually, and manage Entity Feedback data.
If you prefer to upload Entity Feedback data programmatically, use our Append entity feedback API endpoint. The endpoint appends new records without replacing existing Entity Feedback data..
Permissions
Before you get started, make sure your role has the appropriate Entity Feedback permissions. Agent can create entity feedback is required to upload or manually add feedback, and Agent can view entity feedback is required to access the Entity Feedback page. Agent can delete entity feedback is only required if you need to delete feedback.
These permissions can be enabled by navigating to Settings > Roles, selecting the applicable role, and clicking Edit Role. Scroll to the Entity Feedback section and enable the required permissions.
Agent can create entity feedback
Agent can view entity feedback
Agent can delete entity feedback
After the appropriate permissions have been granted, the Entity Feedback tab will appear within the Settings page. Under this tab, there is the option to import the list as a CSV. Please follow the steps below to prepare and share your final outcomes data.
Importing via CSV or Manually
Upload Step
To import a CSV file from the computer, start by clicking the Import Feedback button. The supported file types are .csv, .tsv, .txt, .xls, .xlsx, and .xml.
If you’re unsure of which format to create your CSV, click the text You can also download a template to get started from the modal to download a template that you can use.
You can also input the data manually through the modal. Inputting at least one piece of data will automatically take you to the Review step.
Note: Certain columns are required while others becoming conditionally required based on which columns you fill out. Refer to the Entity Feedback Schema at the bottom of this Knowledge Base Article to understand which fields are required or optional.
Set Header
1. Once the file is selected from the computer, you will be on the Select the header row
step. The modal will show a preview of the CSV file and you will be asked to confirm if the first row contains the column headers.
2. If headers were included in the file, you will need to let the CSV importer know which row contains the header so it’s not imported as Entity Feedback data.
If the file contains a header row, click on that row then choose Confirm selection and continue. You will be taken to the Review and edit step.
If the file does not contain a header row, click The file contains no column names. You will be taken to the Match your columns step.
Match Columns
1. On the Match Columns step, you have the option to match columns to the expected headers or ignore a column from being imported.
2. Alloy will do its best to match the values in each column to the accepted values. If a value is mapped incorrectly, select the correct value from the drop-down menu. If you do not need a column to be imported, you can click Ignore this column. Alloy will ignore the column when completing the upload. You can restore the column by selecting a header in the drop-down menu.
3. To proceed to the next step, click the Confirm matching and continue button at the bottom. This will take you to the Match values step.
Match Values
1. On the Match Values step, you have the option to match the values in the columns to the accepted values.
2. Alloy will do its best to match the header to the correct mapping. If the mapping is incorrect, you can change the match using the drop-down menu.
3. To proceed to the next step, click the Continue button at the bottom. This will take you to the Review and edit step.
Review
1. On the Review step, you will have the option to review the Entity Feedback data and make any final adjustments. If there are any formatting errors that need to be corrected, they will be surfaced at this step by a cell highlighted in red. You can filter for problematic rows by toggling the Show rows with errors option. Rows with valid data are inserted. Rows with validation errors are identified so they can be corrected and corrected.
2. Certain columns have a required format. You can hover over the available info tip to learn more about the accepted values for that column.
3. At this step, you can also input any new data manually into any column or row.
4. You may also click Finish to start the import.
5. Before the import begins, you will confirm one final time to proceed to update the Entity Feedback with a new entry. New Entity Feedback records are appended. Existing records are not overwritten; a later submission for the same entity is added as a new record.
Once the import has been completed successfully, a banner will indicate a successful import.
Entity Feedback Schema
(* denotes fields that are always required)
Column Name | Conditional Requirements | Type | Description |
Entity Token* OR
External Entity ID*
| Required | String | Identifies entity. |
Evaluation Token | Required if Entity Token or External Entity ID are not provided | String | Identifies evaluation. |
Case Status |
| String |
What is the status of this case's internal investigation?
Allowed values are:
Open, Closed, Escalated, Pending Review
|
Case Reason* | Required | String |
Why is feedback being submitted for this case?
Allowed values are:
AML, Confirm Fraud, Suspected Fraud, No Issue, Other
|
Fraud Type |
| String |
Is this a fraud case? If so, what kind?
Allowed values are:
N/A, ATO, First Party, Second Party, Third Party, Synthetic, Check Fraud Deposit, Check Fraud Inclearing, Check Fraud Cashed, Payment Fraud Wire, Payment Fraud ACH, Payment Fraud P2P, Scam, Mule, Identity Theft, Other
|
Fraud Channel |
| String |
Through what channel was this fraud committed?
Allowed values are:
N/A, Branch, ATM, Online, Mobile
|
Fraud Detected At |
| String | Optional date/time field |
Loss Amount |
| Double |
How much was lost due to this case?
Accepted values are:
Positive integers with a max of 12 digits
|
Exposure Amount |
| Double |
How much could have been lost due to this case?
Accepted values are:
Positive integers with a max of 12 digits
|
Entity Status |
| String |
Is this entity a confirmed real identity (victim) or suspected to be a synthetic identity (suspect)?
Accepted values are:
Victim, Suspect
|