Reviewing transactions
Transaction Monitoring → Transactions lists everything received, with its decision. Opening a transaction shows why it was decided that way. Recording a review requires Review flagged transactions.
Why this was decided
The transaction detail opens with the rules that fired, each showing its name, the version that ran, its band, and the points it contributed. Under each rule are the conditions that made it match, in plain language.
Two kinds of line appear:
- A field condition names the field and the threshold — "Amount is above 1,000,000". The value itself is on the transaction, shown further down the page.
- A window count shows the number that was computed and the exact period it covered — "14 transactions for the same initiator account in the last hour". Because the period is recorded, the line links to those transactions.
That link matters: a count on its own tells you a rule fired, whereas the underlying transactions tell you whether it should have.
Shadow rules appear separately and are marked as not having affected the decision.
Incomplete evaluations
If some rules could not run, the section carries a warning and the decision is partial. The rules that failed
are listed with a reason. Treat a partial PASS with the same care your integration does.
Recording a review
Record review captures an investigation outcome: Cleared, Suspicious, Escalated or False positive, plus an optional note.
For a held transaction you also record a release decision:
- Release — allow it to complete.
- Reject — do not complete it.
This is the value your core banking system reads when it next polls the transaction. Until a review is recorded, a held transaction stays unresolved from the caller's point of view, so held transactions should be worked promptly.
A transaction can be reviewed once. The review, the reviewer and the time are recorded, and the action is written to the activity log, which is integrity-linked and append-only.
Working the queue
Filter the list by decision to find what needs attention, and by review state to separate what has been handled from what has not. Held transactions are the most time-sensitive, because a person is holding up a payment; flagged transactions have already settled and can be worked in order.
What the list does not show
The list deliberately omits customer and counterparty detail. Those snapshots appear on the transaction detail page, which records an access event when opened. Identity numbers are currently shown in full on that page to users who can read transactions.