Summary

Users can now edit duplicate transaction control point columns directly at the engagement level.

This enhancement allows users to add engagement-specific columns to duplicate transaction analysis without requiring library-level configuration changes. This is especially useful when uploaded general ledger data includes additional mapped fields that are important for identifying duplicate transactions within a specific engagement.

Configure duplicate transaction control points

After completing data mapping during the ingestion workflow, navigate to Engagement settings > Risk scores.

Select the MindBridge Score, then locate the Duplicate Transaction control point. Add relevant mapped columns from the available column list.

The selected columns are then included in duplicate transaction analysis when the analysis is run.

Workflow considerations

Additional columns must first be mapped during data ingestion before they can be added to the duplicate transaction control point configuration.

To apply engagement-level duplicate transaction settings:

• complete the ingestion and mapping workflow
• update the duplicate transaction control point configuration in Engagement settings
• run the analysis after the configuration changes are complete