A report has been filed or an account is under review, and a colleague writes back to explain the delay: "between us, your account has been flagged." That sentence, not the report, is the offence. VerbaPulse flags the language that discloses an investigation before the message sends.
Tipping off is disclosing that a suspicious activity report has been made, or that a money laundering investigation is underway, in a way that could prejudice it. In the UK it is a criminal offence under POCA 2002 section 333A, and the EU anti-money laundering directives carry an equivalent prohibition. The act is the disclosure itself.
The MLRO knows the rules cold. The risk lives one desk over, with the relationship manager or the onboarding agent who is trying to be helpful. A frozen payment needs an explanation, a delayed onboarding needs a reason, and the honest answer ("we had to report this", "compliance is reviewing you") is the one that tips off. By the time supervision samples the mailbox, the message is already with the customer.
VerbaPulse reads the draft as it forms and flags the span that would disclose a review or report, with a plain reason. Real output from the product:
The same check covers the quieter ways the disclosure slips out:
VerbaPulse does not run KYC, transaction monitoring, or your SAR process, and it does not decide what is suspicious. Those belong to your AML framework and your MLRO. VerbaPulse sits at the one point they do not cover: the outbound message, where a careless explanation becomes the tipping-off act. It is one control inside email compliance for financial services, and it complements the monitoring and archiving systems you already run.
For the evidence behind this, our language risk benchmark runs real, anonymized cases through the product and reports what it flags.