Split Transactions
<p><strong>Split Transactions</strong></p><p>This analytic test is used to identify activities that potentially could represent split transactions. This analytic can be applied to a wide variety of data (e.g. invoices, purchase orders, requisitions, corporate card transactions etc.)</p><p>A split transaction occurs when multiple transactions are made in order to stay within a single transaction authorization limit. While each individual transaction may appear to be authorized and valid, it is only when these transactions are linked that the circumvention becomes evident. Split transactions are a good example of how the intent of a control can be violated even though the designed ‘rule’ (in this case a single authorization limit) was never technically broken.</p>
Split Transactions
This analytic test is used to identify activities that potentially could represent split transactions. This analytic can be applied to a wide variety of data (e.g. invoices, purchase orders, requisitions, corporate card transactions etc.)
A split transaction occurs when multiple transactions are made in order to stay within a single transaction authorization limit. While each individual transaction may appear to be authorized and valid, it is only when these transactions are linked that the circumvention becomes evident. Split transactions are a good example of how the intent of a control can be violated even though the designed ‘rule’ (in this case a single authorization limit) was never technically broken.
Nodes
Extensions
- FeatureKNIME Base nodes
- FeatureKNIME Excel Support
- FeatureKNIME Expressions
- FeatureKNIME Javasnippet
- FeatureKNIME Quick Forms
- FeatureKNIME Reporting
- FeatureKNIME Statistics Nodes
- FeatureKNIME Views
- FeatureLhasa public plugin
Links
- No links available