Aggregate Limits Detection
Table of Contents
Use Case:
Organizations often need to track the amount and value of customer revenue transactions recorded in sales or ERP systems like SAP or Oracle over a set period to ensure they follow company policies and regulations. For instance, if a customer account shows multiple high-value transactions within a short timeframe, it could exceed expected thresholds and trigger a need for further review. This monitoring is especially important in industries with strict financial controls, as it helps identify potential compliance issues early, preventing them from escalating.
The Aggregate Limits Detection analytic tracks the total value or volume of transactions over a set period, using rule-based analysis to detect possible violations of company policies. These rules, configured by the company, define time frames, transaction types, and aggregate thresholds. For instance, a manufacturing company might use this analytic to track daily, weekly, or monthly transaction activity for specific customer accounts to detect policy breaches and ensure compliance with both internal standards and industry regulations.
| Description | Identification of transactions for a subject where an aggregate limit rule (configured by the company) is met. Aggregate limit rules combine a period of time, selection of transaction spend classifications/types, and sum of value or volume |
| Domain(s) | Customer Revenue |
| Analysis Type | Context Flag |
| Focus Area | Context Analysis |
| Score Methodology | The aggregate value or volume of transactions |
Default Scoring Criteria
Importance: 4 (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, open the settings page from Risk Analysis Settings → Aggregate Limits Detection (Customer Domain) and click Add A Rule.
To configure a rule for this risk analysis:
1. From the Admin page, navigate to Risk Settings > Risk Analysis Settings > Aggregate 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 |
| Context Period in Day | The period of time from the spend date for which transactions are considered by the rule | 1 to 365 Days |
| Measure | The measure computed (after rule components are applied) and compared with the Scoring and Automatic Criteria | Amount or Frequency |
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.
Exclusions
None