Can the platform force-match a non-standard transaction past the review stage?
Yes, a user with the appropriate role can manually approve a transaction where the user has formed a positive view that compliance obligations have been met, all audit-logged.
Overview
Yes. An easyAML user with an appropriate role can manually force a transaction past the review gate where the underlying checks haven't met standard verification thresholds but the user has formed a positive view that their compliance obligations are met. This covers non-standard transactions generally, including cases where two IDs for a long-known client conflict (for example a birth-certificate name versus a licence name).
Audit trail
The override is audit-logged with the user, timestamp and reason, so the chain of custody is preserved.