Transaction monitoring cases that explain themselves

An alert is only useful if the analyst can see why it fired. Too many monitoring systems hand over a rule name and a score, and leave the investigator to reconstruct the rest from account statements and screenshots. Transaction monitoring cases in Bits open with the full picture: the transaction, the debtor and creditor, and the rule-by-rule outcome of the procedure that evaluated it.

A short primer on what a transaction monitoring case is. Rules run against transactions as they arrive. When a transaction matches a rule, or a procedure decides a human should take a look, Bits opens a case: a container for the transaction, the parties involved, the evidence, and the decision. Everything an analyst does happens inside it, from assigning and discussing it in comments to editing details, deciding, and, when needed, reporting onward.

Practical examples look like this. A 48,500 EUR credit transfer to a counterparty first seen three days ago. A burst of small card payments in a merchant category the customer has never used. A payout to a country that recently moved onto a high-risk list. In each one the questions are the same: which rule fired, on what values, and what else do we know about these parties? That is what the case is built to answer first.

What you see when a case opens

A case is created when a transaction matches a monitoring rule, or when a procedure reaches a Case action. The top of the case is a single summary line: type and scheme, instructed time, amount, settlement amount when it differs, status, reference, fees, and initiation method. Below it, the debtor and creditor sit side by side with their identifiers, country, and entity id, an Open entity link for parties that are your customers, and a toggle that reveals every entity field and custom property.

The Rule evaluations section lists each rule the procedure ran with a plain True or False, and under each rule the parameter values recorded at execution time, such as the amount or the counterparty’s first-seen date. Expand a rule to see its version and expression. The procedure execution is also shown as a graph of the published version that ran, so you can follow the path the transaction took.

Copy summary

One link at the end of the summary line copies a plain-text summary: a verdict sentence with amount, type, debtor and creditor with their countries and how many of the rules triggered, a sentence about earlier transactions, one line per rule with its outcome, and the transaction id, status, scheme, timestamps, and both parties with entity ids. Paste it into a case comment, an escalation email, or another case management system.

Everything else, in place

• Recent transactions for the same parties, right under the summary.

• Transaction details collapsed by default, with in-place editing of amounts, status, and custom properties.

• Assignee, status, activity feed, comments, and related cases in the same case layout as every other case type.

The outcome column is deliberately plain: True or False, no colors, no icons. The analyst reads the evidence instead of a verdict.

Why this matters for compliance

Consistent, explainable alerts shorten investigations and make audits easier. When every case carries the rule logic and the values it was evaluated on, the reasoning behind a decision is documented at the moment it is made, not reconstructed months later.

Want to see it in action? Reach out to learn how Bits Technology can streamline your compliance operations.