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.
To use this workflow in KNIME, download it from the below URL and open it in KNIME:
Download WorkflowDeploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.