In Policy Management, you can test a policy set against historical data to ensure effectiveness, reduce compliance risks, and optimize a decision assignment before the set is active. Refer to the following scenarios and examples for how you can use testing in Policy Management:
-
Data-driven policy decisions
You can test policy sets using historical data to validate what would have happened if it had been active during past orders. This provides evidence-based insights to help you create better policy sets.
-
Threshold changes
You can test the shift in primary decision thresholds for scores, like Omniscore. For example, if an Omniscore less than 35 was denied and you updated the policy to be less than 40, then the testing analysis quantifies all orders that had an Omniscore between 35 and 39.99. Testing gives you a comparison of how many more orders would have been declined with the new threshold.
-
Priority ordering
The order in which policies or segments are executed can affect the final decision, especially if a block policy is placed before a challenge policy, or if a global allow policy is moved. You can set up testing to identify all orders that would have been blocked early, and then quantify how a challenge decision would have changed the review queue volume and auto-block efficiency.
-
Decision shift analysis
You can test policy sets with different decision outcomes that would have received one decision under an old policy but receive a different decision under the new policy. This helps quantify the immediate operational impact of decision changes.
Note
This feature is not available for organizations with a parent/child organization hierarchy.
Note
Currently, you can test up to 30,000 transactions per calendar month.
To test a policy set with historical data:
-
Sign in to Kount 360.
-
Select Policy Management.
-
Take note of an existing policy set that you want to test.
Note
Policies can be created only for existing sets. If the set is not already created, you must create the set before creating policies.
-
Select Testing.
-
Select an Event Type.
-
Select New Job Request.
-
In the prompt that displays, enter values for the following data fields:
-
Test Name
Enter a unique name for the test.
-
Policy Set
Select a policy set that you want to test.
-
Version
Select the version of the policy set that you want to test. You can test older iterations of the policy set to compare to the current version.
-
Date Range
Enter a date range of historical orders to test the select policy set.
-
-
Select Review Request.
-
Select Submit.
The test is added to the table with a Pending status.
-
Select Refresh Rows to update the test status.
Once completed, you can view the test details.
To view the test results for a policy set:
-
Sign in to Kount 360.
-
Select Policy Management.
-
Select Testing.
-
Select an Event Type.
-
Find the test. Then, in the Actions column, select View.
Test Details displays with a comparison and change table. The Comparison Table provides the Test Value and compares it to the Historical Value to calculate a percent difference for all three decisions (Allow, Block, Challenge). The Change Table displays what decisions changed during the test with the new policy set.
Comments
0 comments
Article is closed for comments.