* Create an Imported Business Object: Import the file containing the list of companies into Oracle Risk Management as an imported business object1.
* Select the 'Payment' Business Object: Choose Oracle's delivered "Payment" business object, which includes attributes related to payment transactions2.
* Combine Objects in a Model: Use the transaction model to combine the imported business object with the "Payment" business object1.
* Add a Standard Filter: Implement a standard filter to compare the "Remit to Supplier Name" from the
"Payment" object with the "Company Name" from the imported business object. Set the similarity condition to 95% to identify payments made to companies on the list1.
References:
* Oracle's documentation on Overview of Transaction Models provides insights into how transaction models can uncover transactions that might involve risk, such as payments to unwanted companies.
* The Overview of Business Objects explains how to work with imported objects and combine them with delivered objects for analysis.
* Detailed instructions on Selecting Business Objects for a Transaction Model guide through the process of creating and using filters within a model.

This filter would allow the model to compare the dates of the invoice and the credit card transaction to ensure they are within a reasonable time frame of each other, which is indicative of a duplicate charge. A similarity within +/- 10 days is a common practice to account for processing delays while still capturing potential duplicates.
References: For the most accurate and detailed explanation, please refer to the Oracle Risk Management documentation on the Oracle site, specifically the sections that discuss building transaction models and setting up filters for identifying duplicate charges.
Please note that this is a logical deduction based on the information provided and not a verified answer from the official Oracle documentation. For a verified answer, you should consult the Oracle Risk Management documents directly.

When a Control object has scheduled assessments with future dates and the test plans associated with it are updated before the assessment starts, the assessment will be associated with the version of the test plans that were current at the time the assessment was initiated. This ensures that the assessment is conducted with the relevant procedures and criteria that were intended for that specific period.
References:The information provided is based on the Oracle Risk Management documentation, which details the use of test plans in control assessments and how they are managed within the system123. The REST API documentation for Oracle Fusion Cloud Risk Management also provides insights into how test plans can be viewed and managed, indicating the behavior of the system when updates occur2.