Chronology Review
Written by Michelle Henley
Updated at September 16th, 2024
Table of Contents
| Description | Identifies transactions where specific chronological expectations are violated |
| Domain(s) | Vendor |
| Analysis Type | Flag |
| Focus Area | Timing |
| Score Methodology | The chronology violation rule, where a transaction is noted when the associated dates meet the violation rule |
Default Scoring Criteria
Importance: 5 (default)
Enabled: True (default)
| Risk Result | Default Value | Notation |
|---|---|---|
| Weak |
Chronology Rule Found
|
|
| Moderate | Key O, B, C, G, H, I, J | |
| Strong | Key E, F, K, L | |
| Auto |
Unique Configuration
Configuration of the checks are as follows:
| Key | Rule for “Hit” Identification | Threshold Days* |
|---|---|---|
| A | Pre-Approval Event Date before Pre-Approval Approval (first approval date) | 0 |
| B | PO Creation before Pre-Approval Approval (first approval date) | 0 |
| C | Invoice Receipt before Pre-Approval Approval (first approval date) | 0 |
| D | Payment before Pre-Approval Approval (first approval) | 0 |
| E | Invoice Receipt* before PO Creation | 0 |
| F | Payment before PO Creation | 0 |
| G | Pre-Approval Event Date before PO Creation | 0 |
| H | Pre-Approval Event Date before Invoice Receipt | 0 |
| I | Invoice Receipt before Pre-Approval Event Date | 0 |
| J | Pre-Approval Event Date before Payment Date | 0 |
| K | Payment Date before Pre-Approval Event Date | 0 |
| L | Vendor Invoice Document Date before PO Creation | 0 |
| M | Vendor Invoice Document Date before Pre-Approval Approval | 0 |
| N | Vendor Invoice Document Date before Pre-Approval Event Date | 0 |
| O | Invoice Liability (posting) Date before Invoice Receipt Date (typically synonymous with created date) | 1 |
* When the data field is available.
Note: “Threshold days" allows for configuring a grace period (in days). For example, if the threshold days for “Payment before PO Creation” is set for 5 days (above), then when the Payment occurs 4 days before the PO Creation, the item does not generate a match (however, if 5 days or more, there IS a match). Further, this can be configured (by Lextegrity) in a negative manner.
Exclusions
None from pre-approval (all requests available for match, regardless of status)