Skip to content
English - Australia
  • There are no suggestions because the search field is empty.

Why might a transaction need to be reviewed for manual approval?

A transaction can stick on conflicting ID data, pending sign-off for a high-risk flag, or third-party verification service interruptions; manual approval resolves these with an audit-logged override.

A transaction can get stuck in a state where automatic matching can't proceed - typically due to:

  • Conflicting ID data - e.g. the name on the captured ID doesn't exactly match the name entered at transaction creation, or the date of birth differs slightly. The mismatch could be a typo or a genuine data variation that needs human judgement.
  • Sign-off pending - the transaction has been completed by the operator but is waiting on Compliance Officer review for a high-risk flag. The CO needs to make a decision.
  • Supplementary documents requiring approval - the customer has uploaded additional evidence (proof of address, source-of-funds document) that needs review before the transaction can be cleared.

Force-match is the CO's mechanism for resolving this stuck state by making a deliberate decision: yes, the captured data does match the customer despite the surface mismatch, or yes, the supplementary evidence is acceptable. The force-match action is audit-logged - the CO's decision and the reasoning are preserved in the transaction record.

Force-match should be used deliberately, not as a workaround for poor data quality. If the same firm hits force-match frequently, it's a signal to look at processes upstream (better data capture at the front end, clearer customer instructions). The CO's audit position is stronger when force-match is rare and well-justified than when it's used routinely.

Related articles