Customer Compliance Check
The system periodically cross-verifies exclusion lists against your customer records in M3 by using Infor AI. While optional, integrating ION Workflow is recommended to enhance automation.
The frequency of runs depends on how often you update your customers and how often an exclusion list is updated. The solution setup, including the upload of the exclusion list, is completed during the deployment phase.
Customers are classified based on the similarity of customer names, address details, customer numbers, organization numbers, and VAT numbers compared against M3 records. Relevant fields are concatenated into a single string to assess similarity against the exclusion list. The results are presented in a Birst report.
This list shows the classification:
- Excluded: Match score is above 90%. This percentage is the default but is configurable.
- Potentially Excluded: Match score is between 70% and 90%, which may indicate a faulty match so you must double check for confirmation. This classification is not available when using an API endpoint.
- Not Excluded: Match score falls below the defined threshold.
If the result is Excluded or Potentially Excluded, the solution can be configured to block transactions with the flagged customer until further approval is granted.
This solution provides these benefits:
- Reduces risk of non-compliance.
- Eliminates recurring manual work.
- Flexible scheduling based on your update cycles.
Best practices
Follow these best practices to help the solution run smoothly and avoid issues:
- You must schedule the run and regularly verify your customer data in Birst. We recommend running the process once a month if you rarely update your customers. However, the schedule primarily depends on when the selected exclusion list is updated.
- You should identify which lists are most relevant to your organization and determine from which lists your customers must be excluded.