Item Limits Detection
Table of Contents
Use Case:
Organizations need to ensure compliance with internal policies regarding high-risk or high-value customer transactions, such as large transactions, specific types of revenue activity, or unique transaction types and customer classifications. Monitoring for potential violations of these limits is essential for maintaining financial and regulatory integrity.
The Item Limits Detection analytic is a powerful tool that enables organizations to configure rules to flag transactions that exceed predefined limits based on various attributes, such as total transaction amount, billing value, or specific transaction categories.
For example, if a customer transaction exceeds a set threshold for large-value sales, credits, or other higher-risk transaction types, the system will automatically flag the transaction for review. This analytic can also detect other high-risk customer revenue transactions, such as large sales or credits in high-risk countries or transactions involving higher-risk customers or third parties, and much more.
By tailoring these rules to your specific policies, industry standards, or regional regulations, organizations can effectively monitor for compliance risks, ensuring adherence to transaction limits and preventing potential financial or reputational damage.
| Description | Identifies transactions where an item limit rule (configured by the organization) is met. Item limit rules are a collection of different attributes and values that must be met to quality for comparison with scoring criteria. |
| Domain(s) | Customer Revenue |
| Analysis Type | Context Flag |
| Focus Area | Context Analysis |
| Score Methodology | The spend measure is selected and applied in accordance with the rule components. |
Default Scoring Criteria
Importance: 5 (default)
Enabled: True (default)
No rules are configured by default. Rules must be set by user.
Rule Configuration
To configure a rule for this risk analysis:
1. From the Admin page, navigate to Risk Settings > Risk Analysis Settings > Items Limits Detection (Customer Domain). Then, click Add A Rule.
2. Complete the following required rule fields:
| Rule Field | Description | Settings Options |
|---|---|---|
| Name | Name for the specific rule | Free text |
| Description | Description of the rule | Free text |
3. Click Add A Rule Component.
4. To set a component, select a Field and Search Type from the dropdowns.
The Value field will appear after you select a Field and Search Type.
See a description of Field, Search Type and Value below:
| Field | Search Type | Value Type |
|---|---|---|
| Company | Includes OR Excludes | List is populated from customer data* |
| Customer (Payer) | Includes OR Excludes | List is populated from customer data* |
| Customer Billing Line Item Amount USD |
Greater Than or Equal To OR Less Than or Equal To |
Dollar Amount |
| Customer Billing Line Cost USD |
Greater Than or Equal To OR Less Than or Equal To |
Dollar Amount |
| Customer Billing Line Item Text | Contains OR Does Not Contain | Free text |
| Has Free of Charge Item | Includes OR Excludes | Yes/No |
| Is Return | Includes OR Excludes | Yes/No |
| Material Type | Includes OR Excludes | List is populated from customer data* |
| Organization Unit | Includes OR Excludes | List is populated from customer data* |
| Original Transaction Amount USD |
Greater Than or Equal To OR Less Than or Equal To |
Dollar Amount |
| Subject (Payer Country) | Includes OR Excludes | Preset List |
| Subject Account Group | Includes OR Excludes | List is populated from customer data* |
| Subject Classification | Includes OR Excludes | List is populated from customer data* |
| Transaction Reason | Includes OR Excludes | List is populated from customer data* |
| Transaction Type | Includes OR Excludes | Preset List |
| Transaction Type (Detailed) | Includes OR Excludes | List is populated from customer data* |
*For values populated from customer data, value lists will not populate if data is not available.
Note: Where multiple rule components are set, they operate only in an “and” manner.
5. Click the Save Changes button at the bottom of the page to save your rule.
Unique Configurations
This analysis utilizes rules configured by the user, for which they can configure the following:
- Rule Components: specific restrictions, by field, to limit the transactions that are considered by the rule
- Scoring Criteria based on the transaction value (Strong, Moderate, and Weak values can be set)
- Automatic Criteria: transactions that meet these criteria will appear in Monitoring Review results regardless of the Risk Engine Score
Exclusions
None