For the person who signs

No. Every clearance and escalation is still a named person's decision; the platform records what that person saw, what they decided and why. Automated closures run only under rules you approve, and they are logged under their own user.

Yes. List versions, parameter history and decision logs are dated and retrievable per period. You can show what the system held on a given day in March, which match was cleared, by whom and why, without rebuilding it from memory.

Each override carries a reason and a named reviewer, so overrides can be reviewed as a set rather than one at a time. A single exception reads as a decision; a recurring one becomes visible to you before a regulator finds it.

They are drafted from the case record, per entity and per jurisdiction. You review, complete, sign and submit, and nothing goes out without that signature. The draft carries the evidence, so what you sign matches what was investigated.

Filing formats and deadlines are handled per entity, while the suspicion process stays one. A group MLRO sees the whole picture across entities, and each local filing still meets its own FIU's format and deadline.

Alerts from onboarding and continuous monitoring are ranked by risk, grouped by customer and show the reason for each alert. You see which customers need attention this week, not a flat list of rows in arrival order.

Escalated matches, with the ownership structure and the source evidence already attached. The call that only you can make starts from a complete file, not from a request back to the analyst for more information.

Every change is logged with its date, its author and its reason, so a threshold can be defended, not just stated. When a regulator asks why a setting moved last year, the answer is in the change history, not in someone's memory.

To your retention policy: five years in most regimes and ten where the jurisdiction requires it. The record stays readable for the whole period, because an archive that cannot be opened meets none of the requirements.

The period's core artifacts, including decisions with their reviewers, overrides, parameter history and filings, exported as one package rather than compiled by hand. It is the same pack whether the request comes from the board, internal audit or the supervisor.