Duplicate Spend Detection
Written by Michelle Henley
Updated at September 16th, 2024
Table of Contents
| Description | Identifies possible duplicate expenses for a vendor using a variety of chosen detection keys |
| Domain(s) | Vendor |
| Analysis Type | Context Flag |
| Focus Area | Policy/Control |
| Score Methodology | The detection key is where a duplicate is noted when two transactions have the same value for the key noted |
Default Scoring Criteria
Importance: 2 (default)
Enabled: True (default)
| Risk Result | Default Value | Notation |
|---|---|---|
| Weak | Not Set | Specific Key (See chart in Unique Configurations below) |
| Moderate | Key I | |
| Strong | Key H | |
| Auto | Not set |
Unique Configuration
Collections can be created using a combination of the following:
-
Keys:
- Transaction Amount
- Transaction Date
- Impact Date
- Company
- Subject ID
- Expense Type
- Expense Type (Detailed)
- Vendor Invoice Number
-
Criteria:
- Different Payment Methods
- No Credits
- Different Transaction Date
- Different Impact Date
- Impact Within 10 Days
- Impact Within 30 Days
- Impact Within 60 Days
- Impact Within 90 Days
- Impact Within 180 Days
- Transaction Within 10 Days
- Transaction Within 30 Days
- Transaction Within 60 Days
- Transaction Within 90 Days
- Transaction Within 180 Days
- Spend Amounts >= $50
- Spend Amounts >= $500
- Spend Amounts >= $1000
- Different Payment ID
-
Same Payment ID
| Key | Rule for “Hit” Identification |
|---|---|
| H | Same Vendor / Vendor Invoice Number, Different Payment ID, Impact within 60 Days |
| I | Same Vendor / Amount / Vendor Invoice Number, Impact within 60 Days |
| V | Same Vendor / Amount / Vendor Invoice Number |
| W | Same Vendor / Amount / Expense Type (Detailed), Impact within 60 Days |
| X | Same Vendor / Expense Type (Detailed), Different Payment Methods |
| AI | Same Vendor / Amount / Impact Date |
Exclusions
- Any transaction for less than $0.01