Duplicate Billing Detection
Table of Contents
Use Case:
Organizations need to monitor customer billing activity for potential duplicate transactions that could indicate processing errors, control failures, or attempts to avoid approval requirements. Duplicate billing may occur when the same transaction is recorded more than once or when a transaction is split into multiple entries with identical or similar attributes. This can be particularly important for higher-risk customer revenue transactions, such as credit notes or other receivable reductions, where duplicate activity may have a greater financial or compliance impact.
The Duplicate Billing Detection analytic identifies potential duplicate customer transactions by comparing selected transaction attributes within configured detection collections. A duplicate is identified when two or more transactions share the same value for the key fields defined in the collection. For example, an organization may configure the analytic to identify transactions with the same customer, amount, invoice number, or other relevant billing details. By flagging potential duplicates for further review, the analytic helps organizations detect billing errors, strengthen financial controls, and identify transaction patterns that may indicate inappropriate splitting or other policy violations.
| Description | Identifies potential duplicate billing transactions by comparing selected transaction attributes within customer-configured detection collections |
| Domain(s) | Customer Revenue |
| Analysis Type | Context Flag |
| Focus Area | Policy/Control |
| Score Methodology | Duplicate detection is based on the configured collection, where transactions are flagged when they share the same value for the selected key fields |
Default Scoring Criteria
Importance: 1 (default)
Enabled: True (default)
| Risk Result | Default Value | Notation |
|---|---|---|
| Weak | Key R, Key T | Collection Identifier |
| Moderate | Key S | |
| Strong | ||
| Auto |
Unique Configuration
The Duplicate Billing Detection analytic identifies potential duplicates using configured collections. Each collection combines:
- Keys: transaction attributes that must match, such as the customer, company, transaction amount, transaction type, transaction date, source reference value, organizational unit, or creator.
- Criteria: additional conditions used to refine the comparison, such as transactions occurring within a selected number of days, having different dates or transaction details, or meeting a minimum transaction amount.
The following collections are available by default:
- Collection R: identifies transactions with the same payer customer, sold-to customer, transaction type, amount, and source reference value when the transaction dates are within 90 days.
- Collection T: applies the same comparison as Collection R but requires the transactions to have different transaction dates.
- Collection S: identifies transactions with the same payer customer, sold-to customer, transaction type, and amount when they occur on different dates within 90 days.
These collections can help identify transactions that may have been entered more than once or recorded separately despite sharing key billing details.
Exclusions
Transactions marked as no longer valid are excluded from duplicate detection.
Customers can also configure exclusions based on:
- Transaction type
- Transaction reason
- Transaction amount in USD
No exclusions are applied by default.